REUSE (https://reuse.software/) is a growing straightforward standard that is a complement to the traditional LICENSE declarations for an Open Source project. In short, it tells the end user about everything else than code, (or if there are multiple licenses, about the specifics).
Why is this good? It tells anyone looking at the project what the intention are for the resources in the projects and the (re)usabilty. Another bonus is that it by design, forces the maintainers to think about images, docs and other things that are easily overlooked when going Open Source.
Feature suggestion description
Do an REUSE Lint check, and fix the problems, (for this project it will most likely be a few images, and text that needs a Creative Commons declaration.
Also, add the REUSE badge in the README when compliant.
Also,extend the workflow with a step for reuse compliance check.
@Ayko1595 If I add the last step, do you prefer it before or after the test step?
I would prefer it before, as one than can also in the future, add a few other steps like lint etc if you are into that, at the same time
like this example https://github.com/janderssonse/janderscripts/actions/runs/4420565672)
Contact Details
No response
What benefits does the suggestion solve?
REUSE (https://reuse.software/) is a growing straightforward standard that is a complement to the traditional LICENSE declarations for an Open Source project. In short, it tells the end user about everything else than code, (or if there are multiple licenses, about the specifics).
Why is this good? It tells anyone looking at the project what the intention are for the resources in the projects and the (re)usabilty. Another bonus is that it by design, forces the maintainers to think about images, docs and other things that are easily overlooked when going Open Source.
Feature suggestion description
Do an REUSE Lint check, and fix the problems, (for this project it will most likely be a few images, and text that needs a Creative Commons declaration. Also, add the REUSE badge in the README when compliant. Also,extend the workflow with a step for reuse compliance check.
@Ayko1595 If I add the last step, do you prefer it before or after the test step? I would prefer it before, as one than can also in the future, add a few other steps like lint etc if you are into that, at the same time like this example https://github.com/janderssonse/janderscripts/actions/runs/4420565672)
Alternative solutions
No response
Additional information
No response