license: LICENSE file still says 'no commercial use' with no grant for the commercial use the README promises (#336 incomplete)

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
1-2 天
新手友好度
62/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
blender, python
领域
documentation

调研方向

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 内容生成。

描述

distribution documentation priority: high stale

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-219 answers "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 view reports licenseInfo Other.
  • The landing page and gallery pages carry no license line at all.

Suggested approach

  • Add an explicit Additional permissions section to LICENSE stating 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/ and templates/ 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

环境准备

从这里开始

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

TMHSDigital/Blender-Developer-Tools 的其他 Issue

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

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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