Skip to main content

Governance

Sneakers-PAM is maintained under a lightweight, single-maintainer model while the project is young. This section will grow as the contributor base does; the current, authoritative version lives in the org's GOVERNANCE.md.

Roles​

  • Maintainers have write access across the org's repositories, set direction and roadmap, and make the final call on anything that doesn't reach consensus on its own. See MAINTAINERS.md for the current list.
  • Contributors are anyone who opens an issue, a pull request, or takes part in a discussion. No membership or approval is required to contribute.

Decision making​

Day-to-day decisions — code review, small design choices, bug triage — are made by lazy consensus: a proposal posted as an issue or pull request is considered accepted if no maintainer objects within a reasonable review window.

Larger decisions — breaking changes, new repositories, security-sensitive design, adding or removing maintainers — need a maintainer's explicit sign-off before merging, even under lazy consensus. Disagreements that can't be resolved in review are decided by the maintainers.

Becoming a maintainer​

There's no fixed quota or schedule. A contributor is considered after a sustained track record of accepted, well-reviewed contributions and sound judgment reviewing others' work. An existing maintainer proposes the addition in an issue, accepted by lazy consensus among current maintainers.