Governance

mkdocs-source-links uses a maintainer-led governance model appropriate for a small open-source library.

Decision-making

Area	How decisions are made
Day-to-day code changes	Pull requests reviewed by a maintainer; merged when CI passes and the change aligns with project scope
Releases	Listed maintainers cut semver releases per Contributing
Security	Coordinated disclosure per Security policy; maintainers decide fix timing and advisory publication
Dependencies	Dependabot PRs reviewed by maintainers; Critical/High CVEs block merge per Security policy
Escalated access	Documented vetting process in Maintainers; requires merged PR before grants
Scope and roadmap	Roadmap states 12-month intent; significant scope changes discussed in GitHub Issues before large PRs

The project owner and listed maintainers make final decisions when consensus is not reached. Disputes are resolved through good-faith discussion in the PR or issue; unresolved technical disagreements defer to maintainer judgment.

Roles

Roles, responsibilities, and who holds them are documented in Maintainers.

Contribution and conduct

Contributors follow Contributing. Community behavior is governed by Code of conduct.

Changes to governance

Updates to this file, Maintainers, or Roadmap require a pull request reviewed and merged by a maintainer, same as code changes.