As I was finishing up the new avogadro.cc webpage, I came across GitHub issue templates: https://help.github.com/articles/creating-an-issue-template-for-your-repository/
I think this would be a *huge* help. Here's my current draft - thoughts? <!-- Before submitting please search open and closed issues at https://github.com/cryos/avogadro The GitHub issue tracker is for bug reports and feature requests. If you have a question about using Avogadro, please post to https://discuss.avogadro.cc/ Feel free to use the following as a template and remove or add fields as you see fit. You can convert `[ ]` into `[x]` to check boxes. --> - [ ] I believe this to be a bug with Avogadro - [ ] This is a feature request ## Expected Behavior <!-- Describe the intended output or what you expected to see. --> ## Actual Behavior <!--- If describing a bug, tell us what happens instead of the expected behavior --> <!--- If suggesting a change/improvement, explain the difference from current behavior —> ## Steps to Reproduce <!-- If the problem occurs with a particular file, please either upload and attach the file or include a link here - this greatly improves our ability to test your problem. Screenshots can also be included if they help illustrate a behavior. --> ## Environment Information Avogadro version: Operating system and version: ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Avogadro-devel mailing list Avogadro-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avogadro-devel
