NGI0 - Updating licensing aspects according REUSE #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
We have been working within the NGI0 framework, helping projects with their licensing and copyright management. After a quick check on your repository, I would like to propose some updates regarding copyright and licensing information. REUSE specifications intend to make licensing easier by setting one way to display all this legal information through comment headers on source files that can be human - and machine – readable.
The REUSE tool makes the process of applying licenses to files and compliance checking much easier. Check this screen-cast:
https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif
Feel completely free to adopt these specifications by merging this pull request.
REUSE Features:
SPDX copyright and license comment headers for all relevant files (first of all let me thank you for implementing such a good practice as displaying license and copyright information in individual files. I just added the REUSE specification to all of them).
LICENSES directory in the root of the project with the license used on the repository (Please notice that I added the AGPL-3.0-only text)
Files missing copyright and licensing information:
I added the comment headers with copyright and license information to all the copyrightable files. I noticed that most of the files had a correct copyright and license information. However, as good practice, I just added the consistent headers with the REUSE specifications.
I provided a more detailed licensing information to
READMEfile as well.Please also double check if the personal information in the headers is correct and consistent.
No contribution policy:
We could not find a very solid contribution policy in your project. Therefore, we strongly recommend you to improve it or create it. To get further information about this please check our documentation: https://download.fsfe.org/NGI0/V2/FSFE%20-%204%20-%20Free%20Software%20Contribution%20Policy.pdf
Further REUSE compliance
In case you find REUSE useful, we offer a wide range of tools to help you to continuously check and display compliance with the REUSE guidelines.
Hope that helps and thank you very much for the amazing job!