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
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)未关闭
难度 2/5 1-3 小时 新手友好度 68/100
-
llm translation
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
FAIRmat-NFDI/sand#239 ·
维护者通常 1 天内回复
-
bug P2
难度 2/5 1-3 小时 新手友好度 72/100
coco-research/coco#539 ·
维护者通常 1 天内回复
-
dependencies
难度 2/5 1-3 小时 新手友好度 62/100
JustBeanie/hass-volcano-hybrid#34 ·
维护者通常 1 天内回复