| Elly Fong-Jones | bbc9206 | 2019-05-29 15:38:03 | [diff] [blame] | 1 | # Chromium Sheriffing |
| 2 | |
| 3 | Author: ellyjones@ |
| 4 | |
| Elly Fong-Jones | bbc9206 | 2019-05-29 15:38:03 | [diff] [blame] | 5 | ## Sheriffing Philosophy |
| 6 | |
| 7 | Sheriffs have one overarching role: to ensure that the Chromium build |
| 8 | infrastructure is doing its job of helping developers deliver good software. |
| 9 | Every other sheriff responsibility flows from that one. In priority order, |
| 10 | sheriffs need to ensure that: |
| 11 | |
| 12 | 1. **The tree is open**, because when the tree is closed nobody can make |
| 13 | progress; |
| 14 | 2. **New test failures are not introduced**, because they weaken our assurance |
| 15 | that we're shipping good code; |
| 16 | 3. **Existing test failures are repaired**, for the same reason |
| 17 | |
| 18 | As the sheriff, you not only have those responsibilities, but you have any |
| 19 | necessary authority to fulfill them. In particular, you have the authority to: |
| 20 | |
| 21 | * Revert changes that you know or suspect are causing breakages |
| 22 | * Disable or otherwise mark misbehaving tests |
| Joey Scarr | 9ded41f | 2020-07-01 04:23:29 | [diff] [blame^] | 23 | * Use TBRs freely as part of your sheriffing duties |
| Elly Fong-Jones | bbc9206 | 2019-05-29 15:38:03 | [diff] [blame] | 24 | * Pull in any other engineer or team you need to help you do these duties |
| 25 | |
| Joey Scarr | 9ded41f | 2020-07-01 04:23:29 | [diff] [blame^] | 26 | ## How to be a Sheriff |
| Elly Fong-Jones | bbc9206 | 2019-05-29 15:38:03 | [diff] [blame] | 27 | |
| Joey Scarr | 9ded41f | 2020-07-01 04:23:29 | [diff] [blame^] | 28 | To be a sheriff, you must be both a Chromium committer and a Google employee. |
| 29 | For more detailed sheriffing instructions, please see the internal documentation |
| 30 | at |
| 31 | [go/chrome-sheriffing-how-to](https://goto.google.com/chrome-sheriffing-how-to). |
