Governance
This document describes how the MiningOS project is governed and how decisions are made.
MiningOS is a Tether led open-source project. While the code is publicly available and community contributions are welcome, final decision-making authority rests with the MiningOS core team.
Project Roles
Users
Anyone who uses MiningOS and provides feedback, bug reports, or feature requests.
Contributors
Community members who contribute code, documentation, tests, or other improvements via pull requests or issues.
Contributors do not have merge access.
Maintainers
Maintainers are responsible for reviewing pull requests, maintaining code quality, and ensuring alignment with the project roadmap.
Maintainers may be appointed by the Lead Maintainer.
Lead Maintainer (Technical Lead)
Hemant T is the Lead Maintainer and Technical Lead for MiningOS.
The Lead Maintainer has final authority over:
Pull request approval and merging
Architecture and design decisions
Release planning and versioning
Accepting or rejecting features
Appointing or removing maintainers
If consensus cannot be reached among maintainers, the Lead Maintainer makes the final decision.
Community Manager
Giorgio Rasetto is the Community Manager for MiningOS.
The Community Manager is responsible for:
Managing community communication channels
Moderating discussions and enforcing the Code of Conduct
Supporting contributors during onboarding
Acting as a bridge between the community and the MiningOS core team
Helping define and communicate the project vision and roadmap
The Community Manager does not make technical decisions.
Decision-Making Process
Community members may propose changes via issues or pull requests.
Maintainers review contributions for quality, security, and alignment with MiningOS goals.
The Lead Maintainer has final approval authority on all technical decisions.
Strategic, roadmap, or breaking changes are determined by the MiningOS core team.
Contribution Review Process
All contributions must follow
CONTRIBUTING.md.Pull requests require review by a maintainer.
Final approval and merge is performed by the Lead Maintainer.
The MiningOS team reserves the right to decline contributions that do not align with the project direction.
Inactivity and Removal
Maintainers who become inactive for an extended period or violate project policies may be removed by the Lead Maintainer.
Code of Conduct
All participants are expected to follow the project’s Code of Conduct. Violations are handled by the Community Manager in coordination with the MiningOS core team.
See CODE_OF_CONDUCT.md for details.
Changes to Governance
This governance model may evolve over time. Any changes will be proposed and approved by the MiningOS core team.
Last updated