A track maintainer is someone who is a member of the track's GitHub team. Becoming a member of a track team is invitation only.
If you'd like to become a track maintainer, please open a topic on the forum.
The are five maintenance categories:
wip-track
unmaintained
maintained-solitary
maintained-autonomous
maintained
A tracks' maintenance category is determined by three variables:
cross-track-maintainers
GitHub teamTo determine the maintenance category, find the first category that matches the track from this table:
Category | Active? | Number of maintainers | Number of cross-track maintainers |
---|---|---|---|
wip-track | No | Any | Any |
unmaintained | Yes | 0 | 0 |
maintained-autonomous | Yes | > 0 | = Number of maintainers |
maintained-solitary | Yes | 1 | 0 |
maintained | Yes | > 1 | < Number of maintainers |
The maintenance category is used to set the track's GitHub repo(s) permission(s).
Category | Requires PR | Requires PR approval | Cross-track team reviews |
---|---|---|---|
wip-track | No | No | No |
unmaintained | Yes | Yes | Yes |
maintained-solitary | Yes | Yes | Yes |
maintained-autonomous | Yes | No | No |
maintained | Yes | No | No |
The wip-track
category is the only category that allows maintainers to push to main
.
Tooling repos will always require PR approval, as their contents are protected via a CODEOWNERS file.