Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp416726imm; Wed, 17 Oct 2018 02:15:26 -0700 (PDT) X-Google-Smtp-Source: ACcGV62MVAGh92cBALndsp6k6YsOTu5HtsVSjyWXZrouYBAEfvRW1t15bm1ifm5ce0oVtHVdbpwl X-Received: by 2002:a17:902:d917:: with SMTP id c23-v6mr24999577plz.206.1539767726349; Wed, 17 Oct 2018 02:15:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539767726; cv=none; d=google.com; s=arc-20160816; b=Krn3N6q4lWEJLXn1BwGPa30hmokLXJVhOWIYscOS/Pc7iW3oVtdbquF/bVGlXqAdET KP2AjD1uURv2VG6oxs6SeapTxOI98IXkWIZSVEZO0x3ppo4LIqqz9saHliKw3qVN14vi 8qEXN7VicGFTsivvaLoIpNT3io3IX36LM5OY/9wHjEBZbUl1SkUUx5FiViQ1vqxlACxc 4p9xtkNU+iMVWEjX1g+W10WGxI6r0p9DYucAmNlMEqXn+hypfNENrUObdiXTTcsO8z9O j9GTp3EJ6XW4ZAPOTKFNOKtbtsLyIT9lGDlQXJxpmU8Frel4nqoUvVEbGXDsHLwHjI62 ic1w== 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=hqy9omjfEgpu/euZHZjREbY/T6Tc0B7DvaAbD4nBliM=; b=OYrOvb1ZqQlbn7wPPquaYYsz02nNu3TzktOcQDAOf+57ZtJ4GWpvj5p542mwdufNEl SqB2F/P4x0HaHX9x6NWO6CEE8Uxu+1/rfmSR1GebcvA4pNz+unKeWZhs4CTJRWqp2AHw rK8U6bd+YfnpSCJ4Cs8x6XVrfgrQEeiDflVmhwuv2jhvVFNd8gn1Xxc4H0yx2EoSwvd8 T7Y9gZ7fVvQ1zK4xeFgT9igKqJ6+yKuIe69rD2jIQUVIjjfgtkc3miQ6320HiJhBazLM aoBEX3cirJXEr7oQp2mXTlVZLbxVsnHqJNtNLFuB5CE1ZgAq2gUE5aNOSuonbu6pX9U8 nYoQ== 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 o79-v6si17617854pfa.267.2018.10.17.02.15.11; Wed, 17 Oct 2018 02:15:26 -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 S1727188AbeJQRIS (ORCPT + 99 others); Wed, 17 Oct 2018 13:08:18 -0400 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:58401 "EHLO relay3-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726994AbeJQRIS (ORCPT ); Wed, 17 Oct 2018 13:08:18 -0400 X-Originating-IP: 50.39.174.102 Received: from localhost (50-39-174-102.bvtn.or.frontiernet.net [50.39.174.102]) (Authenticated sender: josh@joshtriplett.org) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id A8D586003E; Wed, 17 Oct 2018 09:13:28 +0000 (UTC) Date: Wed, 17 Oct 2018 02:13:26 -0700 From: Josh Triplett To: Geert Uytterhoeven Cc: ksummit-discuss@lists.linuxfoundation.org, linux-kernel@vger.kernel.org, James Bottomley , Tomi Valkeinen Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors Message-ID: <20181017091325.GA15991@localhost> References: <20181017071902.30102-1-geert@linux-m68k.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181017071902.30102-1-geert@linux-m68k.org> 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 Wed, Oct 17, 2018 at 09:19:01AM +0200, Geert Uytterhoeven wrote: > Providing an explicit list of discrimination factors may give the false > impression that discrimination based on other unlisted factors would be > allowed. This impression is, in fact, false, as has already been discussed elsewhere. I had hoped that discussion would suffice. As mentioned there: The original commit explicitly said "Explicit guidelines have demonstrated success in other projects and other areas of the kernel."; this is precisely the kind of explicit guideline it refers to. Listing explicit cases to cover does not imply other cases are not covered; it does, however, ensure that the listed cases *are*, and helps people know that they're covered. This patch is not OK, and defeats one of the purposes of the original change.