Skip to content
This repository was archived by the owner on Jan 13, 2025. It is now read-only.

NGI0 - Updating licensing aspects according REUSE specs v3#3

Open
lucaslasota wants to merge 1 commit into
stef:masterfrom
lucaslasota:master
Open

NGI0 - Updating licensing aspects according REUSE specs v3#3
lucaslasota wants to merge 1 commit into
stef:masterfrom
lucaslasota:master

Conversation

@lucaslasota

Copy link
Copy Markdown

Hi,

I am proposing some updates regarding copyright and licensing information according to REUSE[1]

Features:

  • SPDX copyright and license comment headers for all relevant files
  • LICENSE directory
  • Adoption of CC-BY-SA-4.0 for documentation (README for example)

Please feel free to accept this pull request if you find convenient.

Thanks

[1] https://reuse.software

@stef

stef commented Jul 24, 2020

Copy link
Copy Markdown
Owner

i wonder why not also put license headers/parallel files for the Makefile, json html and css files?

@lucaslasota

lucaslasota commented Jul 27, 2020

Copy link
Copy Markdown
Author

i wonder why not also put license headers/parallel files for the Makefile, json html and css files?

Good catch. For the Makefile you can set the comment headers with your project's license, so:

  • SPDX-FileCopyrightText: 2018, Marsiske Stefan pitchfork@ctrlc.hu
  • SPDX-License-Identifier: GPL-3.0-or-later

For the json files, you need to consider if the files are not particularly copyrightable, for example configuration files or automatically generated files. If you do not exercise any copyright over this file, you can use the CC0 license. This is functionally identical to putting the file in the public domain. Add the CC0 text to LICENSES and edit the file to contain:

  • SPDX-FileCopyrightText: 2018, Marsiske Stefan pitchfork@ctrlc.hu
  • SPDX-License-Identifier: CC0-1.0

On the other hand, if they contain data and configuration that are part of the code, edit the files with the project's main license.

For the css files, in case you were the one who wrote the code, edit the files with the the project's main license. If it is a library, than you need to add the headers with the information about the copyright holder and the original license.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants