QWED

Type to search pages, engines and advisories.

    Looking for API details?Search the docs

    Governance

    Decisions, written down

    How decisions are made, who makes them, and how access and releases are protected. Written down so nobody has to guess.

    QWED follows a Benevolent Dictator for Life (BDFL) model. The founder, Rahul Dass, has the final say and works in consultation with the community. QWED currently has a single maintainer.

    A proposalOpened in Issues or Discussions
    ThenIs there consensus?
    YesThe community’s decision stands
    NoThe BDFL decides

    How decisions are made

    By consensus where possible. Proposals go to GitHub Issues and Discussions.

    Who does what

    • 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

      Open to all

      Anyone

      • Open issues and pull requests
      • Follow the contributing guide
      • Follow the code of conduct

    Continuity, stated plainly

    A single-maintainer project is a continuity risk, and we say so. When a backup maintainer is appointed, they will be named here, along with what they can do if the BDFL is unavailable for more than four weeks.

    Maintainers today
    1
    Backup maintainer
    Not appointed yet
    Plan if the BDFL is away over four weeks
    Named with the backup

    Access and releases

    • Enforced

      Two-factor authentication

      Required for everyone with write access to the repositories or package registries (PyPI, Docker Hub), and enforced for the whole QWED-AI organisation on GitHub.

    • Preferred

      Hardware keys or authenticator apps

      Preferred over SMS for that second factor.

    • In place

      Trusted Publishing

      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.