From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Martin Kepplinger <martink@posteo.de>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] samples: replace outdated permission statement with SPDX identifiers
Date: Sat, 18 Nov 2017 11:17:56 +0100 [thread overview]
Message-ID: <20171118101756.GA8368@kroah.com> (raw)
In-Reply-To: <20171117155353.02950038@lwn.net>
On Fri, Nov 17, 2017 at 03:53:53PM -0700, Jonathan Corbet wrote:
> On Thu, 16 Nov 2017 12:41:10 +0100
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > > I'll fold this in, in the thread here. I guess this change is what Greg
> > > had in mind? Or would you prefer having including SPDX and removing
> > > permission statement seperately?
> >
> > I have been doing them in 2 steps, but only because the files I modified
> > were in different "chunks" (i.e. add missing SPDX identifiers to a bunch
> > of files in a directory, and then the second patch would remove the
> > license identifiers for all files in that directory). As that type of
> > patch flow doesn't make sense here, I think what you did was just fine.
>
> So I'll confess to being a little worried about removing the boilerplate:
>
> And it's important to notice that while adding a SPDX line should
> not really be controversial (as long as you get the license right,
> of course - Greg&co have the CSV files for everything, in case you
> want to check things you maintain), before removing the
> boiler-plate you really need to feel like you "own" the file.
> — Linus (https://lkml.org/lkml/2017/11/2/715)
>
> Are we sure that we're not going to get in trouble with the people who do
> "own" those files if we rip out the boilerplate? It would be good to have
> some clarity on when that can be done.
I have discussed this with many lawyers, and as SPDX is acknowledged as
a valid way to specify the license that a file is released under,
removing the "boilerplate" text is just fine according to all of them.
As a backup to this, I have verification from at the legal department of
at least one very large corporate copyright holder in the kernel that
this is fine with them, and they are glad to see this happen, as now we
will not have 700+ different ways to say "released under the GPL v2" in
the tree. You can see one of the patch series on lkml where I say I got
their approval as proof.
So yes, this should be fine, but of course, ask the copyright holder of
the file when doing this. I have been cc:ing the owners of the files
when I do this work, and have gotten no objections so far when doing
this work.
If anyone does object to this change, that's ok too. I'll be glad not
to merge the patch that does this. Which is why I have been splitting
the add-spdx and remove-boilerplate patches apart as they are two
different actions.
And if anyone wants me to talk to their lawyers about this, I'm more
than willing to do so, as for some reason I end up being the one doing
this a lot these days...
Hope this helps explain things better,
greg k-h
next prev parent reply other threads:[~2017-11-18 10:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 9:50 [PATCH] samples: replace FSF address with web source in license notices Martin Kepplinger
2017-11-15 6:29 ` Greg KH
2017-11-15 7:46 ` Martin Kepplinger
2017-11-15 8:45 ` Greg KH
2017-11-15 20:44 ` [PATCH] samples: replace outdated permission statement with SPDX identifiers Martin Kepplinger
2017-11-16 11:41 ` Greg KH
2017-11-17 22:53 ` Jonathan Corbet
2017-11-17 23:43 ` Martin Kepplinger
2017-11-18 0:13 ` Jonathan Corbet
2017-11-18 8:33 ` Martin Kepplinger
2017-11-18 10:20 ` Greg KH
2017-11-18 10:17 ` Greg KH [this message]
2017-11-18 11:21 ` Martin Kepplinger
2017-11-16 13:56 ` Philippe Ombredanne
2017-11-22 22:23 ` [PATCH] samples: replace FSF address with web source in license notices Pavel Machek
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=20171118101756.GA8368@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
/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