community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: Code of Conduct - Over Responding
Date Mon, 06 Jun 2016 08:42:59 GMT
On 06/06/2016 01:16, Rich Bowen 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.

While the CoC might not be the best place for this good advice, there
are other places where it might work better:
http://community.apache.org/contributors/etiquette
http://www.apache.org/dev/contrib-email-tips

Mark

> 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
View raw message