Add section about getting try job access
Bug: webrtc:12298
Change-Id: I305ba0e60513a936deece641032a0bc1490994d8
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/236345
Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
Reviewed-by: Harald Alvestrand <hta@webrtc.org>
Commit-Queue: Artem Titov <titovartem@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#35269}
diff --git a/g3doc/become_a_committer.md b/g3doc/become_a_committer.md
index f2c9844..8045c06 100644
--- a/g3doc/become_a_committer.md
+++ b/g3doc/become_a_committer.md
@@ -1,7 +1,26 @@
-# How to become WebRTC committer
+# How to get tryjob access or become WebRTC committer
<?% config.freshness.owner = 'titovartem' %?>
-<?% config.freshness.reviewed = '2021-07-05' %?>
+<?% config.freshness.reviewed = '2021-10-26' %?>
+
+## Overview
+
+There are two levels of WebRTC contributors access:
+
+1. Tryjob access - permits contributor to run tests for their changes using
+ WebRTC infrastructure
+2. WebRTC committer rights - permits to submit changes to the WebRTC code base.
+ This includes tryjob access.
+
+## Getting tryjob access
+
+To get tryjob access applicant has to do a contribution around 10-20 CLs to the
+WebRTC code base. After that, they should file a bug using
+[Get tryjob access template][7], specifying the email which was used for the
+contributions and to which access will be granted, and listing contributed CLs.
+
+The access will be granted when the ticket is resolved by one of the project
+members. In case of rejection the explanation will be provided.
## WebRTC committer duties
@@ -62,3 +81,4 @@
[4]: https://developers.google.com/open-source/cla/individual?hl=en
[5]: https://google.github.io/styleguide/cppguide.html
[6]: https://bugs.chromium.org/p/webrtc/issues/entry?template=Become+WebRTC+committer
+[7]: https://bugs.chromium.org/p/webrtc/issues/entry?template=Get+tryjob+access
