Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp5269397imm; Tue, 9 Oct 2018 12:15:08 -0700 (PDT) X-Google-Smtp-Source: ACcGV63zuIvkdD1sn+GOlRl4kKOM7e2DSWC/KmcVv6omfwpoy1q1s7wgyDXIyV0D2pkaRVGNpd0j X-Received: by 2002:a17:902:82c5:: with SMTP id u5-v6mr29654115plz.227.1539112508541; Tue, 09 Oct 2018 12:15:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539112508; cv=none; d=google.com; s=arc-20160816; b=bt+bWZXwAzKQSowYFelw4n2gxht57u/RpcFXdY3oKiBfhp5JZR7xMabmcGrNicVtrh KOO+IUQIkvGgLDq08Wt9b4XoecSLxA/ZjAIWF4xNK/PsUwrXDwKd3WsjADP5xDGtkuEj UXPgu4l7kdcKZAaWZef/bFCQ/VimeTe6gdlXxsY4JrSR4ePxE/ETdC+NtBlzppNn3JIT Oul02jq0Nu/o7geyifHjlIeZxMc2Yc/RmwANBOotCZw5qps8PxkxL3yMHUuW9dtQiDDb NyHv/9Z++jTtDdEi1NCam9xXLVfqJCq0/+8OBE0seVr7iGrPhxchdrKClbIGYhQ2AEtm kw6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=FcOT8Caq0yf4w8IIg2ejc2VLDFKFC2IMwXlyA44DgoE=; b=T74UamzFz8IJdaLDRFcAGOPLXdanx9zVtd0dERvpvtolHv/B6XgJ1wyP7gwc3o92kT L9uIkfnAno3deuR8bZSpJacMQ+tBdPibhZCVHM8NkFHyrgxmEyO6IqoiS9LU+/16NaX3 TVs3Jf2Kt594w82K0GTjlE2rJAdiu4FngBK+e7N+R3Kcd60Sq+xhJBILJBseBPGqEipw 40hZ3cCEnTxyshlHs0ZxspRk7pfUT2jQRLjAIk3RBWl0SegR4H8ylygOO8aqi9neODFT 5KInHDZqo2Ly6c74K8PGCT12EJmuUvpLaC6KZzwZHkOzVi1a/jof7auDBjphskecOg3x 9WDQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t1-v6si21703912pgf.262.2018.10.09.12.14.39; Tue, 09 Oct 2018 12:15:08 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726897AbeJJCO5 (ORCPT + 99 others); Tue, 9 Oct 2018 22:14:57 -0400 Received: from relay10.mail.gandi.net ([217.70.178.230]:42887 "EHLO relay10.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726476AbeJJCO5 (ORCPT ); Tue, 9 Oct 2018 22:14:57 -0400 X-Greylist: delayed 86220 seconds by postgrey-1.27 at vger.kernel.org; Tue, 09 Oct 2018 22:14:56 EDT Received: from localhost (jfdmzpr03-ext.jf.intel.com [134.134.139.72]) (Authenticated sender: josh@joshtriplett.org) by relay10.mail.gandi.net (Postfix) with ESMTPSA id EA6AA240007; Tue, 9 Oct 2018 18:56:31 +0000 (UTC) Date: Tue, 9 Oct 2018 11:56:23 -0700 From: Josh Triplett To: Rainer Fiebig Cc: james.bottomley@hansenpartnership.com, linux-kernel@vger.kernel.org, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses Message-ID: <20181009185622.GA20960@localhost> References: <1538861738.4088.5.camel@HansenPartnership.com> <1538861799.4088.6.camel@HansenPartnership.com> <20181008152043.GA5796@localhost> <1718828.OxLgMoHbrt@siriux> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1718828.OxLgMoHbrt@siriux> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote: > Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett: > > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote: > > > 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. > > > > Upstream has now adopted a FAQ, which addresses this and many other > > questions. See https://www.contributor-covenant.org/faq . > > > > Might I suggest adding that link to the bottom of the document, instead? > > (And then, optionally, submitting entries for that FAQ.) > > > > The Code of Conflict has 28 lines, including the heading. > The Code of Conduct has 81 lines, including the heading. And it needs a FAQ. Hm. Yes, it turns out to be a more complicated problem than it was previously oversimplified to. People don't automatically share a common understanding.