返回提示词目录第 1177 页

编写开源社区行为准则

结合项目空间与响应人员信息,起草包含举报渠道、分级处置和利益回避机制的行为规范文档。

完整提示词

<context>
A code of conduct is only as good as its enforcement section. Most projects copy the Contributor Covenant and leave the contact as a placeholder, or point reports to a single maintainer who may be the person being reported, so the document signals safety it cannot deliver. What makes one work: a reporting route that reaches more than one person and has an alternative when a responder is involved; a clear scope (project spaces, and when behaviour elsewhere counts); a graduated enforcement ladder (correction, warning, temporary ban, permanent ban) so responses are proportionate and predictable; a promise of confidentiality that the team can actually keep; and responders who have agreed to the job. Using a widely known template is better than writing a custom one, because people recognise it and it has been tested; adapting means filling it in honestly, not rewriting it. If the project belongs to a foundation or company with its own code, the project usually adopts that one and only adds local contacts.

Project:
<project>
{{project}}
</project>
{{#responders}}Responders: {{responders}}{{/responders}}
</context>

<task>
1. Recommend a template: the parent organisation's code if one exists, otherwise the current Contributor Covenant or another widely used code, and say why. Name the version you are basing it on and tell the maintainer to check it against the published text.
2. Write the CODE_OF_CONDUCT.md: pledge and standards kept close to the template, scope fitted to the project's real spaces (repository, chat, forum, events, official social accounts, representing the project elsewhere), and the enforcement ladder with what each step means here.
3. Write the reporting section with real routes from the responders given: a shared address or private form reaching at least two people, what to include in a report, what happens next and roughly when, confidentiality and its limits, and an alternative route when a responder is involved or the project has only one maintainer.
4. Add conflict-of-interest handling: responders step aside from reports involving themselves or close collaborators.
5. List what must be true before publishing: responders have agreed, the address works and is monitored, the file is linked from README and CONTRIBUTING, and event or chat spaces point to it.
6. Write short responder notes: first-response steps and where to record decisions, pointing to a fuller report-handling process.
</task>

<constraints>
- Do not invent contact addresses or names. Use [REPORT EMAIL] or [RESPONDER NAMES] placeholders where the input does not give them, and list them under Before you publish.
- Keep the template's substance; do not water down standards or remove the enforcement ladder to make the document shorter.
- Do not promise response times or confidentiality the stated team cannot keep.
- If there is only one maintainer, say plainly that a single-person reporting route is weak and suggest a realistic alternative (a trusted outside person, the hosting foundation, a fiscal host).
</constraints>

<output_format>
Use the contract's section headings in order. Put the full code of conduct in a fenced markdown block. Before you publish as checkbox lines. Responder notes as a numbered list of no more than eight steps.
</output_format>

可替换内容

  • {{project}}
  • {{#responders}}
  • {{responders}}
  • {{/responders}}
  • [REPORT EMAIL]
  • [RESPONDER NAMES]

分类与标签

内容创作、开源社区、行为规范、举报流程、社区治理

前往 AI 图片创作