We welcome contributions in the form of bug reports, bug fixes, improvements to the documentation, ideas for enhancements, or the enhancements themselves!
You can find a list of current issues in the project's GitHub repository. Feel free to tackle any existing bugs or enhancement ideas by submitting a pull request. Some issues may be marked as beginner-friendly. These issues are a great place to start working with StateMint, if you're new here.
- Please include a short (but detailed) code snippet or explanation for reproducing the problem. Attach or include a link to any input files that will be needed to reproduce the error.
- Explain the behavior you expected, and how what you got differed.
- Include the full text of any error messages that are printed on the screen or found in the browser console.
- Make sure the test suite passes on your computer. To do this, run
python TestSuite.pyfrom thepythondirectory,make testfrom thewebdirectory, or run theTestSuite.nbnotebook from themathematicadirectory, depending on what code has been changed. - Always add tests and docs for your code.
- Please reference relevant GitHub issues in your commit messages using
#123. - Changes should be PEP8 and PEP257 compatible, although this project uses tabs instead of spaces.
- Keep style fixes to a separate commit to make your pull request more readable.
- Docstrings should follow the Google style.
- When you start working on a pull request, start by creating a new branch pointing at the latest commit on GitHub master.
- The copyright policy is detailed in the
LICENSE.
Thanks to the useful contributing guide of thermostate, which served as an inspiration and starting point for this guide.