Governance
GOVERNANCE.md – roles, decision process
Як використовувати: Projects with multiple maintainers. The tie-break rule is the part that prevents permanent deadlock.
Перегляд
Governance
Who decides what in [project], and how decisions get made.
Roles
| Role | Who | Responsibility |
|---|---|---|
| Maintainer | @name, @name | Merge rights, releases, direction |
| Committer | @name | Write access to [scope] |
| Contributor | anyone | PRs, issues, discussion |
| Lead | @name | Tie-breaks when consensus fails |
Decision making
- Trivial (typos, small fixes): any maintainer merges
- Standard (features, fixes): lazy consensus – proposal stays open N days; silence means consent; objections are resolved or escalate
- Major (breaking changes, new dependencies, architecture): requires an RFC; the outcome is recorded as a decision record
- Deadlock: the lead decides after hearing objections; the decision and its rationale are documented
Becoming a maintainer
Sustained contributions -> nomination by a maintainer -> lazy consensus of existing maintainers over N days.
Maintainers step down by announcing it. Maintainers inactive for N months move to emeritus status by consensus.
Changes to this document
Amendments require an RFC and maintainer consensus.
Related documents
- Conduct: CODE_OF_CONDUCT.md
- Security reports: SECURITY.md
- License: LICENSE