JuliaRegistries / Registrator.jl

Julia package registration bot
https://julialang.org/packages
Other
209 stars 47 forks source link

Requesting new package name validation tool #435

Open anchal-physics opened 20 hours ago

anchal-physics commented 20 hours ago

https://github.com/JuliaRegistries/General/blob/master/README.md#are-there-any-requirements-for-package-names-in-the-general-registry says

There are no hard requirements, but it is highly recommended to follow the package naming guidelines.

But the package naming guidelines do not specify that the package name has to be `Damerau-Levenshtein distance needs to be above 2' for automerging to work. In my opinion, this restriction is too strong and should be set to 1 instead of 2. But even if it is set to 2, we have no pre-assessment tool if the julia package name we are planning for is available and allowed or not. Please provide a tool that runs your automerge requirements on package name on a webpage or somewhere so that we can validate the name.

carstenbauer commented 13 hours ago

Note that "automerge fails" != "the package name is invalid". We make exceptions to the automatically checked rules. But having a way to run the automerge name checks before registration doesn't seem unreasonable to me.

DilumAluthge commented 12 hours ago

Duplicate of https://github.com/JuliaRegistries/RegistryCI.jl/issues/453?

ericphanson commented 9 hours ago

I think it would be cool to have a web tool where you can enter a name and it could run and surface the checks. I don't think it would be worth the increased maintenence cost relative to just providing a function in RegistryCI like https://github.com/JuliaRegistries/RegistryCI.jl/issues/453 though; it seems like something that would end up as nice for a bit until it breaks at some point and goes unmaintained.