|
| 1 | +# Labels used in the `team` repository |
| 2 | + |
| 3 | +Some labels are setup to make it easier to figure out the status of an issue or PR, and allows |
| 4 | +contributors to filter issues/PRs by labels. |
| 5 | + |
| 6 | +## Labels are currently manually applied |
| 7 | + |
| 8 | +[`triagebot`][triagebot] is not currently set up for the `team` repository, as it would need write |
| 9 | +access (which needs to be tightly controlled). Thus, labels are currently manually applied and |
| 10 | +adjusted. See [threat model](./threat-model.md). |
| 11 | + |
| 12 | +## Meaning of labels |
| 13 | + |
| 14 | +- `needs-{team-repo,infra}-admin-review`: needs one of the [`infra-admins` or `team-repo-admins` or |
| 15 | + one from both to review (and approve/reject)][team-repo-rules]. |
| 16 | +- `needs-team-lead-review`: needs a relevant team or Working Group (WG) or Project Group (PG) lead |
| 17 | + to approve. |
| 18 | +- Statuses: |
| 19 | + - `S-waiting-on-{author,review,team}`: self-evident |
| 20 | + - `S-has-concerns`: outstanding concerns that must be addressed |
| 21 | + - `S-blocked`: blocked on *something* |
| 22 | +- Team labels: only `T-{infra,leadership-council}`, the latter is intended to help council members |
| 23 | + to see what `team` PRs would need Council feedback or concerns the Council somehow. |
| 24 | +- `E-{easy,medium,hard}` and `E-help-wanted`: call-for-participation labels copied from |
| 25 | + `rust-lang/rust`. |
| 26 | +- `needs-triage`: someone should try to figure out what the issue/PR needs/is/affects/is blocked on. |
| 27 | +- `needs-council-fcp`: something that requires the Council to FCP (outside `team` repo as rfcbot |
| 28 | + isn't enabled). |
| 29 | + |
| 30 | + |
| 31 | +[triagebot]: https://forge.rust-lang.org/triagebot/index.html |
| 32 | +[team-repo-rules]: |
| 33 | + https://forge.rust-lang.org/infra/team-maintenance.html#rules-for-changes-to-team-repo |
0 commit comments