Make hse-project repositories REUSE compliant #13
Assignees
Comments
|
Alex asked me for an example bill of materials. My website is Reuse compliant, so I ran |
|
From what I can tell, to be REUSE compliant we would do the following:
Am I missing anything? Questions:
|
I would recommend marking this in
Reuse will scan all your SPDX identifiers, and automatically download those for you.
Remove LICENSE.3rdparty.md and use
See above, but yes. |
|
I support this RFC. The benefits:
The downsides:
|
|
Assuming @smoyergh sees value, I propose this work just be tacked onto NFSE-5419. We will have to update the SPDX stuff anyways. And if we decide to remove copyright years, now would be a good opportunity as well. |
|
Agreed. For the SPDX-FileCopyrightText we can use the initial year and skip the range since it is good for 95 years from date of first publication. One question is how this is going to show up in GitHub, does it grok REUSE? For format let's use (for example): This adheres to all of REUSE, SPDX, and the US government. |
|
It looks like not if I look at my own repo (https://github.com/tristan957/tristan.partin.io). I did create a discussion though: https://github.com/orgs/community/discussions/44922. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is REUSE?
https://reuse.software/
REUSE FAQ:
Who is using REUSE?
See https://github.com/curl/curl for how the repository is laid out while being REUSE-compliant.
Main Benefits (imo)
checkossscriptBecoming REUSE Compliant
https://reuse.software/tutorial/
Time Estimate
1-2 days.
What is this not?
This proposal is not a relicensing of any software or materials belonging to
hse-project. This proposal will also not touchhse-mongo,hse-ycsb, or any other future forks of software.The text was updated successfully, but these errors were encountered: