NGI0 - Updating licensing aspects according REUSE

[lnceballosz]

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 screencast:

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.

• LICENSES directory with the licenses used on the repository (Please be aware that I added the general license AGPL 3.0 or later. However, I also noticed that there are some files (e.g. mailpile/mailutils/generator.py) under the Python Software Foundation License 2, so please check individual files and add the header to the files under that license and the license text to the LICENSES directory)

• Associating Copyright/ Licensing information through a DEP5 file in large directories (In large image directories, like yours, where including a comment header for each image file is impossible or undesirable, you may display copyright and licensing information in a DEP5 file)

• Licensing and copyright display of image files. Please be aware that I licensed three images on the directory design/icons as an example of how to create a license file for an image file. However, I also noticed that you have some other image files in some other directories that I did not include in the dep5 file and that I recommend you to license as well.

Files missing copyright and licensing information:

I added the comment headers with copyright and license information to some of the files that lacked that information. I noticed a very good practice in adding licensing and copyright information to the file COPYING.md. However, following REUSE specifications, I added individual and consistent headers to the copyrightable files. Please also double check if the personal information in the headers is correct and consistent.

I improved a little bit the information regarding licensing in README file as well.

In .reuse folder I have created a dep5 file to bulk licensing four large image directories. Please accept this commit only if you intend to bulk licensing these files under the information on the header in the dep5. Otherwise, please modify the information in this dep5 file or please go ahead and follow the practical example I made to create specific license files for specific image files with the appropriate copyright and license information.

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!

[BjarniRunar]

Thanks for this! This is worthwhile, but per your recommendation I am going to hold off on merging until I can properly examine some of the details you mentioned above.