mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy
Date: Mon, 16 Oct 2017 15:50:19 +0100	[thread overview]
Message-ID: <1508165419.7595.10.camel@infradead.org> (raw)
In-Reply-To: <20171016134632.GA30345@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 3969 bytes --]

On Mon, 2017-10-16 at 15:46 +0200, Greg KH wrote:
>  I'll go add it and push out the updated post in a bit.

Thanks. I think it's especially important to show how useful
Conservancy's work in this area is.

If there's anyone who's nodding in approval to this document but who
*hasn't* joined Conservancy's group of kernel developers to help drive
the policies and decision-making there, I'd strongly recommend that you
do so: https://sfconservancy.org/copyleft-compliance/

> > conversations with the TAB on early drafts of this — but I'm a little
> > concerned that what we've ended up with is a bit one-sided. We're
> > giving something away, for nothing in return.
>
> I don't feel that is true at all, what we are doing here is providing a
> well-documented way toward compliance and the reinstatement of our
> license.  That's a key issue with regards to the existing trolls we are
> currently facing today, which we have to address in order to preserve
> our community.

Which trolls? Do you mean Broadcom or Patrick? :)

I think think this directly addresses either of them. Not unless you're
planning to get Patrick, or those who aspire to his methods, to sign up
to this document somehow?

I do agree that *both* of them need dealing with somehow though.

I'm actually *more* worried about the Broadcoms of this world, because
with Patrick there's an easy safeguard that most people seem to have
forgotten about — do not break the law. Make sure you are so obviously
complying with the GPL that any claim to the contrary would be
immediately thrown out of court and your costs awarded. (I know that's
over-simplifying quite a bit — but while I don't condone Patrick's
actions, at a personal level I do find it slightly hard to sympathise
with his victims.)

> > This would have been better if it specified that it applied to
> > *unintentional* violations, and also gave a time limit — automatic
> > reinstatement *only* happens if complete compliance is achieved within
> > 90 days, for example. That would help genuine developers who are only
> > *accidentally* committing a criminal offence through not paying enough
> > attention, while not giving succour to those who intentionally do so.
>
> Defining "unintentional" and "accidentally", might be a bit difficult,
> given that GPLv3 didn't even attempt to do something like that. 

Sure. But as you know, those who are *intentionally* violating the
licence will drag out their repeated candidate releases for years,
fixing one thing at a time and costing us loads of time and money as we
painstakingly investigate each attempt. While genuine mistakes are much
more quickly fixed.

So a time limit may well have worked as as primitive proxy for "intent".

We do have a time limit operating in *one* direction, to the benefit of
the criminal — if you stop offending within 30 days, your licence is
automatically reinstated. But we didn't do it in the opposite direction
— however long they take to come into compliance, we still promise that
their licence is reinstated by default when they do. Again it's one-
sided.

And more to the point, it deprives us of the *one* lever we have, short
of the last resort of legal action, for persuading them to come into
*complete* compliance as we define it.

My main concern is that we used to be able to iterate with a violator
until *we* agreed they were compliant. Now I fear that all they have to
do is get into the grey area where they don't think we'll really sue
for what's *left* — if we've signed away our ability to withhold the
licence from them for the original violations.

So given that Patrick was never going to sign this in the first place,
so it doesn't really protect anyone from his abuse, it seems that *all*
we've done is make live easier for the other kind of troll AFAICT. It's
a nice idea, but I'm just not sure it's really going to help overall.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]

  parent reply	other threads:[~2017-10-16 14:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16  9:25 Greg KH
2017-10-16  9:28 ` [PATCH] Documentation: Add a file explaining the Linux kernel license Greg KH
2017-10-16 13:16   ` Sumit Semwal
2017-10-18 17:21     ` Greg KH
2017-10-16 13:11 ` [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy David Woodhouse
2017-10-16 13:46   ` Greg KH
2017-10-16 14:31     ` Bradley M. Kuhn
2017-10-16 14:50     ` David Woodhouse [this message]
2017-10-17 14:57       ` Greg KH
2017-12-10  8:21       ` Pavel Machek
2017-10-17  8:06     ` Greg KH
2017-10-19 15:28 Pavel Nikulin
2017-10-20  7:29 ` Greg KH
2017-10-20 18:25 ` Alan Cox
2017-10-21  8:03   ` Greg KH
2017-10-21 19:16   ` Pavel Nikulin
2017-10-22  2:28     ` Bradley M. Kuhn
2017-10-23  7:50     ` Greg KH
2017-10-23 13:11       ` Pavel Nikulin
2017-10-23 14:35         ` Theodore Ts'o
2017-10-23 17:47           ` Damian Tometzki
2017-10-23 18:26           ` Damian Tometzki

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=1508165419.7595.10.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®