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

[NGIO] Updating licensing aspects according REUSE specs #2

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

Conversation

lucaslasota
Copy link

@lucaslasota lucaslasota commented Aug 19, 2020

Hello,

I am proposing some updates regarding copyright and licensing information. REUSE specifications intend to make licensing easier, setting one way to display all these legal information through comment headers on source files that can be human and machine readable.

Feel completely to adopt these specifications by merging this pull request.

REUSE Features

  • SPDX copyright and license comment headers for all relevant files
  • LICENSES directory with all licenses used on the repository
  • DEP5 file to bulk-license entire directories

Files missing copyright and licensing information

The repository contains files with missing copyright and licensing information. For those I did not add any headers. Examples:

  • pkg/systray/pid.go no copyright and license
  • branding/templates/osx no year of creation

For these files would be necessary firstly to determine who is the copyright, the year and then the chosen license.

Bundled libraries

It is necessary to update the README with the information about the libraries that are being bundled and distributed into the binaries. I added the basic information on README. Please check if there is anything to be added.

DEP5 file for bulk-licensing

There are icons and arts which licensing information I added to the .reuse/dep5 file on repository root. However, there is another dep5 file in branding/templates/debian/copyright which relates (as far I understood) to all files. Please check the consistency of this file.

Further REUSE compliance

In case you find REUSE useful for Bitmask, 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!

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