Revisit CC-BY-NC-ND license for code, snippets and templates

Aperta
#46 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp, python, unity

Direzione di ricerca

Start by reviewing LICENSE, .cursor-plugin/plugin.json, the README badge, and CONTRIBUTING.md; inventory the code in mcp-server/, snippets/, and templates/ alongside the prose. Compare the listed licensing options and decide which terms apply to each part of the project. Record the decision and add a short README answer to “Can I use this in my commercial game?”

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

Descrizione

community documentation priority: medium

Why it matters

CC-BY-NC-ND-4.0 forbids derivatives and commercial use. For a developer tool this has real consequences:

  • Contributions: ND means nobody may distribute modified versions, which conflicts with CONTRIBUTING.md inviting PRs and forks (a fork with changes is a derivative).
  • Adoption: NC excludes commercial game studios and indie developers selling games, which is most of the target audience. It is unclear whether code generated from the snippets or templates inside a commercial game is permitted.
  • Distribution: some marketplaces and MCP directories prefer or require OSI-approved licenses. Creative Commons itself recommends against CC licenses for software.

Evidence

  • LICENSE, .cursor-plugin/plugin.json ("license": "CC-BY-NC-ND-4.0"), README badge.
  • mcp-server/ (Python code) and snippets/ / templates/ (C# meant to be pasted into games) fall under the same license.

Options to decide

  1. MIT or Apache-2.0 for code (MCP server, snippets, templates) and CC-BY-4.0 for prose (skills, rules, docs). This is the common pattern and maximizes adoption.
  2. Keep restrictions on skills and rules but explicitly grant users rights to use snippet/template code in any game, commercial or not.
  3. Keep as is, but add a FAQ that clearly states what users may do with generated code.

Pair the choice with sponsorship tiers (GitHub Sponsors is already linked) if monetization is the goal of NC.

Done when

A license decision is recorded and README has a short "Can I use this in my commercial game?" answer.

Lingua principale
C#
Stelle
4
Fork
0
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

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/Unity-Developer-Tools

Tutte le issue di TMHSDigital/Unity-Developer-Tools

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.