
If you have any questions about the process you can ask in our community Discord or by emailing a maintainer. If you're interested we've documented the process which includes finding an issue with a bounty, completing the issue, and submitting an expense to Open Collective to be paid. Help us understand why and get paid $300! - Quentin Pradet 🇪🇺 June 6, 2022 Major distributions ship Python with OpenSSL 3.0 though, which breaks urllib3 tests. urllib3 maintainer Quentin Pradet tweeted about a single issue with a bounty and ended up generating enough interest for 3 new contributors to open 5 new pull requests! We’ve also already paid out for two bounties.ĬPython has experimental support for OpenSSL 3.0 with "known performance regressions, missing features and potential bugs". We’ve already seen early success from the “ soft launch” of our bounty program. Bounties are paid out through our public Open Collective balance.
#Openssl github series
Each issue includes a series of tasks that must be completed in order to receive the bounty.

Don't worry if you're not an existing contributor - new contributors are welcome and encouraged!īounty amounts start at $100 for small issues and most issues are $300 or more.


The bounty program works by marking issues with bounty amounts we’re willing to pay for anyone to complete an issue. Our bounty program is hoping to spur interest from the community in the urllib3 project and fairly pay contributors for their time and experience. We’ve recognized that one of the biggest challenges to shipping v2.0 is not having enough time to devote to contributions. The urllib3 team is excited to announce the start of our bounty program!
