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

未關閉
#201 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
30/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
markdown, typescript, yaml
領域
documentation

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.
主要語言
TypeScript
星號
1
分支
4
平均合併
14 小時 8 分鐘
30 天內合併 PR
48

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/screencast-mcp 的其他 Issue

查看 TMHSDigital/screencast-mcp 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。