Ways of quickly describing your governance process to others.
These are just simple ways of talking about the governance in your open source project, in particular. They have been informed by ongoing work at:
We suggest you copy the paragraphs below into any of:
Governance
Governance
Governance.md
file. This repository works through the BDFL – Benevolent Dictator For Life - model. That means that a single maintainer, @USERNAME
, holds all of the admin keys and write access for this repository. Other users are encouraged to open issues, submit Pull Requests, and to ask for recognition as maintainers, but all decisions ultimately lie with the core maintainer.
This maintainer is open to/not open to others joining on the admin team for this repository.
This repository is abandoned. The core maintainer has expressed no more desire for maintaining it. However, they are open to others who have shown their expertise taking over the process.
This repository is run by a single core committee, who all have write-access and a say in technical and governance decisions. Members of the committee include @USER1, @USER2, @USER3
. Other users are encouraged to open issues, submit Pull Requests, and to ask for recognition as maintainers, but all decisions ultimately lie with the core maintaining group.
This maintainer is open to/not open to others joining on the admin team for this repository.
{
"specification": "governance.md",
"pattern": "Core committee",
"members": {
...
}
}
# Please add to this TODO
Please do contribute! This is just a stub of an idea.
MIT