规划开源项目许可证变更
梳理贡献者权利与授权障碍,拟定同意征集、代码处置和发布清单,并整理律师咨询问题。
完整提示词
<context>
A project can only relicense code its owners hold the rights to. Without a contributor agreement that grants the project broad rights, every contributor (or their employer, for work done on the job) keeps copyright in their contribution, so changing the licence needs their consent, or their code must be removed or rewritten. Whether a tiny contribution is protected by copyright at all is a legal judgement that varies by country. Some moves need less: code under a permissive licence can often be included in a project under a more restrictive one while keeping the original notices, which is different from relicensing it. Past releases stay available under the old licence forever, so anyone may fork the last version. Moving from open source to a source-available licence often triggers forks and lost trust, and the result should not be described as open source.
{{> guardrails/professional-limits}}
Project:
<project>
{{project}}
</project>
{{#contributors}}
Contributors:
<contributors>
{{contributors}}
</contributors>
{{/contributors}}
</context>
<task>
1. Can you relicense: state the goal, whether the change is relicensing or something simpler (adding a licence to new code, dual licensing, an exception), what the CLA or DCO in place does and does not allow, and the main obstacle. Give a provisional answer with its assumptions.
2. Copyright holders: explain how to build the list from version history (authors of surviving code, not just commit counts), how employers own work done on company time, and how to treat bots, generated files and vendored third-party code{{#contributors}}, applying this to the summary given{{/contributors}}.
3. Consent plan: the request message (what changes, why, what you are asking them to agree to, how to answer), how to record consent in a durable, public or verifiable way, deadlines, reminders, and how to find people who have moved on.
4. Code you cannot clear: options per contributor who refuses or cannot be reached (remove, rewrite by someone who has not studied the original closely, or keep that part under the old licence if compatible), with the effort each implies.
5. Change checklist: LICENSE file, SPDX identifiers and headers, package metadata, notices for third-party code, docs, the release where the change takes effect, and a note that earlier releases keep the old licence.
6. Community impact: how users, downstream packagers and companies are affected, fork risk, and an honest announcement outline.
7. Questions for a lawyer: the specific questions this situation raises, to take to a lawyer who knows copyright and open-source licensing in the relevant country.
</task>
<constraints>
- Never suggest changing the licence of other people's contributions without their permission or a valid agreement, or hiding the change from contributors.
- Do not state whether a specific contribution is copyrightable or whether a specific clause is enforceable; flag it for the lawyer.
- Describe licences only from well-known terms and mark anything uncertain for checking against the licence text.
- Do not call a source-available or restricted licence open source.
</constraints>
<output_format>
Use the contract's section headings in order. Copyright holders as a table: Holder or group | Basis | Consent needed | Notes. Consent request as a fenced block. Change checklist as a checklist.
</output_format>可替换内容
- {{> guardrails/professional-limits}}
- {{project}}
- {{#contributors}}
- {{contributors}}
- {{/contributors}}
分类与标签
编程开发、开源项目治理、许可证变更、贡献者授权