New package: TDEP v0.0.1

[JuliaRegistrator]

• Registering package: TDEP
• Repository: https://github.com/ejmeitz/TDEP.jl
• Created by: @ejmeitz
• Version: v0.0.1
• Commit: 5ecec4bb06c747476debd79df884ef8e8e0a5094
• Git reference: HEAD
• Description: Temperature Dependent Effective Potential Bindings in Julia

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
• Name is not at least 5 characters long
• Package name similar to 5 existing packages.
  1. Similar to SDDP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  2. Similar to TauP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  3. Similar to RDDP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  4. Similar to ODE. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  5. Similar to DSP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

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.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[goerz]

I would recommend something like MolecularTDEP as a package name

[ejmeitz]

This is a wrapper of an existing package whose name is just TDEP. Most other wrappers I've seen just stick with the original name.

[ejmeitz]

@goerz Do I really have to change the name on this? There are plenty of packages like QML.jl and CUDA.jl which are just wrapper libraries and also less than 5 characters.

[goerz]

The last time this was discussed, the general opinion of the registry maintainers was that the "Wrappers can be named after the project they wrap" guideline does not get around other guidelines. The most important guiding principle for package names is very much becoming "err on the side clarity". An idea that's been floating around for wrappers specifically is to start encouraging the suffix Wrapper as a very descriptive naming scheme, so TDEPWrapper in this case (you may want to highlight the "wrapper" aspect in the README as well). More generally, when acronyms should be part of a package name, my recommendation is to combine them with an explanatory prefix of suffix.

With respect to existing package names: In the early days, there was no enforcement of naming rules in the General registry. 3-letter names in particular are considered a no-go at this point. Other names are a judgement call, but anything less than 5 characters or in all-caps can only be merged by a full registry maintainer (not me). In any case, the interpretation of the naming guidelines is continually evolving, and getting stricter and pushing for more descriptive package names as more and more packages are registered. You can try making a case for TDEP on Slack, but it might be an uphill battle. My recommendation would definitely be to rename the package.

[ejmeitz]

#146680.

Seems to have opened a new one after I renamed. Can close this.