Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp800932imd; Fri, 26 Oct 2018 18:11:53 -0700 (PDT) X-Google-Smtp-Source: AJdET5f5CEXvnjtyopCTRPrdPbFx7H+3qBrSJSnhF97YkzOqm971IvAijeitlX28czI9kKgY0KtO X-Received: by 2002:a63:ee43:: with SMTP id n3-v6mr5253510pgk.234.1540602713453; Fri, 26 Oct 2018 18:11:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540602713; cv=none; d=google.com; s=arc-20160816; b=AEWJ/WZGrfkESvCKMKVQDzh/jw6g72UfeAsjwLXxNuOhBjaAnJS+9Xwj7o3teVyEC1 VHRA3H/0lQHch9oqBE4BweKwGHc1fXvZnyupIKPiCzwADtw0ul4lf/6SlrgbedN635LD Lv8uaxslVXmbuct82fwfF6HBBXPKzoFVSQY7dnj2zngKCugdAddaRubXjf5eVso7bJtM kMNbZU/iUNyIeo9/w3p3MLx1lLsFwuqlQgp9N3bjMWo5U65XIW8T6SNDO5hOyL+B7yWm OiB6MGlrSzQX7MZ5rUPSU/HbRu1EVwuHP5GOrXdcCzGe3oMSVhCCNs6s95EGyD55Xmpr zIPQ== 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=7t7X3QINs6IfbJl+gEBnF4i+xTTEaru2jNYEsNkesh8=; b=bvY/n6wzRX+ZBXXKg4KuF6rZca5taspImKkimey/uqscdY/K7anFZJbuYeSlcEO3rt aHSCLOqSDtgTMjw5uMxH1h+1rz/MaNdmB4Cl804KbUdjP2sowfsLZhcTB92npsHL8Rl8 Du9UXO/WcxDhZ5cP3CiQtJneKhoWcp9Ah0d/sRJspsHDTGh3t/bKnnltQ4FTPxJyE2mq IdGcODBpMg+SJDbwi0GDPJi+6gqvwsj19PtUQ68zouI+TLXm2RCSVQoiDVTOhXl5Np4W DIcvR+WyN/bhVnTBP4Wa7EN+M1/WnWftpYt6o/TbvuYODh8t7qZFwqISS1bzLTxsZPGf m5Tw== 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 34-v6si12591896pgy.249.2018.10.26.18.11.08; Fri, 26 Oct 2018 18:11:53 -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 S1726529AbeJ0Jt2 (ORCPT + 99 others); Sat, 27 Oct 2018 05:49:28 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:40383 "EHLO relay12.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726048AbeJ0Jt2 (ORCPT ); Sat, 27 Oct 2018 05:49:28 -0400 Received: from localhost (unknown [167.98.65.38]) (Authenticated sender: josh@joshtriplett.org) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 1571920000F; Sat, 27 Oct 2018 01:10:10 +0000 (UTC) Date: Sat, 27 Oct 2018 02:10:10 +0100 From: Josh Triplett To: NeilBrown Cc: Greg Kroah-Hartman , linux-kernel , Linus Torvalds , ksummit-discuss@lists.linuxfoundation.org, Mishi Choudhary Subject: Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document Message-ID: <20181027011010.GA29769@localhost> References: <20181020134908.GA32218@kroah.com> <87y3ar80ac.fsf@notabene.neil.brown.name> <20181021222608.GA24845@localhost> <875zxt919d.fsf@notabene.neil.brown.name> <20181024121622.GA10942@localhost> <87ftwt6850.fsf@notabene.neil.brown.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ftwt6850.fsf@notabene.neil.brown.name> 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 Fri, Oct 26, 2018 at 08:14:51AM +1100, NeilBrown wrote: > On Wed, Oct 24 2018, Josh Triplett wrote: > > > On Tue, Oct 23, 2018 at 07:26:06AM +1100, NeilBrown wrote: > >> On Sun, Oct 21 2018, Josh Triplett wrote: > >> > >> > On Mon, Oct 22, 2018 at 08:20:11AM +1100, NeilBrown wrote: > >> >> I call on you, Greg: > >> >> - to abandon this divisive attempt to impose a "Code of Conduct" > >> >> - to revert 8a104f8b5867c68 > >> >> - to return to your core competence of building a great team around > >> >> a great kernel > >> >> > >> >> #Isupportreversion > >> >> > >> >> I call on the community to consider what *does* need to be said, about > >> >> conduct, to people outside the community and who have recently joined. > >> >> What is the document that you would have liked to have read as you were > >> >> starting out? It is all too long ago for me to remember clearly, and so > >> >> much has changed. > >> > > >> > The document I would have liked to have read when starting out is > >> > currently checked into the source tree in > >> > Documentation/process/code-of-conduct.rst . > >> > >> I'm curious - what would you have gained by reading that document? > > > > I would have then had rather less of a pervasive feeling of "if I make > > even a single mistake I get made an example of in ways that will feed > > people's quotes files for years to come". > > Thanks for your reply. Certainly feeling safe is important, and having > clear statements that the community values and promotes psychological > safety is valuable. > > The old "code of conflict" said > If however, anyone feels personally abused, threatened, or otherwise > uncomfortable due to this process, that is not acceptable. > > would you have not found this a strong enough statement to ward off that > pervasive feeling? Not when that document started out effectively saying, in an elaborate way, "code > people". (Leaving aside that the more important detail would be the community actually acting consistently with the code of conduct it espoused.) > In the current code, would The "Our Pledge" section have been > sufficient, or do you think the other sections would have actually > helped you? "Our Standards" would have been at least as important to me personally, as would "Enforcement" (and more importantly, examples of that applying in practice and not just as empty words).