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

Aperta
#348 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
62/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
blender, python
Ambito
documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
17
Fork
3
Merge medio
23h 48m
PR unite (30g)
3

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TMHSDigital/Blender-Developer-Tools

Tutte le issue di TMHSDigital/Blender-Developer-Tools

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.