TestAtlas Governance
TestAtlas is maintained in the open. Governance exists to keep decisions understandable, contributions fair, and the quality bar stable as the project grows.
The project standards are defined in PROJECT_CONSTITUTION.md. This document explains how people apply them.
Roles
Contributors
Contributors propose improvements, report problems, review work, and share practical knowledge. Any person can contribute. Contributors are expected to follow the constitution, style guide, and contribution process.
Reviewers
Reviewers assess changes for accuracy, clarity, scope, maintainability, and learner value. A reviewer does not need to agree with every stylistic choice; feedback should focus on changes that materially improve the project.
Maintainers
Maintainers are responsible for the health of the repository. They guide the structure, review or assign reviews, manage releases and automation, moderate discussions, and make final decisions when consensus is not reached.
Maintainers must explain decisions that significantly affect contributors, public content, or repository architecture.
Decision-making
Start with discussion and aim for informed consensus. Decisions should be based on evidence, practical experience, the learner problem being solved, and long-term maintenance cost.
When options differ materially, assess them in this order:
- Best Practice
- Scalability
- Maintainability
- Contributor Experience
- Learner Experience
Record the rationale for major decisions in the issue, pull request, or a dedicated decision record when the decision has broad or lasting impact.
If consensus is not possible within a reasonable time, maintainers make the final decision. The decision must be documented and remain open to reconsideration when new evidence appears.
Review and merge policy
Substantive changes require at least one maintainer or authorized reviewer approval before merge. A contribution author must not be the only reviewer of their own substantive change.
Changes to the constitution, governance, repository architecture, shared content patterns, or licensing require review by at least two maintainers when that maintainer group exists. Until then, those changes require an explicit documented decision by the project owner.
Reviewers should verify the applicable standards in the constitution and style guide. Maintainers may merge minor mechanical corrections without full review when the change has no effect on meaning, structure, or behaviour.
Maintainer selection and removal
Maintainers are selected based on sustained, high-quality contributions; sound judgment; constructive collaboration; and willingness to take responsibility for long-term stewardship.
A maintainer may step down at any time. Removal is considered when a maintainer repeatedly violates project standards, neglects responsibilities, or harms the community. The project owner or a majority of the remaining maintainers makes and documents the decision, while respecting privacy where needed.
Conflict resolution
Address disagreements early and focus on the work. Start in the relevant issue or pull request. If that does not resolve the issue, ask a maintainer for a decision.
Harassment, discrimination, threats, or deliberate bad-faith behaviour are not acceptable. Maintainers may limit participation to protect contributors and the project.
Changing this governance model
Governance should evolve as the contributor community grows. Proposed changes need a clear problem statement, the intended outcome, trade-offs, and review under the policy above. They must remain consistent with the constitution.