Back to Details

open-source-license

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
First published on Skala Legal Skills
首次发布于 Skala Legal Skills

Legal Disclaimer

法律免责声明

This skill is provided for informational and educational purposes only and does not constitute legal advice. The analysis and information provided should not be relied upon as a substitute for consultation with a qualified attorney. No attorney-client relationship is created by using this skill. Open source licensing involves complex legal considerations that may vary by jurisdiction. Laws and regulations vary by jurisdiction and change over time. Always consult with a licensed attorney in your jurisdiction for advice on specific legal matters. The creators and publishers of this skill disclaim any liability for actions taken or not taken based on the information provided.
本技能仅用于信息和教育目的，不构成法律建议。请勿将此处提供的分析和信息作为咨询合格律师的替代方案。使用本技能不会建立律师-客户关系。开源许可涉及复杂的法律考量，可能因司法管辖区而异。法律法规因司法管辖区不同而有所差异，且会随时间变化。针对特定法律事务，务必咨询您所在司法管辖区的持牌律师。本技能的创作者和发布者对基于此处提供的信息所采取或未采取的任何行动不承担任何责任。

Open Source License Skill

开源许可证技能

Comprehensive guidance for open source license selection, compliance review, and documentation drafting.
开源许可证选择、合规审查与文档起草的全面指导。

Capabilities

功能

1. License Selection

1. 许可证选择

Help users choose the right license based on their goals using the decision tree.
借助决策树，根据用户的目标帮助其选择合适的许可证。

2. License Comparison

2. 许可证对比

Explain differences between licenses, compatibility, and trade-offs.
解释不同许可证之间的差异、兼容性以及权衡取舍。

3. Compliance Review

3. 合规审查

Analyze projects for license compliance issues and compatibility conflicts.
分析项目中的许可证合规问题与兼容性冲突。

4. License Drafting

4. 许可证起草

Generate LICENSE files, NOTICE files, and source file headers using canonical texts.
使用标准文本生成LICENSE文件、NOTICE文件以及源文件头部。

Workflow

工作流程

For License Selection Questions

针对许可证选择类问题

  1. Read 
    references/selection/decision-tree.md
  2. Ask clarifying questions based on the decision tree:
    • Primary goal (adoption vs keeping code open)?
    • Patent protection needed?
    • Library or application?
    • SaaS/network use?
  3. Provide recommendation with reasoning
  4. Reference notable projects using recommended license
  5. Offer to generate LICENSE file if desired
  1. 阅读 
    references/selection/decision-tree.md
  2. 根据决策树提出明确问题：
    • 核心目标（推广采用 vs 保持代码开源）？
    • 是否需要专利保护？
    • 是库还是应用程序？
    • 是否用于SaaS/网络场景？
  3. 提供带有理由的推荐方案
  4. 列举使用该推荐许可证的知名项目
  5. 若用户需要，可提供生成LICENSE文件的服务

For License Comparison Questions

针对许可证对比类问题

  1. Read 
    references/selection/comparison-matrix.md
  2. Compare requested licenses across key dimensions:
    • Permissions (commercial use, distribution, modification)
    • Conditions (attribution, copyleft, source disclosure)
    • Limitations (liability, warranty)
  3. Highlight key differences
  4. Provide examples of projects using each license
  1. 阅读 
    references/selection/comparison-matrix.md
  2. 从关键维度对比用户指定的许可证：
    • 权限（商业使用、分发、修改）
    • 条件（署名、Copyleft、源码披露）
    • 限制（责任、担保）
  3. 突出关键差异
  4. 列举每个许可证的实际使用项目案例

For Compliance Review

针对合规审查

  1. Read 
    references/compliance/compatibility.md
    and 
    references/compliance/checklist.md
  2. Identify all licenses in the project
  3. Check compatibility between licenses
  4. Flag any copyleft licenses that may affect distribution
  5. Note any missing attribution or compliance gaps
  6. Provide actionable remediation steps
  7. Reference 
    references/compliance/common-issues.md
    for context
  1. 阅读 
    references/compliance/compatibility.md
    和 
    references/compliance/checklist.md
  2. 识别项目中的所有许可证
  3. 检查许可证之间的兼容性
  4. 标记可能影响分发的Copyleft许可证
  5. 记录任何缺失的署名或合规缺口
  6. 提供可执行的整改步骤
  7. 参考 
    references/compliance/common-issues.md
    获取相关背景信息

For License/NOTICE File Generation

针对LICENSE/NOTICE文件生成

  1. Read appropriate template from 
    references/templates/
  2. CRITICAL: Always use canonical license text exactly as provided
  3. Never modify license terms or generate license text from scratch
  4. Only fill in placeholders: 
    [YEAR]
    , 
    [FULLNAME]
    , 
    [PROJECT NAME]
  5. For NOTICE files, aggregate third-party attributions properly
  6. For headers, use language-appropriate comment syntax
  1. 从 
    references/templates/
    中读取合适的模板
  2. 重要提示：务必完全使用提供的标准许可证文本
  3. 绝不要修改许可证条款或从头生成许可证文本
  4. 仅填充占位符：
    [YEAR]
    、
    [FULLNAME]
    、
    [PROJECT NAME]
  5. 对于NOTICE文件，正确汇总第三方署名信息
  6. 对于文件头部，使用对应语言的注释语法

Reference Files

参考文件

TopicFile
Permissive licenses (MIT, Apache, BSD, ISC)
references/licenses/permissive.md
Copyleft licenses (GPL, LGPL, AGPL, MPL)
references/licenses/copyleft.md
Other licenses (CC, Boost, zlib)
references/licenses/specialty.md
License comparison table
references/selection/comparison-matrix.md
License selection guide
references/selection/decision-tree.md
License compatibility rules
references/compliance/compatibility.md
Compliance checklist
references/compliance/checklist.md
Common compliance mistakes
references/compliance/common-issues.md
LICENSE file templates
references/templates/license-files.md
NOTICE file templates
references/templates/notice-files.md
Source header templates
references/templates/source-headers.md
主题文件
宽松许可证（MIT、Apache、BSD、ISC）
references/licenses/permissive.md
Copyleft许可证（GPL、LGPL、AGPL、MPL）
references/licenses/copyleft.md
其他许可证（CC、Boost、zlib）
references/licenses/specialty.md
许可证对比表
references/selection/comparison-matrix.md
许可证选择指南
references/selection/decision-tree.md
许可证兼容性规则
references/compliance/compatibility.md
合规检查清单
references/compliance/checklist.md
常见合规错误
references/compliance/common-issues.md
LICENSE文件模板
references/templates/license-files.md
NOTICE文件模板
references/templates/notice-files.md
源文件头部模板
references/templates/source-headers.md

Key Rules

核心规则

Never Generate License Text

禁止生成许可证文本

Always use canonical license text from templates. License texts are legal documents that must be exact. Do not:
  • Paraphrase license terms
  • Generate license text from memory
  • Modify standard license language
  • Create "custom" licenses
务必使用模板中的标准许可证文本。许可证文本属于法律文件，必须完全准确。禁止：
  • 意译许可证条款
  • 凭记忆生成许可证文本
  • 修改标准许可证语言
  • 创建“自定义”许可证

Include Project Examples

包含项目案例

When discussing licenses, mention notable projects that use them:
  • MIT: React, Node.js, jQuery, Rails, Angular
  • Apache-2.0: Kubernetes, TensorFlow, Android, Spark
  • GPL-3.0: WordPress, GIMP, Bash
  • AGPL-3.0: Nextcloud, Mastodon, Grafana
  • BSD-3-Clause: Django, Flask, numpy
  • MPL-2.0: Firefox, Thunderbird
讨论许可证时，提及使用该许可证的知名项目：
  • MIT: React、Node.js、jQuery、Rails、Angular
  • Apache-2.0: Kubernetes、TensorFlow、Android、Spark
  • GPL-3.0: WordPress、GIMP、Bash
  • AGPL-3.0: Nextcloud、Mastodon、Grafana
  • BSD-3-Clause: Django、Flask、numpy
  • MPL-2.0: Firefox、Thunderbird

Flag Complex Scenarios

标记复杂场景

Recommend legal counsel for:
  • Dual licensing strategies
  • License changes mid-project
  • Commercial projects with copyleft dependencies
  • AGPL in SaaS environments
  • Multi-jurisdictional distribution
  • Patent-sensitive situations
针对以下场景，建议咨询法律顾问：
  • 双重许可策略
  • 项目中途变更许可证
  • 包含Copyleft依赖的商业项目
  • SaaS环境中使用AGPL
  • 跨司法管辖区分发
  • 涉及专利敏感的情况

Quick Answers

快速解答

"What license should I use?"

“我应该使用什么许可证？”

→ Follow decision tree; default to MIT for simplicity or Apache-2.0 for patent protection.
→ 遵循决策树；若追求简洁默认选择MIT，若需要专利保护则选择Apache-2.0。

"Can I use GPL code in my proprietary app?"

“我可以在专有应用中使用GPL代码吗？”

→ Generally no, unless through LGPL dynamic linking or separate processes.
→ 通常不可以，除非通过LGPL动态链接或独立进程的方式。

"What's the difference between MIT and Apache-2.0?"

“MIT和Apache-2.0有什么区别？”

→ Apache-2.0 includes explicit patent grant and retaliation clause; MIT is simpler but no patent protection.
→ Apache-2.0包含明确的专利授权和反报复条款；MIT更简洁但不提供专利保护。

"Is Apache-2.0 compatible with GPL?"

“Apache-2.0与GPL兼容吗？”

→ Apache-2.0 is compatible with GPL-3.0, but NOT with GPL-2.0.
→ Apache-2.0与GPL-3.0兼容，但与GPL-2.0不兼容。

"Do I need to open source my code if I use AGPL?"

“如果我使用AGPL，是否需要开源我的代码？”

→ Only if you modify the AGPL code AND provide it as a network service. Using unmodified AGPL tools internally doesn't trigger copyleft.
→ 只有当您修改了AGPL代码并将其作为网络服务提供时才需要。内部使用未修改的AGPL工具不会触发Copyleft条款。

Output Format

输出格式

When generating LICENSE files:
  1. Confirm the license choice
  2. Ask for copyright holder name and year
  3. Output the complete canonical license text
  4. Remind user to place it in repository root as 
    LICENSE
    or 
    LICENSE.txt
When reviewing compliance:
  1. List all identified licenses
  2. Show compatibility analysis
  3. Flag any issues with severity (critical/warning/info)
  4. Provide specific remediation steps
生成LICENSE文件时：
  1. 确认许可证选择
  2. 询问版权持有人姓名和年份
  3. 输出完整的标准许可证文本
  4. 提醒用户将其放置在仓库根目录，命名为
    LICENSE
    或
    LICENSE.txt
进行合规审查时：
  1. 列出所有识别到的许可证
  2. 展示兼容性分析
  3. 标记问题的严重程度（严重/警告/信息）
  4. 提供具体的整改步骤