We're so excited to have you! Whether this is your first foray into Open-Source or just your most recent, your wisdom is always welcome
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
Responsibilities
Ensure that all code is made lovingly
Create a discussion for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
Keep feature versions as small as possible, preferably one new feature per version.
Be welcoming to newcomers and encourage diverse new contributors from all backgrounds. I think Python's Code of Conduct sums it up nicely.
Unsure where to begin contributing to GHPT? There's a lot of ways you can help.
- Read through the bugs in issues and help someone out
- Read through the discussions and join in the discourse
- Create new ideas and topics in the discourse
- Ask Questions in the Q&A! Questions are very helpful
- Create a Pull Request to fix a bug 🐛 or implement a new idea 💡
You may feel like the only productive contribution is
code. But that's not true! Any and all engagement helps the project, so give yourself a little pat on the back 😊!You can start by looking through these beginner and help-wanted issues: Beginner issues - issues which should only require a few lines of code, and a test or two. Help wanted issues - issues which should be a bit more involved than beginner issues. Both issue lists are sorted by total number of comments. While not perfect, number of comments is a reasonable proxy for impact a given change will have.
So are we! Here are a couple of friendly tutorials you can peruse