How To Contribute¶
Every open source project lives from the generous help by contributors that sacrifice their time and
ramlfications is no different.
To make participation as pleasant as possible, this project adheres to the Code of Conduct by the Python Software Foundation.
Here are a few hints and rules to get you started:
Current status of the project (including issues & PRs) can be seen on our waffle.io page.
- Meaning of GitHub labels:
help wanted: Feeling generous with your time? These issues are up for grabs. Ask any questions in the comments of the issue.
in progress: This issue is currently being worked on.
ready: Issue/bug has been confirmed, and is available for anyone to work on.
feature: Feature/idea to extend
bug: A bug or issue within
no repro: A filled bug that can not be reproduced (feel free to comment/reopen if you find you are seeing this bug).
wontfix: A filled issue deemed not relevant to the project in some way.
duplicate: Either duplicate issue or PR.
Take a look at the Wishlist for inspiration.
Any GitHub issue that is labeled
readyis up for grabs.
Add yourself to the AUTHORS.rst file in an alphabetical fashion. Every contribution is valuable and shall be credited.
If your change is noteworthy, add an entry to the changelog.
No contribution is too small; please submit as many fixes for typos and grammar bloopers as you can!
Always add tests and docs for your code. This is a hard rule; patches with missing tests or documentation won’t be merged – if a feature is not tested or documented, it doesn’t exist.
Write good commit messages.
If you have something great but aren’t sure whether it adheres – or even can adhere – to the rules above: please submit a pull request anyway!
In the best case, we can mold it into something, in the worst case the pull request gets politely closed. There’s absolutely nothing to fear.
Thank you for considering to contribute to