I love your input! and 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
I use github to host code, to track issues and feature requests, as well as accept pull requests.
I Use Github Flow, So All Code Changes Happen Through Pull Requests
Pull requests are the best way to propose changes to the codebase (I use Github Flow). I actively welcome your pull requests:
- Fork the repo and create your branch from
master
. - Give your branch a clear descriptive name and do your changes there.
- If you've changed the HTTP APIs, update the documentation.
- Issue a pull request against a branch of the same name in the main repo.
- Clearly describe your changes and the reason for them in the pull request.
In short, when you submit code changes, your submissions are understood to be under the same License that covers the project.
Report bugs using Github's issues
We use GitHub issues 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!
- 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.
- 4 spaces for indentation rather than tabs in the main code
By contributing, you agree that your contributions will be licensed under its GNU Lesser General Public License v2.1
This document was adapted from the open-source contribution guidelines for Facebook's Draft