Roles and Responsibilities
August 15, 2026 ยท View on GitHub
Chinese | English
Roles describe work, not status. Access is scoped to the repository or asset where the responsibility exists.
| Role | Typical evidence | Permission scope | Review |
|---|---|---|---|
| Participant | Questions, feedback, attendance | Public participation | None |
| Contributor | Accepted contribution | Normal contributor access | Ongoing |
| Triager | Sustained issue/discussion help | Triage in named repositories | 90 days during trial |
| Repository Maintainer | Sustained technical ownership | Named repository only | 90 days during trial |
| Steward | Community process and records | Defined community files/process | 30-day trial |
| Compatibility Coordinator | Upstream change coordination | Compatibility records, not project code by default | 30-day trial |
| Security/Conduct Contact | Trusted sensitive intake | Need-to-know case access | Per case and 30-day trial |
| Emeritus | Former active responsibility | No default sensitive access | On request |
During the trial, advancement requires public evidence, one non-conflicted sponsor, a defined scope, least privilege, and a review date. Use role-template.md. Sensitive-case reviewers must be different from the original decision-maker.