license: LICENSE file still says 'no commercial use' with no grant for the commercial use the README promises (#336 incomplete)
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 1-2 天
- 新手友好度
- 62/100
- Issue 類型
- 文件
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- blender, python
研究方向
Read LICENSE alongside README.md lines 215-219, the README license badge, and the landing and gallery pages. Update those named license surfaces to reflect the permissions and dual license described in the issue; check that snippets/ and templates/ license files are referenced. Done when LICENSE alone answers the commercial-use FAQ and the badge and site reflect the dual license.
由索引模型根據 Issue 內容生成。
描述
Why it matters
Professional add-on developers, and the legal reviewers at their studios, read LICENSE and the GitHub sidebar, not README prose. Right now those surfaces say "NonCommercial". The README's FAQ answer ("Yes, use it for paid work") is an interpretation, not a grant, so the core audience is still scared off. #336 fixed the README wording but not the license itself.
Evidence
LICENSE:21: "NonCommercial - You may not use the material for commercial purposes." There is no mention of the MIT carve-outs (snippets/LICENSE,templates/LICENSE) and no agent-use clarification.README.md:215-219answers "Can I use this to build a commercial or GPL add-on? Yes".- The README license badge shows only
CC-BY-NC-ND-4.0.gh repo viewreports licenseInfoOther. - The landing page and gallery pages carry no license line at all.
Suggested approach
- Add an explicit Additional permissions section to
LICENSEstating that:- using the material as context or instructions for an AI agent or a human, to produce your own software (commercial or GPL), is permitted;
- that output is not Adapted Material;
snippets/andtemplates/are MIT (point to their LICENSE files).
- Change the badge to "CC BY-NC-ND 4.0 + MIT (code)".
- Add a one-line license footer on the site.
Done when
LICENSE alone answers the commercial-use FAQ the same way the README does, and the badge and site reflect the dual license.
- 主要語言
- Python
- 星號
- 17
- 分支
- 3
- 平均合併
- 23 小時 48 分鐘
- 30 天內合併 PR
- 3
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TMHSDigital/Blender-Developer-Tools 的其他 Issue
-
bug ci priority: high
難度 2/5 1-3 小時 新手友好度 55/100
-
content-integrity priority: low showcase stale
難度 5/5 一週以上 新手友好度 45/100
TMHSDigital/Blender-Developer-Tools#499 · 1 則留言 ·
-
community documentation priority: high security stale
難度 3/5 1-2 天 新手友好度 56/100
TMHSDigital/Blender-Developer-Tools#392 · 2 則留言 ·
-
feature marketing priority: high stale testing
難度 5/5 一週以上 新手友好度 25/100
TMHSDigital/Blender-Developer-Tools#373 · 1 則留言 ·
查看 TMHSDigital/Blender-Developer-Tools 的全部 Issue
相似的 Issue
-
hive size:simple
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)未關閉
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 70/100
painted-porch/marcus#977 ·
維護者通常 1 天內回覆
-
llm translation
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
FAIRmat-NFDI/sand#239 ·
維護者通常 1 天內回覆