Example of both REUSE and Licensee compliant codebase
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start with the “publish with an open license” criterion linked in the issue, then review the Alliander utility-route-planner repository as the proposed example. Done means documenting an example of a codebase that complies with both REUSE and Licensee, including the relevant link and context.
Written by the indexing model from the issue text.
Description
For 'publish with an open license':
While I was at Alliander, we updated our template open source repo to require meeting both standards (by publishing the license multiple times in multiple places).
Example: https://github.com/alliander-opensource/utility-route-planner
- Dominant language
- Shell
- Stars
- 1
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 standard-for-public-code/community-implementation-guide-standard
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
standard-for-public-code/community-implementation-guide-standard#131 · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
standard-for-public-code/community-implementation-guide-standard#97 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
standard-for-public-code/community-implementation-guide-standard#129 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
standard-for-public-code/community-implementation-guide-standard#128 ·
-
funding.yml? Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
standard-for-public-code/community-implementation-guide-standard#126 · 3 comments ·
All issues in standard-for-public-code/community-implementation-guide-standard
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·