catalog: only 48 of 414 entries have a credit line, so "Copy credit line" is missing on most CC-BY and OFL pages
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 57/100
- Issue 類型
- 功能
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript, markdown
研究方向
Start with the catalog entries under catalog/*/*.md, then read site/lib/entry-page.mjs around line 52 and find the validator entry point. Add credit lines for entries marked attribution_required: true, recording each source in its Evidence section, and make the validator warn when a required credit line is missing. Done when every such entry has a credit line and the validator reports missing ones.
由索引模型根據 Issue 內容生成。
描述
Why it matters
The entry page has a "Copy credit line" button and the shortlist exports a CREDITS file, but both depend on attribution_string, which exists on 48 entries. For the roughly 90 entries whose licence requires or customarily asks for credit (CC-BY 3.0/4.0, OFL reserved names, custom licences with a credit clause), the page says "Attribution is required and no canned credit line is recorded", which pushes the work back to the reader at the exact moment the catalog promised to save it.
Evidence
grep -l 'attribution_string:' catalog/*/*.md | wc -l→ 48.- Data audit 2026-10-21: license_spdx CC-BY-4.0 15, CC-BY-3.0 6, OFL-1.1 19, custom 60;
attribution_required: trueentries without a string render the fallback atsite/lib/entry-page.mjs:52.
Suggested approach
For each attribution_required: true entry, write the credit line the source asks for (or the CC-standard form "Title by Author, licensed CC BY 4.0" when the source gives none) and record where it came from in Evidence. Add a validator warning for attribution_required: true without attribution_string so new entries fill it.
Done when
Every attribution_required: true entry has a credit line, and the validator warns when one is missing.
- 主要語言
- 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 天內回覆