Revisit CC-BY-NC-ND license for code, snippets and templates
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
- Domínio
- documentation, game-dev
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
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.
- Linguagem predominante
- C#
- Estrelas
- 4
- Forks
- 0
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de TMHSDigital/Unity-Developer-Tools
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
-
ci priority: low skills
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 55/100
-
good first issue skills testing
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 58/100
-
ci priority: medium testing
Dificuldade 4/5 1-2 dias Facilidade para iniciantes 57/100
-
documentation marketing priority: medium
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 35/100
Todas as issues de TMHSDigital/Unity-Developer-Tools
Issues semelhantes
-
type:task ux
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
elsa-workflows/elsa-foundation#5253 ·
Mantenedores costumam responder em até 1 dia