编写开源项目治理规范文档
根据项目现有决策与维护方式起草治理文件,明确角色权限、决策流程、资产交接和待确认事项。
完整提示词
<context>
Governance documents fail in two ways: they describe an imaginary democracy while one person still decides everything, or they copy a large foundation's process onto a three-person project that will never hold a vote. A useful GOVERNANCE.md writes down what already happens, then fixes the gaps that hurt projects in practice: who breaks a deadlock, how someone becomes or stops being a maintainer, what happens when the lead disappears, who controls the repository, package names, domain and money, and how to stop one employer from quietly controlling the project. Common models are a single lead (often called BDFL), a maintainer council deciding by lazy consensus with a vote as a fallback, and a steering committee over several teams. Most small projects need the first or second, plus a clear succession rule.
Project:
<project>
{{project}}
</project>
{{#trigger}}Why now: {{trigger}}{{/trigger}}
</context>
<task>
1. Describe how the project works today from the facts given: who decides what, who holds which access, and where the single points of failure are (one person with publish rights, one employer with most maintainers, no written tie-break). If key facts are missing, list them and state the assumption you make.
2. Recommend a model sized to the project, with one sentence on why the bigger or smaller alternative is not right yet{{#trigger}}, and how it addresses why governance is needed now{{/trigger}}.
3. Write GOVERNANCE.md covering: roles and what each may do; how decisions are made (lazy consensus with a stated waiting period, what needs explicit approval, who breaks ties); how people join a role, step down, become emeritus, or are removed for inactivity or conduct; employer diversity rules if relevant; who holds the project's assets (repository, package names, domain, trademarks, funds) and how they are handed over; how the code of conduct is enforced and by whom; how this document is changed.
4. List the concrete changes needed to make the document true (access to add or remove, a MAINTAINERS file, a funding host, a second person with publish rights).
5. List open questions the maintainers must answer together before publishing.
</task>
<constraints>
- Do not describe a process the project does not follow or has not agreed to adopt. Where you propose something new, mark it "proposed" so maintainers can discuss it.
- Keep it short enough to read in five minutes; a small project's governance should fit on one page.
- Do not invent foundation rules, legal entities or trademark registrations. If the project holds money or trademarks, say who should check the legal side.
- Every role that can block a decision needs a named way to resolve deadlock and a way to leave.
</constraints>
<output_format>
## How the project works today
Bullets, including single points of failure.
## Recommended model
Two or three sentences.
## GOVERNANCE.md
The full file in a fenced markdown block, with "proposed" marked inline.
## Changes to make
A table: Change | Who | Why.
## Open questions
Numbered.
</output_format>可替换内容
- {{project}}
- {{#trigger}}
- {{trigger}}
- {{/trigger}}
分类与标签
办公效率、开源项目、团队治理、协作规范