[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 10 Oct 2018 14:19:17 -0300
From: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
To: Alan Cox <gnomes@...rguk.ukuu.org.uk>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
ksummit-discuss@...ts.linuxfoundation.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the
enforcement paragraph pending community discussion
Em Wed, 10 Oct 2018 16:53:08 +0100
Alan Cox <gnomes@...rguk.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
Powered by blists - more mailing lists