From: J Lovejoy <opensource@jilayne.com>
To: "Bradley M. Kuhn" <bkuhn@ebb.org>
Cc: linux-spdx@vger.kernel.org
Subject: Re: clarification on -only and -or-later
Date: Tue, 21 May 2019 12:05:37 -0600 [thread overview]
Message-ID: <595412F8-2FA4-4898-8B98-0251D493CBDA@jilayne.com> (raw)
In-Reply-To: <20190521172435.aez323uuvjcghejd@ebb.org>
HI Bradley,
Thanks for weighing in there. I think my original examples got a but lost in the various back and forth. So, let me reproduce and re-match:
1) where no version is indicated, the license text of GPL (all versions) tells us what to do, " If the Program does not specify a
version number of this License, you may choose any version ever published by the Free Software Foundation.”
- thus, use: SPDX-License-Identifier: GPL-1.0-or-later
example:
* May be copied or modified under the terms of the GNU General Public License
This is what Allison and I were going back and forth on. Net sum being: I was pointing out that under a literal reading of the license, such a unclear reference to just “GPL” would be GPL-1.0-or-later
I think this is where your point is spot on and confirms my memory of the various discussions:
> I agree that one can use GPL-1.0-or-later in this case well (which was
> discussed down thread), but I also agree with the argument (also downthread)
> that there is no *requirement* to include GPL-1.0 in the mix. The text of
> the COPYING file (i.e., GPLv2) is clear on this point, if we have code that
> does "not specify a version number of this License, you may choose any
> version ever published by the Free Software Foundation."
>
> Jilayne and I did a pretty deep dive on this question of the 'no version
> number specified' and I think our discussions made us sure that it does
> *not* mean GPL-2.0-only, because of the text above. I checked with
> Fontana too and he agrees with this as well.
I think what I was looking for here, was confirmation as to whether we want to do the “literal” GPL-1.0-or-later option that the license provides for, or trigger the option to “choose any version” and go with GPL-2.0-or-later for consistency of v2 across the kernel and for other reasons I believe you raised regarding GPL-1.0
Thoughts?
thanks,
Jilayne
> On May 21, 2019, at 11:24 AM, Bradley M. Kuhn <bkuhn@ebb.org> wrote:
>
> J Lovejoy wrote:
>> 3) where the license notice in the file simply points to the COPYING file or some other license file that contains the full text of GPL-2.0
>
>> This is a tougher call, as there isn’t really any arguably clear call, but
>> my thinking is that we’d use:
>
>> SPDX-License-Identifier: GPL-2.0-or-later
>
> I agree that one can use GPL-1.0-or-later in this case well (which was
> discussed down thread), but I also agree with the argument (also downthread)
> that there is no *requirement* to include GPL-1.0 in the mix. The text of
> the COPYING file (i.e., GPLv2) is clear on this point, if we have code that
> does "not specify a version number of this License, you may choose any
> version ever published by the Free Software Foundation."
>
> Jilayne and I did a pretty deep dive on this question of the 'no version
> number specified' and I think our discussions made us sure that it does
> *not* mean GPL-2.0-only, because of the text above. I checked with
> Fontana too and he agrees with this as well.
>
> Meta note: I've got a hectic week so I am not available to look at
> any Thomas' patch sets (and the threads they're generating) until this weekend,
> but I've set aside time on this Sunday morning for it. Looking forward to it!
>
> --
> Bradley M. Kuhn
>
> Pls. support the charity where I work, Software Freedom Conservancy:
> https://sfconservancy.org/supporter/
next prev parent reply other threads:[~2019-05-21 18:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 18:40 clarification on -only and -or-later J Lovejoy
2019-05-20 18:52 ` Greg KH
2019-05-20 19:26 ` J Lovejoy
2019-05-20 21:35 ` Allison Randal
2019-05-20 22:09 ` J Lovejoy
2019-05-20 22:19 ` Allison Randal
2019-05-20 22:52 ` J Lovejoy
2019-05-20 23:15 ` Allison Randal
2019-05-21 17:24 ` Bradley M. Kuhn
2019-05-21 18:05 ` J Lovejoy [this message]
2019-05-22 13:23 ` Greg KH
2019-05-22 13:53 ` Allison Randal
2019-05-22 14:00 ` Greg KH
2019-05-22 14:20 ` Thomas Gleixner
2019-05-22 14:30 ` Allison Randal
2019-05-22 15:45 ` Greg KH
2019-05-22 19:04 ` Bradley M. Kuhn
2019-05-22 14:22 ` Allison Randal
2019-05-22 15:03 ` J Lovejoy
[not found] ` <5EB6B416-F24C-4741-BC0E-6C1896E7A705@jilayne.com>
2019-05-21 21:14 ` Bradley M. Kuhn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=595412F8-2FA4-4898-8B98-0251D493CBDA@jilayne.com \
--to=opensource@jilayne.com \
--cc=bkuhn@ebb.org \
--cc=linux-spdx@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).