catalog: a terminal status for per-item aggregators so 40 entries do not sit in `needs-review` forever
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- javascript
- 领域
- content, documentation
调研方向
Start with docs/review-ledger.md and the README status table, then find the catalog validator, status filters, and card and entry page copy. Review the remaining needs-review aggregators and add a Notes line for each explaining how to check its per-file licence. Done means open questions remain needs-review, per-item licences have a clear badge, and the README explains all three states.
由索引模型根据 Issue 内容生成。
描述
Why it matters
40 entries are needs-review, and the 2026-10-04 ledger says most of the remaining ones "are mostly per-file aggregators, or questions only the publisher can answer" (Freesound, OpenGameArt, Sketchfab, Lospec, Poly Pizza, NASA Image Library...). They will never become active because their licence genuinely varies per file. Leaving them as needs-review makes the status meaningless as a work queue, hides them behind the default filter, and makes 46% of the video category look unfinished.
Evidence (data audit 2026-10-21)
- status: active 372, needs-review 40 (audio 8, 3d 7, tools 6, video 6 of 13), deprecated 2.
- Their licences: custom 17, varies 16, unknown 3.
commercial: variesis already a value (16 entries). docs/review-ledger.md, 2026-10-04 section, "Still needs-review" paragraph.
Suggested approach
Add a status such as per-item (licence settled as "varies by file; check each download"), with its own badge and copy on the card and entry page, and keep needs-review strictly for entries with an open question. Move the aggregator entries over in one sweep, each with a Notes line on how to read the per-file licence on that site. Update the validator, the filters, docs/, and the README status table.
Done when
needs-review contains only entries with a stated open question, aggregators show a clear "varies per file" badge, and the status table in the README explains the three states.
- 主要语言
- JavaScript
- 星标
- 58
- 派生
- 15
- 平均合并
- 16 小时 53 分钟
- 30 天内合并 PR
- 14
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
TMHSDigital/Free-Game-Dev-Assets 的其他 Issue
-
community marketing priority: low
难度 2/5 1-3 小时 新手友好度 72/100
TMHSDigital/Free-Game-Dev-Assets#151 ·
维护者通常 1 天内回复
-
documentation priority: medium
难度 2/5 1-3 小时 新手友好度 78/100
TMHSDigital/Free-Game-Dev-Assets#72 ·
维护者通常 1 天内回复
-
enhancement
难度 1/5 1-3 小时 新手友好度 68/100
TMHSDigital/Free-Game-Dev-Assets#3 · 1 条评论 ·
维护者通常 1 天内回复
-
marketing priority: low
难度 2/5 1-3 小时 新手友好度 55/100
TMHSDigital/Free-Game-Dev-Assets#152 ·
维护者通常 1 天内回复
-
feature priority: medium
难度 5/5 一周以上 新手友好度 25/100
TMHSDigital/Free-Game-Dev-Assets#144 ·
维护者通常 1 天内回复
查看 TMHSDigital/Free-Game-Dev-Assets 的全部 Issue
相似的 Issue
-
bug require-triage
难度 2/5 1-3 小时 新手友好度 72/100
expressjs/expressjs.com#2549 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
vercel-labs/agent-skills#348 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
NanmiCoder/dsh-agent-teams#289 ·
维护者通常 1 天内回复