Governance
How decisions are made, who makes them, and how access and releases are protected. Written down so nobody has to guess.
Model
QWED follows a Benevolent Dictator for Life (BDFL) model. The founder, Rahul Dass, has the final say on decisions and works in consultation with the community. QWED currently has a single maintainer.
Roles
BDFL
Rahul Dass
- Strategy and roadmap
- Final call on contested pull requests
- Conflict resolution
- Release management
- Security vulnerability response
Maintainers
None yet besides the BDFL
- Triage issues and pull requests
- Merge uncontested pull requests
- Maintain documentation
- Enforce the code of conduct
Contributors with a sustained record of good work can be invited. Maintainers will be listed here when the role is filled.
Contributors
Anyone
- Open issues and pull requests
- Follow the contributing guide
- Follow the code of conduct
How decisions are made
By consensus where possible. Proposals go to GitHub Issues and Discussions. If consensus can’t be reached, the BDFL decides.
Continuity
A single-maintainer project is a continuity risk, and we say so plainly. No backup maintainer with administrative access has been appointed yet. When one is, they will be named here, along with what they can do if the BDFL is unavailable for more than four weeks.
Access and releases
- Everyone with write access to the repositories or package registries (PyPI, Docker Hub) must use two-factor authentication. It is enforced for the whole QWED-AI organisation on GitHub.
- Hardware keys or authenticator apps are preferred over SMS.
- PyPI packages are published through PyPI Trusted Publishing, with build provenance attestations.
Code of conduct
QWED follows the Contributor Covenant. By taking part, you agree to uphold it. Contributions follow the contributing guide, and the code is licensed under Apache-2.0.
This page follows GOVERNANCE.md in the qwed-verification repository, which is the canonical version.