Skip to content

GOVERNANCE.adoc

Latest commit

 

History

History
109 lines (70 loc) · 1.85 KB

GOVERNANCE.adoc

File metadata and controls

109 lines (70 loc) · 1.85 KB

eTMA Handler Governance

Table of Contents

1. Overview

eTMA Handler follows a BDFL (Benevolent Dictator For Life) governance model with a core team structure.

2. Roles

2.1. BDFL

The BDFL has final authority on project decisions:

  • Set project direction

  • Resolve disputes

  • Appoint core team members

  • Must maintain succession plan

2.2. Core Team

Core team members (see MAINTAINERS.md):

  • Merge permissions

  • Release management

  • Security response

  • Architecture decisions

2.3. Contributors

All levels as defined in CONTRIBUTING.adoc (TPCF Perimeters 1-3).

3. Decision Making

3.1. Lazy Consensus

Most decisions use lazy consensus:

  1. Proposal made (issue/PR/discussion)

  2. Review period (72 hours standard, 14 days for breaking changes)

  3. No blocking objections = accepted

3.2. Voting

When consensus fails:

  • Core team votes

  • Simple majority required

  • BDFL breaks ties

  • 7-day voting period

4. Succession Planning

4.1. BDFL Succession

  • Designated successor documented

  • Triggers: resignation, 6-month inactivity, ⅔ removal vote

  • 30-day transition period

4.2. Core Team

  • Nomination by existing Core member

  • 14-day discussion

  • BDFL approval

  • Emeritus status for departing members

5. Release Management

5.1. Versioning

Semantic Versioning (SemVer):

  • MAJOR: Breaking changes

  • MINOR: New features

  • PATCH: Bug fixes

5.2. Release Authority

  • Patch: Any Core member

  • Minor: Two Core members

  • Major: Core consensus + BDFL

6. Financial Transparency

See FUNDING.yml for funding sources.

Funds used for:

  • Infrastructure

  • Security audits

  • Documentation

Quarterly reports in Discussions.

7. Amendments

Changes to this document require:

  1. RFC with 30-day discussion

  2. ⅔ Core team vote

  3. BDFL approval

Last updated: 2024-12-01