blob: d804d0c0432bdd1c1f92e37c80e426554dc1b9e5 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
# Chromium Sheriffing
Author: ellyjones@
## Sheriffing Philosophy
Sheriffs have one overarching role: to ensure that the Chromium build
infrastructure is doing its job of helping developers deliver good software.
Every other sheriff responsibility flows from that one. In priority order,
sheriffs need to ensure that:
1. **The tree is open**, because when the tree is closed nobody can make
progress;
2. **New test failures are not introduced**, because they weaken our assurance
that we're shipping good code;
3. **Existing test failures are repaired**, for the same reason
As the sheriff, you not only have those responsibilities, but you have any
necessary authority to fulfill them. In particular, you have the authority to:
* Revert changes that you know or suspect are causing breakages
* Disable or otherwise mark misbehaving tests
* Use TBRs freely as part of your sheriffing duties
* Pull in any other engineer or team you need to help you do these duties
## How to be a Sheriff
To be a sheriff, you must be both a Chromium committer and a Google employee.
For more detailed sheriffing instructions, please see the internal documentation
at
[go/chrome-sheriffing-how-to](https://goto.google.com/chrome-sheriffing-how-to).
## Contacting the Sheriffs
The currently oncall sheriffs can be viewed in the top-left corner of the
[Chromium Main Console](https://ci.chromium.org/p/chromium/g/main/console). You
can also get in touch with sheriffs using the
[#sheriffing Slack channel](https://chromium.slack.com/messages/CGJ5WKRUH/).
|
