linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allison Randal <allison@lohutok.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-spdx@vger.kernel.org
Subject: Re: Meta-question on GPL compliance of this activity
Date: Mon, 27 May 2019 17:54:05 -0400	[thread overview]
Message-ID: <fc77dea6-e4cc-e7f0-4a97-a7ae1cb616b0@lohutok.net> (raw)
In-Reply-To: <20190525165643.GA13394@kroah.com>

On 5/25/19 12:56 PM, Greg KH wrote:
> 
> Again, remember we have over 65 thousand files in the kernel source
> tree.  Any single file that tries to reference them all, in any form, is
> going to be unworkable.

Yeah, we wouldn't be looking to track every single license notice change
throughout history, that wouldn't be reasonable. We want to narrow it
down to specific sets of changes that removed license notices and
replaced them with SPDX identifiers. And, ideally, display those with
the most minimal amount of information possible. It might even be
reasonable to generate the page as a list of links to the pretty diff
displays of the relevant commits, like:

https://github.com/torvalds/linux/commit/fd534e9b5fdcf9bab33c03cb3ade1a1ae5b23c20

That's the most faithful capture of the removed license notices we could
possibly provide, and is more accessible than simply saying that they're
in the git history. But, it might not satisfy the most conservative
definitions of "keep intact".

It seems like we're weighing effort against effectiveness here, but
without a clear definition of what effective means, other than our best
guess at how "keep intact" might be interpreted by someone, somewhere,
sometime.

Allison

  reply	other threads:[~2019-05-27 21:54 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
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 [this message]
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=fc77dea6-e4cc-e7f0-4a97-a7ae1cb616b0@lohutok.net \
    --to=allison@lohutok.net \
    --cc=gregkh@linuxfoundation.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).