New package: Carbon v1.0.0

[JuliaRegistrator]

• Registering package: Carbon
• Repository: https://github.com/vrkansagara/Carbon.jl
• Created by: @vrkansagara
• Version: v1.0.0
• Commit: 11203da3791766f702943b6c7d9f36c904710a1b
• Reviewed by: @vrkansagara
• Reference: new deployment at JuliaHub vrkansagara/Tz.jl#4 (comment)
• Description: A simple Julia API extension for DateTime.

[cormullion]

[noblock] This looks a bit like a test package ... 🤔

[github-actions]

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: Documenter
• Package name similar to 2 existing packages.
  1. Similar to Chron. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  2. Similar to Carlo. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simple retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[vrkansagara]

[noblock] This looks a bit like a test package ... 🤔

@cormullion Please check latest state

[cormullion]

[noblock] This looks a bit like a test package ... 🤔

@cormullion Please check latest state

I don't think code like this needs to be in a package?

function now()
    return DateTime(2023)
end

[vrkansagara]

@cormullion updated the code.
Can you help me with this how can I remove or solve this error.

Package name similar to 2 existing packages.
Similar to Chron. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
Similar to Carlo. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

[cormullion]

@cormullion updated the code. Can you help me with this how can I remove or solve this error.

Package name similar to 2 existing packages. Similar to Chron. Damerau-Levenshtein distance 2 is at or below cutoff of 2. Similar to Carlo. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

There's nothing you can do now - you have to wait 3 days before a submitted package can be registered - if it's considered to be a useful addition to the registry. You can discuss the naming of your package on the Slack channel mentioned above

[briochemc]

What does this package do? How is it related to carbon?

[vrkansagara]

Here is the explanation of the package name. Why did I choose this package name as Carbon?

There is a very good library in a different language community called Carbon , From where I was inspired to take the name and it has a very friendly implementation of the DateTime

There is no actual Carbon relating to this package nor relating to any chemical or substance relating in this package name

cc: @cormullion @briochemc

[briochemc]

I think there are a few problems here:

1. This package looks empty. No point in registering it at this stage.
2. It is not clear what this package intends to do. Please add some description/example of what people might use this for in your ReadMe at least.
3. The name choice is not good. If you call a package "Carbon.jl", people will expect it to have something to do with the most common definition of carbon, not a very specific PHP API. Try to think of a name that will be meaningful to a random Julia user.

[vrkansagara]

noted with thanks @briochemc , I have just changed the package name.

[vrkansagara]

@JuliaRegistrator
This issue should be closed now.

[vrkansagara]

FYI, I have changed that package name to TZ Hope this will works foryou @briochemc

[briochemc]

No, sorry, but it does not work: The new name, "Tz", is just as confusing if not worse. But this does not matter at this stage anyway, because your package is basically empty and thus not ready for registration.

[vrkansagara]

Now I am really confused about what is the definition of an empty package here.?

[briochemc]

I'm sorry that this is confusing to you. There's no formal definition as far as I know, but your package provides close to zero functionality. It merely contains four "Hello World!"-printing types of functions or aliases:

• greet just prints "hello". Not useful.
• version just prints the package version. Not useful since this functionality is built in the package manager.
• now just prints the current time with a static format. Not really useful and overwriting the standard library's now function seems like a bad idea.
• p is an alias for printf. Not useful. Probably errors since printf is not defined.

Anyway, What is the intended purpose of the package? Even this is not clear...

[vrkansagara]

@JuliaRegistrator Give up this PR and close it

[github-actions]

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]

[github-actions]

This pull request has been inactive for more than 30 days and has automatically been closed. Feel free to register your package or version again once you fix the AutoMerge issues. [noblock]