Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reuse #130

Open
wants to merge 22 commits into
base: master
Choose a base branch
from
Open

Reuse #130

wants to merge 22 commits into from

Conversation

NSfsfe
Copy link

@NSfsfe NSfsfe commented Jul 11, 2022

Hello,

By way of introduction, I am Niharika Singhal from the Free Software Foundation Europe, and the REUSE Booster program. Thank you for contacting us and we are happy to help you out with the implementation of REUSE. After a check on your repository, I would like to propose some updates regarding your copyright and licensing information. The REUSE specifications intend to make licensing easier with best practices to display legal information through comment headers on source files that can be easily human and machine readable. You can check this screencast:
https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif

Please keep in mind that this merge request is intended to be a practical example of how REUSE looks like.

I would also like to make some remarks to be considered to make your full project REUSE compliant.

Feel completely free to adopt these specifications by merging this pull request.
REUSE Features:

SPDX copyright and license comment headers for all relevant files (please be aware that in the current state of the repository, I was able to add headers to all the directories. However, some files might miss this feature depending on the type of the file. For example, .owl, .rdf, .rq, .jar, .trig, .env files etc..) If you are interested in implementing REUSE specification, I hope this merge request can help you to do so.
LICENSES directory in the root of the project with the licenses used on the repository:

I included in this directory, the file that contained the license for your project (Apache 2.0 only) text. If some pieces of your project use a different license, please add their license text to the LICENSES directory.
Files missing copyright and licensing information:

I noticed that your project does not have the copyright and license information displayed in a comment header. According to the REUSE specifications, the comment headers MUST contain the SPDX Tag. For this, we recommend to update the headers, or at least the SPDX-License-Identifier as in this practical example.

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.

Please note that I used the REUSE helper tool to add the headers, so the tool automatically deleted the existing header (if any) and changed it to the SPDX format.

Image files:
I added the Apache 2.0 license to all of the image files. However, you can license other image files under different licenses as well and include the license in the LICENSES directory.

We can also do a follow up of this PR and further REUSE specification with a call. Feel free to reach me out.

Hope that helps and thank you very much for the amazing job!

Niharika Singhal - Trainee
Free Software Foundation Europe
Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290
Registered at Amtsgericht Hamburg, VR 17030 | https://fsfe.org/support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant