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 Mon, 06 Jun 2016 21:21:16 GMT
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.

Niall




> On Jun 5, 2016 8:00 PM, "Niall Pemberton" <niall.pemberton@gmail.com>
> wrote:
>
> > Hi,
> >
> > I really like the code of conduct, but I think it would be good to
> include
> > something about sending too many emails. Sometimes you get people who
> > dominate a thread, responding to almost everyone and they drain the
> energy
> > of others to take part.
> >
> > My suggestion is to add a sentence to the "Be concise" section, perhaps
> > something like the following:
> >
> > "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."
> >
> > WDYT?
> >
> > Niall
> >
>

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