-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebrand and Rename the Cookiecutter - Discussion #123
Comments
I'd be in favor of replacing the "cms" acronym with "molssi" in some way, since "computational molecular sciences" isn't a widely-used acronym in my experience, and everyone calls this the "MolSSI Cookiecutter" in practice. I'm slightly in favor of continuing to use the phrase "cookiecutter". |
I'm for keeping "cookiecutter". For those that know the parent project, it's good for cookiecutter-cms to be associated as a specialty. For those that don't know about the parent project, it's a good intro to a broader world that they might have other uses for. "cms" I've never confused with content management system, but it is an initialism I associate closely with molssi. Happy as-is or "molssi". |
|
And does this mean that the MolSSI Advisory Board finally recognizes this project as a first-class MolSSI project rather than a "hobby side project"? ;) |
I concur that a rename would be helpful, and @jchodera's suggestion of
I hope so, this is one of the most useful MolSSI resources I know of. I point people to this quite often. |
To me, the "cookiecutter" prefix makes it sound like a fork of https://github.com/cookiecutter/cookiecutter rather than an instance of a cookiecutter template. However, |
It has been suggested by an advisory board to MolSSI's to consider rebranding this repository to distinguish it more from the base Cookiecutter tech it runs on. Specifically the name clashes between Cookiecutter (the base tech), and CMS (Content Management Systems).
The goal would be both distinction and easier searchability for the project.
Lower priority, but I wanted to get a discussion going for opinions and thoughts.
The text was updated successfully, but these errors were encountered: