Skip to content

GOVERNANCE.md

Latest commit

 

History

History
100 lines (73 loc) · 1.7 KB

GOVERNANCE.md

File metadata and controls

100 lines (73 loc) · 1.7 KB

RootlessNet Governance

How decisions are made in the RootlessNet project.

Principles

  1. Decentralization: No single point of control
  2. Transparency: All decisions public
  3. Meritocracy: Contribution-based influence
  4. Stability: Protocol changes require broad consensus

Roles

Contributors

  • Submit issues and PRs
  • Participate in discussions
  • Help with documentation

Committers

  • Merge PRs
  • Triage issues
  • Review code
  • Earned through consistent contribution

Maintainers

  • Protocol decisions
  • Release management
  • Security response
  • Strategic direction

Steering Committee

  • Major governance decisions
  • Conflict resolution
  • Long-term vision
  • 5 members, 2-year terms

Decision Making

Code Changes

  • Minor: Any committer can merge
  • Major: Two maintainer approvals
  • Breaking: RFC + steering committee

Protocol Changes (RFCs)

  1. Proposal submitted
  2. 30-day discussion period
  3. Maintainer review
  4. Steering committee vote
  5. 60-day implementation period

Voting

  • Simple majority for most decisions
  • 2/3 majority for protocol changes
  • Unanimity for governance changes

RFC Process

RFC Lifecycle:
Draft → Review → Final Comment → Accepted/Rejected → Implemented

RFC Template

  • Summary
  • Motivation
  • Detailed Design
  • Drawbacks
  • Alternatives
  • Unresolved Questions

Conflict Resolution

  1. Discussion in issue/PR
  2. Ping maintainers
  3. Steering committee mediation
  4. Community vote (last resort)

Amendments

This governance document can be amended:

  • Proposal with rationale
  • 60-day discussion
  • Steering committee unanimous approval
  • Community notification

Last Updated: December 2024