Consider using CC0 Public Domain declaration
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Review the repository’s current public-domain or licensing declaration, then compare the proposed CC0 and Unlicense options linked in the issue. Done means the project has a clearly chosen replacement declaration and its licensing text reflects that decision.
Written by the indexing model from the issue text.
Description
As some jurisdictions don't recognize the right to prematurely put your creation into the public domain, it'd be a good idea to use the Creative Commons CC0 public domain declaration rather than writing your own.
It contains an "If your jurisdiction doesn't allow this, then, instead, I license it to you under equivalent terms" clause.
Otherwise, people in those jurisdictions get the default "All Rights Reserved".
...or, if you don't like that for some reason, there's also The Unlicense as a way to put something in the public domain which GitHub likes enough to list in choosealicense.com's list of more options.
- Dominant language
- Vim Script
- Stars
- 173
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 vim-jp/vim-vimlparser
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#201 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
vim-jp/vim-vimlparser#200 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#198 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#197 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#191 ·
All issues in vim-jp/vim-vimlparser
Similar issues
-
area/docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area: providers/aws priority: p1 size: S type: documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
finos/open-resource-broker#417 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
inbo/erl-butterflies-2025#26 ·