👍 🎉 Thank you so much for taking the time to contribute! 🎉 👍
The following is a set of guidelines for contributing to DjangoCon US 2017.
Start looking through the Issues and watch out for any issues with the yellow label up-for-grabs. Issues marked with this label haven't been assigned to anyone yet and we would love for you to work on them.
Here's a quick guide to help you understand what the different difficulty labels mean that you will find while looking through the issues:
difficulty: easy: Fixing this issue doesn't require a lot of time or programming knowledge. This would be a great issue for someone new to programming or open source to work on.
difficulty: medium: This is an issue which requires more time or programming knowledge than a difficulty: easy issue but you don't have to be a programming expert to fix it.
difficulty: hard: This issue probably requires some time or a good bit of programming knowledge and could be a challenge, but this shouldn't keep you from trying to submit a patch for it 😉
If you find any bugs, it would be great if you would let us know so we can look into it. You can do so by creating an issue. If you don't know how to create an issue, please follow these instructions. Screenshots and notes for how you encountered the bug are really helpful when reporting bugs!
After you've created a patch that fixes an issue, please submit a pull request for it. If you're not sure how to create a pull request, please follow these instructions. In general we'd like to ask you to please target the development branch with your pull requests.
You're welcome to review issues and pull requests, provide feedback, and answer questions. Please remember to be friendly and respectful when commenting on issues or pull requests, and always follow our Code of Conduct. It's okay for people to make mistakes and ask questions!
If you have a question or need help, please leave a comment on the issue you have a question about or are working on. We will try to answer your question and help you as soon as possible.
As a contributor, you can help us keep the Django community open and inclusive. Please read and follow our Code of Conduct, and report unacceptable behavior to {{site.coc_email}}.