community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niall Pemberton <niall.pember...@gmail.com>
Subject Re: Code of Conduct - Over Responding
Date Wed, 08 Jun 2016 22:27:24 GMT
On Tue, Jun 7, 2016 at 1:49 AM, Rich Bowen <rbowen@rcbowen.com> wrote:

>
>
> On 06/06/2016 05:21 PM, Niall Pemberton wrote:
> > On Mon, Jun 6, 2016 at 1:16 AM, Rich Bowen <rbowen@rcbowen.com> wrote:
> >
> >> The challenge with a CoC is knowing when to quit before becoming the
> >> thought police. Also, it should be things that are measurable and
> >> enforceable. I don't think this is either.
> >>
> >> What you are suggesting is really good advice, but isn't something we
> can
> >> enforce with policy.
> >>
> >
> > The Code of Conduct is mostly not "measurable and enforceable" and just
> > contains good advice - of the seven sections the only we can enforce is
> the
> > "Be careful in the words that we choose" section. I dont have a problem
> > with that because I see it as a tool to encourage people, rather than
> just
> > something to be enforced.
>
>
>
> Yes, I suppose you're right.
>
> Perhaps such an injunction could indeed be added to that section. Do you
> have a recommended patch?
>

I came up with adding the following in the "Be concise" section (attached
as a patch):

"Try not to dominate a thread, you don't have to respond to everyone. Pause
between sending emails to give others an opportunity to contribute to the
debate."

Niall



>
>
> --
> Rich Bowen - rbowen@rcbowen.com - @rbowen
> http://apachecon.com/ - @apachecon
>
>

Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message