From: "Bradley M. Kuhn" <bkuhn@ebb.org>
To: linux-spdx@vger.kernel.org
Subject: Re: Meta-question on GPL compliance of this activity
Date: Wed, 22 May 2019 21:41:20 -0700 [thread overview]
Message-ID: <20190523044120.zi6anxxofswk5d6i@ebb.org> (raw)
In-Reply-To: <20190522133053.GE28920@kroah.com>
Greg KH wrote:
> Just use git history, we have it, why ignore it?
How do we reconcile the "keep intact all the notices" requirement with "the
info is in the Git history"?
Specifically:
Fontana and I are both worried about downstream users and their
susceptibility to license compliance infractions. GPLv2 says: "keep intact
all the notices that refer to this License".
From my perspective, I'd prefer if GPLv2 said instead something like: "ensure
that downstream recipients are informed of the all notices that referred to
this License and are able to request them somehow". But it doesn't, and we
can't change the text of GPLv2 (obviously). I suspect that's one reason why
LF's SPDX project advises the text that John kindly brought to our attention.
Linux is not (usually) distributed with its full Git history passed along for
the distribution ride; i.e., most Linux distribution recipients *don't*
receive a copy to the Git repository with the copy of Linux they receive.
The requirement to keep the notices intact is an inconvenient truth we must
deal with before we move Thomas' patches upstream.
--
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-23 4:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 19:58 [Batch 1 - patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_208.RULE Thomas Gleixner
2019-05-21 17:58 ` Meta-question on GPL compliance of this activity Richard Fontana
2019-05-21 18:59 ` J Lovejoy
2019-05-21 21:08 ` Bradley M. Kuhn
2019-05-22 9:40 ` Thomas Gleixner
2019-05-22 13:30 ` Greg KH
2019-05-23 4:41 ` Bradley M. Kuhn [this message]
2019-05-23 5:42 ` Thomas Gleixner
2019-05-22 16:14 ` J Lovejoy
2019-05-22 21:10 ` John Sullivan
2019-05-23 1:19 ` J Lovejoy
2019-05-23 6:06 ` Thomas Gleixner
2019-05-29 20:57 ` John Sullivan
2019-05-29 21:30 ` Greg KH
2019-06-01 3:22 ` John Sullivan
2019-06-01 9:31 ` Greg KH
2019-06-01 4:21 ` Richard Fontana
2019-05-24 4:33 ` Richard Fontana
2019-05-24 5:20 ` Greg KH
2019-05-24 20:24 ` Allison Randal
2019-05-25 1:07 ` Richard Fontana
2019-05-27 21:23 ` Allison Randal
2019-05-25 16:56 ` Greg KH
2019-05-27 21:54 ` Allison Randal
2019-05-28 7:21 ` Dominik Brodowski
2019-05-22 13:27 ` Greg KH
2019-05-22 14:16 ` Thomas Gleixner
2019-05-22 16:33 ` J Lovejoy
2019-05-22 16:52 ` Thomas Gleixner
2019-05-22 17:00 ` J Lovejoy
2022-06-06 20:11 ` [Batch 1 - patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_208.RULE Richard Fontana
2022-06-06 20:17 ` Thomas Gleixner
2022-06-07 18:12 ` Bradley M. Kuhn
2022-06-07 23:05 ` Thomas Gleixner
2022-06-08 8:33 ` Allison Randal
2022-06-08 14:04 ` Bradley M. Kuhn
2022-06-08 14:59 ` Allison Randal
2022-06-08 17:18 ` Bradley M. Kuhn
2022-06-08 18:54 ` Richard Fontana
2022-06-08 19:29 ` Bradley M. Kuhn
[not found] ` <02f4021f-63a5-4796-d790-2bacd37b90d2@jilayne.com>
2022-06-09 0:31 ` Bradley M. Kuhn
2022-06-09 4:51 ` J Lovejoy
2022-06-09 15:03 ` Bradley M. Kuhn
2022-06-09 2:35 ` Richard Fontana
2022-06-06 20:31 ` 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=20190523044120.zi6anxxofswk5d6i@ebb.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.