From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 2A0B9C21 for ; Wed, 10 Oct 2018 17:19:24 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6352F7D5 for ; Wed, 10 Oct 2018 17:19:23 +0000 (UTC) Date: Wed, 10 Oct 2018 14:19:17 -0300 From: Mauro Carvalho Chehab To: Alan Cox Message-ID: <20181010141917.611fb5d8@coco.lan> In-Reply-To: <20181010165308.187aae51@alans-desktop> References: <1538861738.4088.5.camel@HansenPartnership.com> <1538861851.4088.7.camel@HansenPartnership.com> <20181008172303.4f06cd94@coco.lan> <20181010165308.187aae51@alans-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: James Bottomley , linux-kernel , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Em Wed, 10 Oct 2018 16:53:08 +0100 Alan Cox escreveu: > > -Maintainers have the right and responsibility to remove, edit, or reject > > +Maintainers may remove, edit, or reject > > comments, commits, code, wiki edits, issues, and other contributions that are > > not aligned to this Code of Conduct, or to ban temporarily or permanently any > > contributor for other behaviors that they deem inappropriate, threatening, > > > > The previous text seems too much legal for my taste. > > > > That is just as confusing. Maintainers have the right to remove, edit, > reject commits that *are* aligned with the code as well. Good point. Yeah, a maintainer can do whatever he thinks it is appropriate for a patch - even when it follows the CoC. > So what exactly is the point here ? The point is "responsibility" - that sounds like it is bounding a legal duty to a maintainer. While this makes sense for Github (as the company doesn't want to be responsible for sanitizing every single post), this doesn't work for e-mail based workflow, where the message is stored on a distributed way, as a maintainer can't "remove, edit or reject" an e-mail. Thanks, Mauro