Revisit CC-BY-NC-ND license for code, snippets and templates

未关闭
#46 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃

调研方向

Start by reviewing LICENSE, .cursor-plugin/plugin.json, the README badge, and CONTRIBUTING.md; inventory the code in mcp-server/, snippets/, and templates/ alongside the prose. Compare the listed licensing options and decide which terms apply to each part of the project. Record the decision and add a short README answer to “Can I use this in my commercial game?”

由索引模型根据 Issue 内容生成。

描述

community documentation priority: medium

Why it matters

CC-BY-NC-ND-4.0 forbids derivatives and commercial use. For a developer tool this has real consequences:

  • Contributions: ND means nobody may distribute modified versions, which conflicts with CONTRIBUTING.md inviting PRs and forks (a fork with changes is a derivative).
  • Adoption: NC excludes commercial game studios and indie developers selling games, which is most of the target audience. It is unclear whether code generated from the snippets or templates inside a commercial game is permitted.
  • Distribution: some marketplaces and MCP directories prefer or require OSI-approved licenses. Creative Commons itself recommends against CC licenses for software.

Evidence

  • LICENSE, .cursor-plugin/plugin.json ("license": "CC-BY-NC-ND-4.0"), README badge.
  • mcp-server/ (Python code) and snippets/ / templates/ (C# meant to be pasted into games) fall under the same license.

Options to decide

  1. MIT or Apache-2.0 for code (MCP server, snippets, templates) and CC-BY-4.0 for prose (skills, rules, docs). This is the common pattern and maximizes adoption.
  2. Keep restrictions on skills and rules but explicitly grant users rights to use snippet/template code in any game, commercial or not.
  3. Keep as is, but add a FAQ that clearly states what users may do with generated code.

Pair the choice with sponsorship tiers (GitHub Sponsors is already linked) if monetization is the goal of NC.

Done when

A license decision is recorded and README has a short "Can I use this in my commercial game?" answer.

主要语言
C#
星标
4
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TMHSDigital/Unity-Developer-Tools 的其他 Issue

查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。