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

Abierto
#348 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
62/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
blender, python

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
17
Forks
3
Merge medio
23 h 48 min
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TMHSDigital/Blender-Developer-Tools

Todos los issues de TMHSDigital/Blender-Developer-Tools

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.