Governance

Facet is an open source project led by its maintainer community and intended to be run in the open with clear decision-making and contribution paths.

Project leadership

• Project lead: @Tim-Maes
• Maintainers: Contributors with ongoing responsibility for reviewing changes, triaging issues, shaping roadmap decisions, and keeping releases healthy.
• Contributors: Anyone who reports bugs, proposes ideas, improves documentation, reviews code, or submits pull requests.

How decisions are made

The project lead is responsible for final decisions when consensus cannot be reached. Day-to-day decisions should happen in the open through issues, pull requests, and discussions whenever practical.

Maintainers are expected to:

• Keep technical discussions respectful, transparent, and focused on project health.
• Prefer documented decisions over private coordination.
• Review contributions in a timely and constructive way.
• Balance stability, usability, performance, and maintainability when evaluating changes.

Contribution intake

Facet accepts contributions through GitHub pull requests. The expected path is:

1. Open an issue or discussion for bugs, larger features, or design changes.
2. Agree on scope before investing in substantial implementation work.
3. Submit a pull request with tests and documentation updates when behavior changes.
4. Address review feedback before merge.

Maintainers may decline changes that conflict with project direction, break compatibility expectations, reduce reliability, or lack sufficient tests or documentation.

Committer and maintainer selection

The project aims to grow maintainership deliberately and transparently.

Contributors may be invited to become committers or maintainers when they consistently:

• Submit high-quality changes across multiple pull requests.
• Participate constructively in reviews and community discussions.
• Demonstrate good judgment around compatibility, testing, and project direction.
• Follow the Code of Conduct and help reinforce healthy community norms.

New maintainers are selected by the project lead, ideally with input from existing maintainers, and are expected to earn trust gradually before receiving broader repository permissions.

Release stewardship

Maintainers are responsible for keeping the project releasable. That includes:

• Reviewing breaking changes carefully.
• Ensuring CI stays healthy.
• Publishing documentation for notable user-facing changes.
• Triaging regressions and security issues promptly.

Governance changes

Material changes to this document should be proposed through a pull request so the community can review them in the open.