We love your input! We want to make contributing to this project 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
- Becoming a maintainer
We use github to host code, to track issues and feature requests, as well as accept pull requests.
We Use Github Flow, So All Code Changes Happen Through Pull Requests
Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:
- Fork the repo and create your branch from
master
. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
Report bugs using Github's issues
Report a bug by opening a new issue.
A good example from Craig Hockenberry.
Great Bug Reports tend to have:
- A quick summary and/or background.
- Steps to reproduce:
- Be specific!
- Give sample code if you can, so we can reproduce what you was seeing.
- 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).
- 4 spaces for indentation rather than tabs.
- You can try running
python -m flake8
to check your style.
By contributing, you agree that your any contributions you make will be licensed under the MIT Software License. Feel free to contact the maintainers if that's a concern.
- https://gist.github.com/briandk/3d2e8b3ec8daf5a27a62
- Open-source contribution guidelines for Facebook's Draft