Agent WranglersMaintainers and governance
Keep two people who can publish, write down who decides and who holds each key, vet people before granting rights and retire unused rights.
- Required 1
- Recommended 5
Required
Keep at least two people who can publish
OSS-12Give at least two maintainers admin rights on the repository, owner rights on every registry package and access to the release process. Each of them has published at least one release in the last 12 months.
Recommended
Write down how decisions are made
OSS-13Keep a
GOVERNANCE.mdthat names the roles and what each may decide. It also says how disputes are settled and how people gain or lose a role.List everyone who holds a key to the project
OSS-14Keep a
MAINTAINERS.mdnaming everyone with write or admin rights on the repository or owner rights on a registry. Add everyone with access to the domain, signing keys or CI secrets. A CI job compares it with the code host every week.Vet a person before giving them release or admin rights
OSS-15Give release, admin or registry rights only after a written nomination that another maintainer approves. The nominee has at least 6 months of reviewed contributions to the project.
Take back rights from people who have gone quiet
OSS-16Remove release, admin and registry rights from anyone with no commit, review or release in the project for 12 months. Thank them by name as emeritus maintainers in
MAINTAINERS.md.Hold the project's accounts in an organisation
OSS-17Keep the repository, the registry namespace, the domain and the chat server in accounts owned by the project, each with at least two admins. Never keep them under one person's private account.
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/open-source/maintainers-and-governance">Agent Wranglers open source maintenance playbook</a>. In code you write, add a comment next to it with the same link.