Commercial-use path: FUNDING.yml, GitHub Sponsors tiers, and a commercial license offer for the NC license

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

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
markdown, typescript, yaml
Domínio
documentation

Direção de pesquisa

The payload points to a missing .github/FUNDING.yml, the funding field in package.json (which npm fund reads), and the NC license explanation in the README around line 306. The FUNDING.yml and package.json edits are mechanical, but the commercial license terms, pricing and contact route are maintainer decisions, so confirm those before writing copy. Done when a business visitor can reach the commercial path from the README and home page in one click, and npm fund lists the project.

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

Descrição

effort: small impact: medium marketing monetization priority: medium

Why it matters

CC-BY-NC-ND-4.0 is a deliberate choice (#91). It also means every company that wants to use screencast-mcp for work, the natural buyers of an agent QA and demo tool, currently has no way to say yes. That is both a missed revenue path and a reason for companies to pick a less capable alternative. Making "how to use this commercially" one click away turns the license from a blocker into a funnel.

Evidence

  • There is no .github/FUNDING.yml, no Sponsors button, and no commercial-use contact in the README, the site or package.json (funding field).
  • The README explains the NC terms (around line 306) but gives no next step for a business.

Suggested approach

  • Add .github/FUNDING.yml (GitHub Sponsors, and others if desired) and a funding field in package.json, which shows in npm fund.
  • Add a "Commercial use" section and page with a clear offer: a per-seat or per-company commercial license, priority support, or a sponsorship tier that includes commercial rights. Add a contact route, either a form or a dedicated address. Don't put personal email in issues.
  • Add sponsor tiers tied to project value: logo on the docs site, priority on feature requests, an early-access build of bigger bets such as the review player features and publish (#176).
  • Show a single footer line on the site: "Free for non-commercial use · Commercial license →".

Done when

  • A business visitor can find the commercial path in one click from the README and the home page.
  • npm fund shows the project.
Linguagem predominante
TypeScript
Estrelas
1
Forks
4
Merge médio
14h 8min
PRs com merge (30d)
48

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/screencast-mcp

Todas as issues de TMHSDigital/screencast-mcp

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

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