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

Change licensing templates to use recommended format from REUSE v3.0 #453

Open
2 tasks
bernhardreiter opened this issue Oct 14, 2022 · 5 comments
Open
2 tasks

Comments

@bernhardreiter
Copy link

Currently licensing headers have lines like (for Go):

// Copyright (C) <year> <company>
//
// SPDX-License-Identifier: AGPL-3.0-or-later
//
// This program is free software: you can redistribute it and/or modify
...

the current standard https://reuse.software/spec/ v3.0 suggests to use

// SPDX-FileCopyrightText: <year> <company> <https://greenbone.net>
//
// SPDX-License-Identifier: AGPL-3.0-or-later
  • Change from Copyright (C) to SPDX-FileCopyrightText: and add contact address. Fullfils the SHOULD in the reuse spec.
  • Remove extra text This program is ... or at least reduce it. Saves space. Removes needs for updates.

Advantages: The rights holder(s) can be identified better automatically. The marking is kept flexible for the future.

@bernhardreiter
Copy link
Author

https://github.com/Intevation/pontos/tree/update-headers-go-reuse30 does both for the AGPL Go template with main...Intevation:pontos:update-headers-go-reuse30 .

Note that the command must be called with a contact address, e.g. like

pontos-update-header --company 'Greenbone Networks GmbH <https://greenbone.net>' -l AGPL-3.0-or-later -d cmd/

@bjoernricks
Copy link
Contributor

Could you create a PR and we also need a possibility to update and keep existing headers.

@bernhardreiter
Copy link
Author

@bjoernricks would you accept a PR that only updates AGPL and go?

@bjoernricks
Copy link
Contributor

We need this tool for updating the copyright in many repos and files. As long it stays backwards compatible or has an upgrade path and there are unit tests I am fine with every PR.

@cfi-gb
Copy link
Member

cfi-gb commented Apr 17, 2023

Now that #681 has been merged this might be closed.

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

No branches or pull requests

3 participants