The Supporters of Chromium-Based Browsers initiative is keeping Chromium healthy by rewarding the engineers fixing the bugs. So how do we select the bugs? And what makes a project a strong candidate for financial support?
How are bugs selected?
The Bug Bounty Program has a “hot list” containing bugs which need to be fixed. These bugs are categorized into small, medium, and large issues:
- Large Issues are high-impact bugs with broad user or developer visibility. Reward: $20,000
- Medium issues are moderate-impact issues. Reward: $5,000
- Small issues are targeted fixes with clear user benefit. Reward: $1,000
Anyone who has edit bug access can tag and nominate interesting or important bugs that they’d like to see added to the hot list. It is then down to the SoCBB Steering Committee to review the proposed candidates to ensure they meet the criteria, assess appropriate sizing, and ensure eligibility. Once approved, the bug gets added to the hot list for developers to work on.
What makes a good funded project?
For a larger funded project to be accepted, it needs to tick the following boxes:
- Improves broad code health or interoperability within Chromium and its dependencies.
- Addresses web developer pain points (fundamentals, performance, reliability, accessibility, security).
- Benefits multiple embedders – anything benefiting only a single browser is out of scope
- Through the RFP Program, the strategic goal is to find and fund highly skilled independent developers who have the inclination to dive deep into browser architecture. Meanwhile, hobbyists can focus on fixing bugs on the Bug Bounty Program hot list.
How to get involved
We are on a mission to improve the Chromium ecosystem by fixing one bug at a time. If you have the skills to fix bugs, we have the resources to back you:
If you are a Developer wanting to get paid to fix Chromium, learn more here.
If you are a Vendor looking for your next high-impact project, learn more here.