Draft: NGI - Updating licensing aspects according to REUSE
Hello,
I work for the Free Software Foundation Europe (FSFE), and we have been working with the NGI 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 is an FSFE-developed initiative intended to make licensing easier by establishing a single way to display all copyright and licensing information through comment headers on source files that can be human- and machine-readable.
REUSE Features:
Copyright and Licensing Information in each file
One of the main features of REUSE is that each file in the repository contains copyright and license information with the help of a comment header. I have seen that quite some files on your repository already contained the headers, great work! What I did was add the legal information that is in the COPYING file in the respective files. Please note that REUSE has also an option to add this information for binary and uncommentable files - as I did - as well as for insignificant files - no copyrightable files such as .gitignore.
LICENSES directory in the root of the project with the licenses used on the repository:
I included in this directory the texts of the licenses used in your repository: AGPL3.0, CC-BY-4.0, CC-BY-SA-4.0. I did not do anything with the existing file COPYING in the root of the directory. It is up to you if you want to keep it or delete it, however, this won't affect the REUSE specification. Please also be aware, that if some pieces of your project use a different license, add such license text to the LICENSES/ directory as well as to the specific files.
Files missing copyright and licensing information:
There are still some files that do not contain the headers in directories such as lib/. Please feel free to check the REUSE documentation and the helper tool, and if you are interested in making your project REUSE-compliant, please add the legal information to the missing files. I am also available if you want support with the process.
Please also double-check if the personal information in the headers is correct and consistent, in the case of several copyright holders please update that information in the headers. In case you want to license certain files under a different license, special attention should also be paid to that aspect and such files should contain the appropriate SPDX tag.
Wide range of tools
In case you find REUSE useful, we offer other tools to help you continuously check and display compliance with the REUSE guidelines. For instance, you can automatically run reuse lint on every commit as a pre-commit hook for Git. And, it can be easily integrated into your existing CI/CD processes to continuously test your repository and its changes for REUSE compliance
Hope that helps and thank you very much for the amazing job!