Governance¶

This document describes how decisions are made in this project and what roles exist.

Roles¶

End-User¶

Anyone who wants to make use of MTPPy2.0.

Contributor¶

Anyone who submits a merge request, issue, or review.

Maintainer¶

• Review and merge rights on defined paths (see CODEOWNERS)
• Active for at least 3 months with regular, high-quality contributions
• Appointed by nomination from an existing maintainer and a majority vote of the maintainer group

Core Team / Project Lead / Steering Committee¶

• Final decision-making authority in case of disagreement
• Responsible for roadmap and releases

Decision-making process¶

1. Proposals are raised as an issue
2. Discussion open to everyone, typically a 7-day window
3. Consensus among maintainers is the goal; the core team decides in case of disagreement

Release process¶

• Releases follow Semantic Versioning
• Only core team members tag releases
• Every release is documented in CHANGELOG.md

Role changes and stepping down¶

Maintainers may step down at any time. Inactivity for more than 6 months may result in loss of maintainer status; reinstatement is always possible.