Commercial-use path: FUNDING.yml, GitHub Sponsors tiers, and a commercial license offer for the NC license
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 30/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- markdown, typescript, yaml
研究方向
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 內容生成。
描述
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 orpackage.json(fundingfield). - 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 afundingfield inpackage.json, which shows innpm 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 fundshows the project.
- 主要語言
- TypeScript
- 星號
- 1
- 分支
- 4
- 平均合併
- 14 小時 8 分鐘
- 30 天內合併 PR
- 48
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TMHSDigital/screencast-mcp 的其他 Issue
-
effort: small good first issue priority: medium testing
難度 2/5 1-3 小時 新手友好度 84/100
TMHSDigital/screencast-mcp#351 ·
維護者通常 1 天內回覆
-
bug effort: small priority: medium
難度 2/5 1-3 小時 新手友好度 82/100
TMHSDigital/screencast-mcp#344 ·
維護者通常 1 天內回覆
-
bug effort: small good first issue priority: medium
難度 2/5 1-3 小時 新手友好度 82/100
TMHSDigital/screencast-mcp#343 ·
維護者通常 1 天內回覆
-
effort: medium help wanted priority: medium testing
難度 3/5 1-2 天 新手友好度 76/100
TMHSDigital/screencast-mcp#350 ·
維護者通常 1 天內回覆
-
effort: medium priority: medium testing
難度 4/5 1-2 天 新手友好度 70/100
TMHSDigital/screencast-mcp#349 ·
維護者通常 1 天內回覆
查看 TMHSDigital/screencast-mcp 的全部 Issue
相似的 Issue
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
難度 2/5 1-3 小時 新手友好度 82/100
openclaw/openclaw#200365 · 1 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
area-templates triage:bot-seen triage:needs-human
難度 2/5 1-3 小時 新手友好度 75/100
microsoft/aspire#22356 · 1 則留言 ·
維護者通常 1 天內回覆
-
Archiving an agent that is not loaded keeps its old updatedAt可能已有人在做 @luoph 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
content triage
難度 1/5 1 小時以內 新手友好度 88/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆