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

Update references to GNU-family licenses in spec #89

Closed
swinslow opened this issue Jun 12, 2018 · 4 comments · Fixed by #183
Closed

Update references to GNU-family licenses in spec #89

swinslow opened this issue Jun 12, 2018 · 4 comments · Fixed by #183
Milestone

Comments

@swinslow
Copy link
Member

In connection with #6 to update the License List Appendix to the latest version, any references to the GNU family of licenses (GPL, LGPL, AGPL, GFDL) that are used in the spec should be updated to the new ID format for these licenses.

Old format: GPL-2.0; GPL-2.0+
New format: GPL-2.0-only; GPL-2.0-or-later

@wking
Copy link
Contributor

wking commented Jun 14, 2018

#37 (still in flight) does this for the license expression appendix.

@kestewart kestewart added this to the 2.2 milestone Jun 11, 2019
@kestewart
Copy link
Contributor

Yes, need a full scrub of 2.2 to update to latest GPL notation from license list.

@iamwillbar
Copy link
Collaborator

In the license expression specification we say "An SPDX License List Short Form Identifier with a unary"+" operator suffix to represent the current version of the license or any later version. For example: GPL-2.0+", is this deprecated and use of the -or-later license ID is preferred? Or is this still valid since it can be applied to any license?

@goneall
Copy link
Member

goneall commented Jan 17, 2020

GPL-2.0+", is this deprecated and use of the -or-later license ID is preferred?

-or-later license ID is preferred by the license steward.

This has a bit of complex history - although a bit out of date, this wiki page can give you a bit of background: https://wiki.spdx.org/view/Legal_Team/or-later-vs-unclear-disambiguation

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 a pull request may close this issue.

5 participants