-
Notifications
You must be signed in to change notification settings - Fork 299
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
Comments
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 :) |
On Thu, Jan 11, 2018 at 08:50:55PM +0000, Jilayne Lovejoy wrote:
… 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) …
Can you link to FSF-recommended wording for the only forms? Then we
could weaken the policy to just “Recommended by the license steward”.
|
…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)
…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)
…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)
…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)
…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)
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:condition. And I'm not even sure if they satisfy the potential weaker condition of:
You might have to weaken to:
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.The text was updated successfully, but these errors were encountered: