Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp3630621imm; Mon, 8 Oct 2018 07:10:11 -0700 (PDT) X-Google-Smtp-Source: ACcGV62rX0rsDyTCJv2aO+Z0m4CVQnEAzgVxl3wHsZQFrHJ9hwXhDqOWVK3vMI9m5Z78ZsjWdd0P X-Received: by 2002:a65:48cc:: with SMTP id o12-v6mr20396226pgs.22.1539007811203; Mon, 08 Oct 2018 07:10:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539007811; cv=none; d=google.com; s=arc-20160816; b=U2YN2/6/q+syJmhzZ3iYjlRaJ+V72KyVSrciA1qWDEZTJCYwx3YdAHOqyEM99sUIzm Ovv7nyUYtfTfQOzgfflsuxB/nSMSa7uGSe7Gs5yLQNP3H418nePPbc3OOgbg876HQ96X tTACF5YIms7Fw2RUdwieilnaFKGMu4taevW32StN1EtFLWL+W4/CZoNBkW+dH8nl3wk+ Prwtwq4NLE7XQDhU25Lfr87WC6hbXBXfayljrK2brAv0h+EYoCZK9Ji00EmRjllorgsB FIMuBS5enrfRsw/wzvzWSkBqE64/XBDvCtleizvaMda3SGs7T1ASZ4CNjDqFp4MMxG6e dhTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=X0qfdvSyS7yScDvmkBQQyLGLAFFcLl1d6l1WVA5rnwM=; b=D/zrtvkl1+DI9Di26pAfym2vOSBvnN/sYjDLpIxz6V6Xr7aK5oLSAt6NB7tlPlYreX hxiczUoIYBh3KK2nVnnW5m4Xqf5P9obKiEaAtF0UuLlcZy1c+qA6JzTs9ldvhx+ov1u8 tWMakCgCm/qEup2n05Rp5wuQRQ9REfrCdZ1oawgpX525ONSU5MPHwariC9woj+BR78fn 6fiqpN/va/IDS0tu6QM/bafqYP9dizWuLTxVR84QBWlFmvBimqNgswjo81ykG8amsbMK Ank0CpfoxCK6LrUOWOx0gBZ0nltwetVEK86U0oCtJOZnPAspGx+M4eF3Wma1vrr0y2QH AHkQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@hansenpartnership.com header.s=20151216 header.b=hr7VqVS2; 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=fail (p=NONE sp=NONE dis=NONE) header.from=hansenpartnership.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1-v6si8735513pln.388.2018.10.08.07.09.56; Mon, 08 Oct 2018 07:10:11 -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=fail header.i=@hansenpartnership.com header.s=20151216 header.b=hr7VqVS2; 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=fail (p=NONE sp=NONE dis=NONE) header.from=hansenpartnership.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726418AbeJHVUV (ORCPT + 99 others); Mon, 8 Oct 2018 17:20:21 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:42758 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726056AbeJHVUV (ORCPT ); Mon, 8 Oct 2018 17:20:21 -0400 Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id BC4D48EE2EC; Mon, 8 Oct 2018 07:08:26 -0700 (PDT) Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 88DPsMC4owcH; Mon, 8 Oct 2018 07:08:26 -0700 (PDT) Received: from [153.66.254.242] (unknown [50.35.68.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id 17F468EE0FD; Mon, 8 Oct 2018 07:08:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1539007706; bh=PKREqNPr12/NEXMbDEFMaQlgJ5I6kZugtL4sM+F1jfk=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=hr7VqVS27kfNDrfdkm3O2gjKpbmfgO1sLeNS96DK5dTIk/gGpyqrw6NszkdYbMNOK ynmQx7eZ/xIR20ONpiMjXC0BYxaOpCtudd2xGq9sVbDDTuzKeOes/TJHMXcOM7Cfsl 4W5kAYJSBY8k6HQiPTa2YGHkiIQLIptzZCYABh+0= Message-ID: <1539007704.4344.2.camel@HansenPartnership.com> Subject: Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses From: James Bottomley To: Dave Airlie Cc: LKML , ksummit Date: Mon, 08 Oct 2018 07:08:24 -0700 In-Reply-To: References: <1538861738.4088.5.camel@HansenPartnership.com> <1538861799.4088.6.camel@HansenPartnership.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2018-10-08 at 08:25 +1000, Dave Airlie wrote: > On Sun, 7 Oct 2018 at 07:36, James Bottomley > wrote: > > > > From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 > > 2001 > > From: James Bottomley > > Date: Sat, 6 Oct 2018 14:21:56 -0700 > > Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about > > collecting email  addresses > > > > The current code of conduct has an ambiguity in the it considers > > publishing private information such as email addresses unacceptable > > behaviour.  Since the Linux kernel collects and publishes email > > addresses as part of the patch process, add an exception clause for > > email addresses ordinarily collected by the project to correct this > > ambiguity. > > > > Signed-off-by: James Bottomley > om> > > --- > >  Documentation/process/code-of-conduct.rst | 2 +- > >  1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/Documentation/process/code-of-conduct.rst > > b/Documentation/process/code-of-conduct.rst > > index ab7c24b5478c..aa40e34e7785 100644 > > --- a/Documentation/process/code-of-conduct.rst > > +++ b/Documentation/process/code-of-conduct.rst > > @@ -31,7 +31,7 @@ Examples of unacceptable behavior by participants > > include: > >  * Trolling, insulting/derogatory comments, and personal or > > political attacks > >  * Public or private harassment > >  * Publishing others’ private information, such as a physical or > > electronic > > -  address, without explicit permission > > +  address not ordinarily collected by the project, without > > explicit permission > >  * Other conduct which could reasonably be considered inappropriate > > in a professional setting > > > > I agree we want something like this, the question is whether we want > to change the CoC text from upstream, or clarify it in a separate > section. A Code of Conduct should be clear and not hedged around with footnotes and interpretations in my opinion, which is why I offered the patch like this. > This isn't a legally binding license or anything, but departing from > the upstream wording makes it tricker to merge new upstream versions > if they are considered appropriate. The way I look at this is that it's very much like a vendor driver. Some are mirror images of the source because we work closely with them; others could be forks. However, the process for vendor drivers is that we make them work for us first and then see how the vendor wants to handle it. Once we agree the shape of what we need I promise to try to push it back into the source ... is that good enough compromise? James