Repository navigation
Governance
The canonical governance document is GOVERNANCE.adoc in main. This wiki page summarises the highlights and links into the deeper content.
Benevolent Dictator For Life (BDFL). Best-fit model for a solo-maintained registry where decision latency matters more than formal consensus. Transitions to consensus-based governance if the active maintainer count exceeds three (per the transition clause in GOVERNANCE.adoc § Transition clause).
| Role | Authority |
|---|---|
| BDFL | Final say on all matters; accepts/declines registrations |
| Maintainer | Commit access; reviews, triages, manages releases |
| Contributor | Opens PRs/issues; no direct commit access |
| Bot | Automated agent (gitbot-fleet); subject to the same review standards as humans |
See MAINTAINERS.adoc for the current maintainer list.
- Routine (CI fixes, dep updates) — any maintainer with commit access
- Version bumps of registered packages — any maintainer, once CI is green
- New package registrations — BDFL approves against the quality bar
- Removals or renames — BDFL + ADR required
- Significant changes (Registry.toml schema, acceptance criteria) — issue discussion first, then PR
Significant technical decisions are recorded as Architecture Decision Records under docs/decisions/ (created on demand — none yet at the time of writing). Each ADR has a status: proposed, accepted, deprecated, superseded, rejected.
Nomination by an existing maintainer to the BDFL, based on:
- Sustained quality contributions (3+ months)
- Familiarity with the estate's RSR standards
- Constructive participation in issue triage and review
- Reliable engagement cadence
See GOVERNANCE.adoc § Becoming a Maintainer for the formal process.
All participants follow the Code of Conduct. The BDFL is the final arbiter in conduct disputes.