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 天内回复