Legal code issues & errata: Outdated errata (“until the new website is launched”)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- html
- Domain
- documentation
Research direction
Start by locating the “Issues by legal tool” section on the Legal code issues & errata page in the repository; the payload does not name a file or test. Remove the outdated parenthetical references to the new website launch and review the related wording noted in the body. Done when the published errata no longer says those changes are waiting for the new website.
Written by the indexing model from the issue text.
Description
The Issues by legal tool section of the Legal code issues & errata page reads:
CC0 1.0
[…]
Description. The Deed page of CC0 1.0 refers to using “the license”; CC0 should be described as a legal tool. (This is not part of the legal code but will not be corrected until the new website is launched.)
Public Domain Mark 1.0
Description. The Deed page of PDM 1.0 refers to using “the license”; PDM should be described as a legal tool. (This is not part of the legal code but will not be corrected until the new website is launched.)
The parentheses are outdated following the launch of the new website (although the CC0 Deed page still contains “Use the license for your own material.”).
By the way
”This will be changed when we next version CC0” should presumably read something like “This will be changed when we release the next version of CC0”.- Dominant language
- HTML
- Stars
- 187
- Forks
- 243
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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 creativecommons/creativecommons.org
-
💻 aspect: code 🚧 status: blocked 🛠 goal: fix 🟨 priority: medium
Difficulty 5/5 Over a week Newbie friendliness 35/100
creativecommons/creativecommons.org#1424 · 4 comments ·
-
💻 aspect: code 🛠 goal: fix 🟨 priority: medium 🧹 status: ticket work required
Difficulty 4/5 3-5 days Newbie friendliness 45/100
creativecommons/creativecommons.org#1422 · 2 comments ·
-
✨ goal: improvement 🏁 status: ready for work 💻 aspect: code 🟩 priority: low
Difficulty 5/5 Over a week Newbie friendliness 20/100
creativecommons/creativecommons.org#1315 · 1 comment ·
-
✨ goal: improvement 💻 aspect: code 🟩 priority: low 🧹 status: ticket work required
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
[Feature] Unambiguously Grant a Copyright License to CC IconsMay be free again @diyananoory-cc claimed this 422 days ago, and no pull request is open. Open✨ goal: improvement 🏁 status: ready for work 🔒 staff only 🕹 aspect: interface 🟩 priority: low
creativecommons/creativecommons.org#1308 · 2 comments · 3 assignees ·
All issues in creativecommons/creativecommons.org
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mohi-devhub/antivibe#12 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
awsdocs/amazon-eks-user-guide#1261 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
A-documentation S-needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Quantinuum/hugr#3344 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
huggingface/tau#799 ·
Maintainers usually reply within 2 days