Skip to content

GOVERNANCE.md

Latest commit

 

History

History
25 lines (16 loc) · 1.16 KB

GOVERNANCE.md

File metadata and controls

25 lines (16 loc) · 1.16 KB
Raw

Community Governance Model

Status: Active | Tracks: #1168 (Q4 goal — Community governance model)

Roles and Authority

  1. Contributor: Submits PRs, opens issues.
  2. Reviewer/Triage: Can review PRs, label issues, and run initial triage.
  3. Maintainer: Has review and merge authority, sets project direction.
  4. Project Lead: Final escalation point for lazy-consensus disputes.

Decision Process

We use a lazy-consensus model. When someone proposes a PR or RFC and nobody raises an objection within 72 hours, we consider it approved. This applies only if CI passes and the change meets our guidelines. If objections arise, the participants must resolve them through discussion. If they cannot reach consensus, the Project Lead resolves the dispute.

RFC Lifecycle Integration

Major architectural changes must go through an RFC process.

  • Draft an RFC document.
  • Open a PR for the RFC.
  • Lazy-consensus applies for adoption.

Per-Repo CODEOWNERS Policy

Each repository must have a CODEOWNERS file that defines who has review and merge authority over specific paths. Nobody can merge code changes without approval from a designated code owner.