From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> To: Alan Cox <gnomes@lxorguk.ukuu.org.uk> Cc: James Bottomley <James.Bottomley@HansenPartnership.com>, linux-kernel <linux-kernel@vger.kernel.org>, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion Date: Wed, 10 Oct 2018 14:19:17 -0300 [thread overview] Message-ID: <20181010141917.611fb5d8@coco.lan> (raw) In-Reply-To: <20181010165308.187aae51@alans-desktop> Em Wed, 10 Oct 2018 16:53:08 +0100 Alan Cox <gnomes@lxorguk.ukuu.org.uk> 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
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> To: Alan Cox <gnomes@lxorguk.ukuu.org.uk> Cc: James Bottomley <James.Bottomley@HansenPartnership.com>, ksummit-discuss@lists.linuxfoundation.org, linux-kernel <linux-kernel@vger.kernel.org> Subject: Re: [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion Date: Wed, 10 Oct 2018 14:19:17 -0300 [thread overview] Message-ID: <20181010141917.611fb5d8@coco.lan> (raw) In-Reply-To: <20181010165308.187aae51@alans-desktop> Em Wed, 10 Oct 2018 16:53:08 +0100 Alan Cox <gnomes@lxorguk.ukuu.org.uk> 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
next prev parent reply other threads:[~2018-10-10 17:19 UTC|newest] Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-06 21:35 [Ksummit-discuss] [PATCH 0/2] code of conduct fixes James Bottomley 2018-10-06 21:35 ` James Bottomley 2018-10-06 21:36 ` [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley 2018-10-06 21:36 ` James Bottomley 2018-10-07 8:25 ` [Ksummit-discuss] " Geert Uytterhoeven 2018-10-07 8:25 ` Geert Uytterhoeven 2018-10-07 15:25 ` Shuah Khan 2018-10-07 15:25 ` Shuah Khan 2018-10-07 9:04 ` Daniel Vetter 2018-10-07 9:04 ` Daniel Vetter 2018-10-07 9:54 ` Hannes Reinecke 2018-10-07 15:29 ` James Bottomley 2018-10-08 19:49 ` Mauro Carvalho Chehab 2018-10-08 19:49 ` Mauro Carvalho Chehab 2018-10-07 17:53 ` Guenter Roeck 2018-10-07 22:25 ` Dave Airlie 2018-10-07 22:25 ` Dave Airlie 2018-10-07 22:56 ` Al Viro 2018-10-07 23:02 ` Al Viro 2018-10-07 23:37 ` Dave Airlie 2018-10-08 10:14 ` Mark Brown 2018-10-08 10:14 ` Mark Brown 2018-10-08 19:32 ` Mauro Carvalho Chehab 2018-10-08 19:32 ` Mauro Carvalho Chehab 2018-10-08 17:05 ` Luck, Tony 2018-10-08 17:05 ` Luck, Tony 2018-10-08 14:08 ` James Bottomley 2018-10-10 16:36 ` Pavel Machek 2018-10-10 16:36 ` Pavel Machek 2018-10-08 15:20 ` Josh Triplett 2018-10-08 15:20 ` Josh Triplett 2018-10-08 15:30 ` James Bottomley 2018-10-08 19:23 ` Mauro Carvalho Chehab 2018-10-08 19:23 ` Mauro Carvalho Chehab 2018-10-08 19:57 ` Josh Triplett 2018-10-09 10:55 ` Mark Brown 2018-10-09 18:29 ` Rainer Fiebig 2018-10-09 18:56 ` Josh Triplett 2018-10-09 19:38 ` Laurent Pinchart 2018-10-09 19:38 ` Laurent Pinchart 2018-10-09 19:44 ` James Bottomley 2018-10-10 7:22 ` Rainer Fiebig 2018-10-10 5:52 ` Rainer Fiebig 2018-10-10 7:08 ` Rainer Fiebig 2018-10-08 19:24 ` Mauro Carvalho Chehab 2018-10-08 19:24 ` Mauro Carvalho Chehab 2018-10-10 20:48 ` Frank Rowand 2018-10-06 21:37 ` [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley 2018-10-06 21:37 ` James Bottomley 2018-10-06 21:43 ` [Ksummit-discuss] " Tim.Bird 2018-10-06 21:43 ` Tim.Bird 2018-10-07 3:33 ` James Bottomley 2018-10-08 13:51 ` Tim.Bird 2018-10-08 13:51 ` Tim.Bird 2018-10-08 14:09 ` James Bottomley 2018-10-08 17:58 ` Tim.Bird 2018-10-08 17:58 ` Tim.Bird 2018-10-08 18:11 ` James Bottomley 2018-10-08 18:54 ` Tim.Bird 2018-10-08 18:54 ` Tim.Bird 2018-10-08 15:03 ` jonsmirl 2018-10-08 15:03 ` jonsmirl 2018-10-08 15:37 ` Alan Cox 2018-10-08 15:37 ` Alan Cox 2018-10-11 7:42 ` Dan Carpenter 2018-10-07 15:32 ` Shuah Khan 2018-10-07 15:32 ` Shuah Khan 2018-10-07 17:56 ` Guenter Roeck 2018-10-07 19:51 ` Geert Uytterhoeven 2018-10-07 19:51 ` Geert Uytterhoeven 2018-10-08 18:15 ` Chris Mason 2018-10-08 18:15 ` Chris Mason 2018-10-08 19:04 ` [Ksummit-discuss] " Josh Triplett 2018-10-08 20:23 ` Mauro Carvalho Chehab 2018-10-08 20:23 ` Mauro Carvalho Chehab 2018-10-10 15:53 ` Alan Cox 2018-10-10 15:53 ` Alan Cox 2018-10-10 17:19 ` Mauro Carvalho Chehab [this message] 2018-10-10 17:19 ` Mauro Carvalho Chehab 2018-10-10 20:09 ` Alan Cox 2018-10-10 20:09 ` Alan Cox 2018-10-10 20:30 ` Mauro Carvalho Chehab 2018-10-10 20:30 ` Mauro Carvalho Chehab 2018-10-10 20:32 ` Dave Airlie 2018-10-07 17:11 ` [Ksummit-discuss] [PATCH 0/2] code of conduct fixes Daniel Vetter 2018-10-07 17:11 ` Daniel Vetter 2018-10-07 17:40 ` James Bottomley 2018-10-07 17:50 ` jonsmirl 2018-10-07 17:50 ` jonsmirl 2018-10-07 17:52 ` Daniel Vetter 2018-10-10 16:12 ` Pavel Machek 2018-10-10 16:12 ` Pavel Machek 2018-10-10 16:25 ` Randy Dunlap
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20181010141917.611fb5d8@coco.lan \ --to=mchehab+samsung@kernel.org \ --cc=James.Bottomley@HansenPartnership.com \ --cc=gnomes@lxorguk.ukuu.org.uk \ --cc=ksummit-discuss@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.