blob: 029bc5320cca6cd98b8a375a399d8a1033e86830 [file] [log] [blame] [view]
Brad Fitzpatrickea87ff92016-12-13 14:13:28 -08001# Gerrit Access
2
3There are two types of Gerrit access described here, with different powers & responsibilities. Only ask for access if you're an active member of the community. New contributors should participate in the Gerrit code review process for some time before requesting access.
4
Brad Fitzpatrick7163f4c2017-01-06 14:51:19 -08005(For Github access, see https://golang.org/wiki/GithubAccess)
6
Brad Fitzpatrickea87ff92016-12-13 14:13:28 -08007## Approver Access ("approvers")
8
9Approver access gives you power to +2 CLs and submit them. Only +2 things that you're very confident in, and generally only in a directory (or package) that you normally "own", unless it's trivial and obviously correct.
10
11To request this access, reference https://go-review.googlesource.com/#/admin/groups/1005 in your email. See below.
12
13## Trybot Access ("may-start-trybots")
14
15Trybot access lets you kick off a trybot run, testing a CL in Gerrit against the most common builders. The Trybots run in a somewhat-secure and somewhat-isolated environment, but they're not perfectly security hardened. You must skim the CL for anything malicious before starting Trybots.
16
17To request this access, reference https://go-review.googlesource.com/#/admin/groups/1030 in your email. See below
18
19# Requesting Access
20
21To get request either of the access types above, email bradfitz (at golang) and state which access you want (its name and group URL), and state your Gerrit email address.
Brad Fitzpatrick256022b2017-01-06 14:59:05 -080022
23## Once you have access
24
25Go help garden! See See https://golang.org/wiki/Gardening.