Consider adding RegistryCI.jl to enforce versioning/documentation guidelines

Alexsp32

Part of the advantage of registering packages in the General Registry is the [enforcement of guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) on package versioning, maintaining compatibility entries and the existence of documentation, all of which are important steps to developing sustainable code. Carrying over some of these guidelines as conditions for addition to the ACEregistry would make all of the contained packages more sustainable, while still allowing full control over deviations from the guidelines (as opposed to the General Registry). In particular, enforcing the existence of compatibility entries would be a great step, since any packages without effectively have an expiry date 12-18 months into the future, when it becomes incredibly annoying to piece together dependency versions that might have been current at the time of development if you want to update the code to the current state of the ecosystem.

cortner

the entire point of ACEregistry is to not deal with the restrictionsof General, so we won't do this. I understand your frustration - but I just don't have the time or interest to deal with this unless I need it for my own research. The point of the software project with James and Reini is to better separate and manage components of ACEsuit so that maintenance can be better distributed. All the new backends are already in General, but it will now be a lot of boring work refactoring the front-end.