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

Aberta
#46 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
csharp, python, unity

Direção de pesquisa

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?”

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C#
Estrelas
4
Forks
0
Métricas de merge de PRs
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/Unity-Developer-Tools

Todas as issues de TMHSDigital/Unity-Developer-Tools

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.