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

GPL-*-only: Drop standard license headers? #579

Closed
wking opened this issue Dec 29, 2017 · 2 comments
Closed

GPL-*-only: Drop standard license headers? #579

wking opened this issue Dec 29, 2017 · 2 comments
Assignees

Comments

@wking
Copy link
Contributor

wking commented Dec 29, 2017

We currently provide these (e.g. here), but the license text only recommends the or-later header (e.g. here). That means the -only headers do not satisfy our:

Leave this field blank if there is no standard header as specifically defined in the license

condition. And I'm not even sure if they satisfy the potential weaker condition of:

Recommended by the license steward.

You might have to weaken to:

Frequently found in the wild.

and that's a big weakening. Although #489 is going that far for the license text, so maybe we're ok going that far for the headers. Either way, I think we need to either soften our header claims or remove the GPL-*-only headers.

@jlovejoy
Copy link
Member

sorry @wking but this is taking the explanation of the standard header field a bit too rigidly. The standard headers for GPL are very well known and used; the difference of the "any later version" language being present or removed in the license notice is the recommendation from the FSF (reiterated recently by RMS) and codified by the clause about later versions. No one has ever had an issue here before, notably when that definition was made at a time when the two variations were listed individually on the license list (as they now are again). This is a bit of a solution in search of a problem :)

@wking
Copy link
Contributor Author

wking commented Jan 11, 2018 via email

wking added a commit to wking/license-list-XML that referenced this issue Jan 11, 2018
…t (again)

In 983694a (schema/ListedLicense: Move standardLicenseHeader under
text as fileGrant, 2017-12-29, spdx#581), I'd removed the sibling option
based on our nominal standard license header policy [1].  Recent
maintainer statements have clarified the desire for sibling headers
[2,3], so this commit allows it again.  I'm not yet clear enough to
propose new policy wording.

[1]: https://spdx.org/spdx-license-list/license-list-overview#fields
[2]: spdx#579 (comment)
[3]: spdx#581 (comment)
wking added a commit to wking/license-list-XML that referenced this issue Jan 16, 2018
…t (again)

In 983694a (schema/ListedLicense: Move standardLicenseHeader under
text as fileGrant, 2017-12-29, spdx#581), I'd removed the sibling option
based on our nominal standard license header policy [1].  Recent
maintainer statements have clarified the desire for sibling headers
[2,3], so this commit allows it again.  I'm not yet clear enough to
propose new policy wording.

[1]: https://spdx.org/spdx-license-list/license-list-overview#fields
[2]: spdx#579 (comment)
[3]: spdx#581 (comment)
wking added a commit to wking/license-list-XML that referenced this issue Jan 26, 2018
…t (again)

In 983694a (schema/ListedLicense: Move standardLicenseHeader under
text as fileGrant, 2017-12-29, spdx#581), I'd removed the sibling option
based on our nominal standard license header policy [1].  Recent
maintainer statements have clarified the desire for sibling headers
[2,3], so this commit allows it again.  I'm not yet clear enough to
propose new policy wording.

[1]: https://spdx.org/spdx-license-list/license-list-overview#fields
[2]: spdx#579 (comment)
[3]: spdx#581 (comment)
wking added a commit to wking/license-list-XML that referenced this issue Jan 26, 2018
…t (again)

In 983694a (schema/ListedLicense: Move standardLicenseHeader under
text as fileGrant, 2017-12-29, spdx#581), I'd removed the sibling option
based on our nominal standard license header policy [1].  Recent
maintainer statements have clarified the desire for sibling headers
[2,3], so this commit allows it again.  I'm not yet clear enough to
propose new policy wording.

[1]: https://spdx.org/spdx-license-list/license-list-overview#fields
[2]: spdx#579 (comment)
[3]: spdx#581 (comment)
wking added a commit to wking/license-list-XML that referenced this issue Jan 26, 2018
…t (again)

In 983694a (schema/ListedLicense: Move standardLicenseHeader under
text as fileGrant, 2017-12-29, spdx#581), I'd removed the sibling option
based on our nominal standard license header policy [1].  Recent
maintainer statements have clarified the desire for sibling headers
[2,3], so this commit allows it again.  I'm not yet clear enough to
propose new policy wording.

[1]: https://spdx.org/spdx-license-list/license-list-overview#fields
[2]: spdx#579 (comment)
[3]: spdx#581 (comment)
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

2 participants