[lkml]   [2017]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license
And I swear I wrote the previous mail before I read this announcement:

But the actual practices there are pretty much what I'd expect as a
start (plus a list of acceptable licenses), they even use the same
identifiers as you are adding, but they also back them up with the
actual license texts in the source tree, which makes them a whole lot
more useful.

On Wed, Nov 08, 2017 at 07:11:21AM -0800, Christoph Hellwig wrote:
> On Wed, Nov 08, 2017 at 01:35:46PM +0100, Philippe Ombredanne wrote:
> > The benefits now and later:
> > - no distraction with licensing boilerplate cr*p in patches and files
> > - no guessing licensing needed when sending a patch
> > - anyone can grep the kernel tree for licensing, no extra tool needed
> > - Greg must feel really good about deleting so much things for once
> This patch didn't delete anything, it added random notes.
> I see now Greg deletes things from files he maintains which is even
> worse, given that the kernel tree doesn't document anywhere what these
> tags actually mean.
> So he deletes a lot of license tags and replaces them with tags he
> puts a great significance on, but which aren't defined. A quick googles
> shows some Linuxfoundation web page defines them, but they could change
> them any time they want, nevermind that we don't even have a reference
> to them either.
> >
> > The downsides:
> > - folks can no longer express their creativity in licensing texts like
> > licensing thermal code under the "therms" of the GPL [2]
> I'd love something like that to happen. But for that we don't need a
> sneaky patch that doesn't talk to kernel contributors.
> For that we need to
> a) agree on which licensing schemes we accept for future contributions
> b) cleary document that policy in the kernel tree
> c) reject anything that doesn't matter the above policy by manual
> and/or automated review
> An automated tag scheme might help with b) and c) above if done
> properly. But for that we need to document it, agree on it, discuss
> it with everyone involved, etc. None of that has happened. Instead
> Greg farted arcane tags that he thinks have a legal singnificance
> all over three three without talking to the people whos code he tagged,
> without any RFC or public discussion, without documenting what his
> tags mean or any future strategy towards making use of them.
---end quoted text---

 \ /
  Last update: 2017-11-08 21:14    [W:0.065 / U:1.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site