Revisit CC-BY-NC-ND license for code, snippets and templates
還沒有人認領這個 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 內容生成。
描述
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.mdinviting 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) andsnippets//templates/(C# meant to be pasted into games) fall under the same license.
Options to decide
- 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.
- Keep restrictions on skills and rules but explicitly grant users rights to use snippet/template code in any game, commercial or not.
- 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
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TMHSDigital/Unity-Developer-Tools 的其他 Issue
-
難度 4/5 3-5 天 新手友好度 35/100
-
ci priority: low skills
難度 3/5 1-2 天 新手友好度 55/100
-
good first issue skills testing
難度 3/5 1-2 天 新手友好度 58/100
-
ci priority: medium testing
難度 4/5 1-2 天 新手友好度 57/100
-
documentation marketing priority: medium
難度 5/5 一週以上 新手友好度 35/100
查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue
相似的 Issue
-
type:task ux
難度 2/5 1-3 小時 新手友好度 72/100
elsa-workflows/elsa-foundation#5253 ·
維護者通常 1 天內回覆