Received: by 10.223.164.221 with SMTP id h29csp2363172wrb; Mon, 23 Oct 2017 06:12:36 -0700 (PDT) X-Received: by 10.84.150.131 with SMTP id h3mr10520528plh.126.1508764356300; Mon, 23 Oct 2017 06:12:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508764356; cv=none; d=google.com; s=arc-20160816; b=QlQIw1IRDQV0lBXi/IdovW/RGx4y9ent7M1/qdKnLe8p+Vc/NUsQVJPb+h40YoNW7w qf7Lpmv6SpZBmk9+WiQ3xGSAEJRYFhPS+uSmQ3nnHB632cNQANHlZbHUSpxmq+N2/U1w H7N1IHIH1b2OGdXLgPRoNzFi5/upk6ukZKSdKHqPLIuvnQgQH+eWDwZSQFlajb4YsOyF 2GnHhsd6xIj8UtwKrKSJG1BrNceMDcokVcnHub4UkrL0VOBy12tTImpoaE4BENW4VRUp 6YKAtqOxxVsEoZ31F7WVsorTPI4ECO/CFr42H83pKNWnyrwn+4+1x8SEY6EoGH8mYWrS 3NBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=14rqqrWCYb2wP9jd4pI9QVUF7ot0m7WkiEEiQ+gjRSQ=; b=ehD2fsw+lGMOcBbYxKiRJIFrOq7r493szOLLKLS2v2Ai9Aqctiuzrqdb054u54f+Ba k/EbqLmFJAEnkqYBDc8+GAjVkpXm3ycukNul7nBrA8s8JFjSSssoU52y5NGJXKvOXaxI sEobP474gDmdNcZiEP1WksPHCJzlx/eo4/veJIZglQmDS1oct8hBoxF1EzRfOdCGG2Gl TpKWYDKE6dncs4KIHOwH2LOJFXkDgx2pGfRhj13Eo3oCKbPFzjKlbA4g7Cc5o887iggW SYvpnGSzye+KHGJ9i+xFxQVldCGGNW+rG+GdtAR9s1pTbI1NvPWg8lkoK+1GFc60Uvip RcBg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=jOaOysee; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s199si5245227pfs.356.2017.10.23.06.12.20; Mon, 23 Oct 2017 06:12:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=jOaOysee; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751363AbdJWNL5 (ORCPT + 99 others); Mon, 23 Oct 2017 09:11:57 -0400 Received: from mail-pg0-f68.google.com ([74.125.83.68]:56383 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751116AbdJWNLz (ORCPT ); Mon, 23 Oct 2017 09:11:55 -0400 Received: by mail-pg0-f68.google.com with SMTP id m18so11732271pgd.13 for ; Mon, 23 Oct 2017 06:11:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=14rqqrWCYb2wP9jd4pI9QVUF7ot0m7WkiEEiQ+gjRSQ=; b=jOaOysee4nPlq1zBUaqxYXQpE46ZGZsShJJPpgtf4apxZkhOe5/nDaWz+uXk0h43wE p5kuoKbCYr0nxeZ1NHkUA5EeiPn/N5E4pb8CvFoz7eScBaHVZCibl3wz9Rw7FZWe9uXe yTd1WQXIQV8gk1Q7Ut/e0AK9sQuwjbpujsRyqxHW9PLnt+sNJ8rySJpTzW8BE/IrDHfL FOqPkVD0CnrCADG1HcDnRer2urZLynXiOTFCjiMdyAGyLfhsZmpzxj+LXlwYCd4v5qLT i+yDkHZXthoCGE4TaHNMNmkZUpR/GaBdwzUD4kJKYfCQmZLMqDXchZVYinWD+AnXNbLw 6lCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=14rqqrWCYb2wP9jd4pI9QVUF7ot0m7WkiEEiQ+gjRSQ=; b=O46NR5O7brIo3BguHA3MIEiI2TKTBEPM1CcCTKElF68Bu/Fl+wwdxG1EK8AILO7O/g mApplGrtLFR6Sptfd5YgiEKehzsUoKVdXWPh+/ODBviAr+DUKbrhNlgOjE1JZz6jSHnC lFT+I7/AN466ZUmmQVoUokI2vn8trfnN3pzyb3h9KKHLO+tkenwxsk11GkwaMty7Hnzw IhhHoZRU2aK/AYLNazMqSnVd42zmeIx1A4/m+vuVueH8V9X6+m6xSwGZyo+KzTWvmlqc WI2yAvIuOIrAyOpRjzixnQIkKBD8a4KO2UsY1uGPJxXp2UVc9swR5tsr77OXoArBew93 /Kpg== X-Gm-Message-State: AMCzsaUnu98uRmay3f7KkXyipZiFweYko6+KI+tNmmNYHntET1AVqFUR 4s2yVCGrKq1P6ANXNaLc6WD6bMj6y8rCF0qEMd0= X-Google-Smtp-Source: ABhQp+R0y1Pj1IkoLj68SUtmZEo9MuPncl5MqGIt7Go6+7ebT9N5Ce3zRuixSSIR+n+U1lids+IX16j6l/uPHze39ug= X-Received: by 10.84.164.104 with SMTP id m37mr10290433plg.242.1508764315178; Mon, 23 Oct 2017 06:11:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.130.71 with HTTP; Mon, 23 Oct 2017 06:11:14 -0700 (PDT) In-Reply-To: <20171023075022.GA2821@kroah.com> References: <20171020192519.78772151@alans-desktop> <20171023075022.GA2821@kroah.com> From: Pavel Nikulin Date: Mon, 23 Oct 2017 16:11:14 +0300 Message-ID: Subject: Re: [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy To: Greg KH Cc: Alan Cox , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >If you don't agree with this, that's great, don't sign onto the >agreement. But as you don't seem to be part of our community in the >first place, I don't really understand your concern here at all. My last patch submitted to kernel was over a decade ago, yes I have not much say here. My worry is that people other than me and who were much more involved with kernel development will have themselves in hot water when it comes to enforcing their copyright. The people signing there effectively say: "we, to big extend, limit our options to call for expedient permanent license revocation" - the only thing that will ever tickle a commercial entity. When I first heard news of this and had a glancing look on the document, it looked to me almost as if it is a change to terms made on behalf of the "community," only after I read the document through few times over, I got an understanding of the semantics there. At least, lawyers you talk with now should consider moving a stament specifying who is making this statement to the start of the document, and to specify the undefined reference to a "community," so other people will not have to prove in court that the this statement was not done on their behalf if defendants will resort to "semantic equilibristics" with this document (and I am certainly sure some will). Attribution, and who and to whom one is giving permissions or promises is a big thing. I had to got to court two times in my life when my work on microcontroller boot loaders and a PID controller were used illegaly. In first case, the company tried to undermine my standing in court by bringing a back dated informal permission for use of project's code made on behalf of the whole project by a minor contributor who fraudulently issued it for money. As right in this case, that fraudulent informal permission had a "no sue" promise in it. If they were successful in proving the legal force of such permission, I bet a court in Russia, would've sided with them. The second time, I ever had to resort to legal action ended amicably, but we still had heated conversation whether I did or didn't alienate my right for attribution and copyright. On 23 October 2017 at 10:50, Greg KH wrote: > On Sat, Oct 21, 2017 at 10:16:12PM +0300, Pavel Nikulin wrote: >> If you say that your lawyers have comprehensively researched that, >> I can't say they did a good job. > > Is there a open source knowledgable lawyer that you recommend we work > with in place of the ones that were consulted for this statement? > > Remember, get two lawyers in a room, and you now have 3 opinions :) > > I know that not everyone we consulted agreed with everything in the > document, but that's to be expected. However, they all agreed that for > the issue we are currently facing, this statement will make a difference > and help resolve the issue. > > If you don't agree with this, that's great, don't sign onto the > agreement. But as you don't seem to be part of our community in the > first place, I don't really understand your concern here at all. > > thanks, > > greg k-h From 1582033852757206669@xxx Mon Oct 23 07:50:53 +0000 2017 X-GM-THRID: 1581405651618458163 X-Gmail-Labels: Inbox,Category Forums