Revisit CC-BY-NC-ND license for code, snippets and templates
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 48/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Bereich
- documentation, game-dev
Rechercherichtung
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?”
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.mdinviting 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) andsnippets//templates/(C# meant to be pasted into games) fall under the same license.
Options to decide
- 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.
- Keep restrictions on skills and rules but explicitly grant users rights to use snippet/template code in any game, commercial or not.
- 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.
- Vorherrschende Sprache
- C#
- Sterne
- 4
- Forks
- 0
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus TMHSDigital/Unity-Developer-Tools
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
-
ci priority: low skills
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 55/100
-
good first issue skills testing
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 58/100
-
ci priority: medium testing
Schwierigkeit 4/5 1-2 Tage Anfängerfreundlichkeit 57/100
-
documentation marketing priority: medium
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 35/100
Alle Issues in TMHSDigital/Unity-Developer-Tools
Ähnliche Issues
-
type:task ux
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
elsa-workflows/elsa-foundation#5253 ·
Maintainer antworten meist innerhalb von 1 Tag