Contributing to this project should be as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
When making changes in code, please use the existing development environment — this will save you from many errors and help create more convenient code to support.
To install the environment, run the ./bin/setup
script.
Github is used to host code, to track issues and feature requests, as well as accept pull requests.
Pull requests are the best way to propose changes to the codebase.
- Fork the repo and create your branch from
master
. - If you've changed something, update the documentation.
- Make sure your code lints (using black).
- Issue that pull request!
Report bugs using Github's issues
GitHub issues are used to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can.
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
People love thorough bug reports. I'm not even kidding.
Use black to make sure the code follows the style.
This program (and not only this) is automatically applied on code commit if you set up the developer environment as indicated at the beginning of this document. Please make this set up. It will greatly facilitate your work.
By contributing, you agree that your contributions will be licensed under its MIT License.
In short, when you submit code changes, your submissions are understood to be under the same License that covers the whole project. Feel free to contact the maintainers if that's a concern.