linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: John Sullivan <johns@fsf.org>
Cc: J Lovejoy <opensource@jilayne.com>, linux-spdx@vger.kernel.org
Subject: Re: Meta-question on GPL compliance of this activity
Date: Sat, 1 Jun 2019 02:31:20 -0700	[thread overview]
Message-ID: <20190601093120.GA1783@kroah.com> (raw)
In-Reply-To: <87pnnydm63.fsf@wjsullivan.net>

On Fri, May 31, 2019 at 11:22:44PM -0400, John Sullivan wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
> 
> > On Wed, May 29, 2019 at 04:57:20PM -0400, John Sullivan wrote:
> >> Project copyrightholders can as always make their own decisions about
> >> questions like this. What Linux does will be looked to by others as a
> >> practice to model, so I'm interested to participate in the conversation
> >> here for that reason (I see there are also a few cases of actual FSF
> >> copyrighted materials up for consideration, so will try to watch for
> >> those but would also appreciate a ping if anyone can spare one as they
> >> come up).
> >
> > To help address any issues that you might have with your own files being
> > modified, could you please just submit a patch to add the proper SPDX
> > header and place whatever text you feel is "correct" in them?  That way
> > you know your files are fine.
> >
> > I'll gladly review and submit any patches you create for this, it would
> > be most helpful.  Same offer to any other copyright holder (Richard,
> > want to do this for all Red Hat owned files?)
> >
> 
> Yes, that is reasonable and I'll arrange for that.

Great!

> I'd like to avoid the race condition though, so also asking for any
> patches that may get circulated here to be flagged and held.

If you happen to notice them and flag them, that's fine.  But kernel
development is very much not "don't touch my file!" type of methodology.
That is what killed other open source projects, it is "first in-first
applied".

If you happen to miss any such file in these huge cleanups, that's fine,
just go back later and send a patch fixing it up to be whatever you
want, but we can't special-case anyone here, it's just not going to be
viable.

Just take an hour or so today and knock them out, you all already have
the list of all of your copyrighted files, so this shouldn't be much
work at all.  I'll be glad to queue that up with the rest of these types
of changes.

thanks,

greg k-h

  reply	other threads:[~2019-06-01 16:20 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 [this message]
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=20190601093120.GA1783@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=johns@fsf.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=opensource@jilayne.com \
    /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).