WebRTC committers are responsible for keeping WebRTC codebase in a good shape including, but not limited to the following aspects:
Whenever a committer sets
Code Review +1 label on the CL, they approve that the CL fulfills WebRTC style guides, language mastery, testability and documentation. Being a committer means being responsible for the WebRTC codebase health and code quality.
To write code in WebRTC you don‘t need to be a committer (also see FAQ), but to submit code to WebRTC you do. So if you don’t plan to work on the WebRTC codebase regularly, you can ask other committers through code review to submit your patches, but if you are going to work in the WebRTC codebase, then it's recommended to apply for WebRTC committer rights obtaining process.
If you are going to write in C++ make yourself familiar with with C++ style guides:
Create a ticket to obtain WebRTC committers rights in Monorail.
TODO: add link to the template.
Pick a mentor among WebRTC committers, who will review your CLs. For C++ authors, the mentor will also look for C++ readability skills. It's recommended to ask someone who is familiar with the code base which you will be working on (you can check OWNERS files to find such person). Otherwise you can reach out to committers mailing list <firstname.lastname@example.org>.
Send CLs to the mentor for review and attach them to the created ticket.
When the mentor decides that you are ready (for C++ authors their C++ readability skills are good enough), they will send a proposal for granting WebRTC committer rights to the reviewing committee mailing list to review. If the proposal will be approved, then committer rights will be granted. Committee members will have up to 5 business days to answer. In case of rejection detailed feedback on what aspects should be improved will be provided.
Also as any contributor you must sign and return the Contributor License Agreement