community: CONTRIBUTING never states that contributions are dedicated under CC0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Read CONTRIBUTING.md, .github/PULL_REQUEST_TEMPLATE.md, and the README License section. Add the requested CC0 contribution statement and checkbox, then link the contribution guidance from the README. Done when all three documents contain the stated guidance and link.
Written by the indexing model from the issue text.
Description
Why it matters
CC0 is a dedication the author must make. LICENSE and package.json claim the metadata and documentation are CC0, but a contributor's prose (summaries, notes, guides) is not covered unless they say so. That matters for contributors at companies, for publishers listing their own work, and for every downstream reuser of data.json who relies on the CC0 claim.
Evidence (at 69387df)
- Searching
CONTRIBUTING.mdand.github/PULL_REQUEST_TEMPLATE.mdfor cc0, public domain, dedicate or waive finds only frontmatter-value mentions (CONTRIBUTING.md:45,48,50,53,90); there is no statement about the licence of the contribution itself. The PR template checklist has no acknowledgement line. README.md:399-401andLICENSEdedicate "catalog metadata and documentation in this repository" to the public domain.
Suggested approach
Add a two-sentence "Licence of contributions" section to CONTRIBUTING ("By opening a pull request you dedicate your contribution to the public domain under CC0 1.0, like the rest of the repository; quotes from licence pages stay the publisher's words and are used as short factual quotations") and one checkbox in PULL_REQUEST_TEMPLATE.md. No CLA tooling needed.
Done when
CONTRIBUTING and the PR template carry the CC0 statement; the README "License" section links to it.
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 15
- Avg merge
- 16h 53m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TMHSDigital/Free-Game-Dev-Assets
-
community marketing priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/Free-Game-Dev-Assets#151 ·
Maintainers usually reply within 1 day
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TMHSDigital/Free-Game-Dev-Assets#72 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
TMHSDigital/Free-Game-Dev-Assets#3 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
TMHSDigital/Free-Game-Dev-Assets#152 ·
Maintainers usually reply within 1 day
-
feature priority: medium
Difficulty 5/5 Over a week Newbie friendliness 25/100
TMHSDigital/Free-Game-Dev-Assets#144 ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/Free-Game-Dev-Assets
Similar issues
-
bug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vercel-labs/agent-skills#348 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NanmiCoder/dsh-agent-teams#289 ·
Maintainers usually reply within 1 day