[Development] Code of conduct.
aschmidt at dekaresearch.com
Fri Jun 22 14:01:27 CEST 2012
> I hate to point fingers but reading this made me sad :
That's actually an excellent example of how/why electronic
discussions often go sour. The basic algorithm is:
1. Begin discussion about something meaningful.
2. Person injects entirely off-track but known-to-be
highly inflammatory comment.
3. Other persons involved in the discussion react
reflexively and respond to the inflammation.
4. Meaningful conversation is forgotten amid the
Here in the United States, our political Right Wing has
absolutely perfected this method and has effectively brought
to a stop any online discussions among the Middle and the Left.
One answer is to ban the trolls, but that always seems draconian.
Another answer is simple but personally difficult to implement:
Don't feed the trolls.
The downside, of course, is that the trolls still take up
"airtime" and, unresponded to, naïve readers may assume that
there's no response to the trolls because they "have a point".
That's what makes it so personally difficult to implement
the second strategy.
And of course all this is nothing new; it has been such for
decades, ever since the first electronic discussion fora
were formed. But these days, the disruption technique has
really been perfected.
From: development-bounces+aschmidt=dekaresearch.com at qt-project.org [mailto:development-bounces+aschmidt=dekaresearch.com at qt-project.org] On Behalf Of Alexis Menard
Sent: Friday, June 22, 2012 6:29 AM
To: marius.storm-olsen at nokia.com
Cc: thiago.macieira at intel.com; development at qt-project.org
Subject: Re: [Development] Code of conduct.
On Fri, Jun 22, 2012 at 4:53 AM, <marius.storm-olsen at nokia.com> wrote:
> Right. I must admit i can't see which specific incident which triggered this thread now, i believe the community has behaved good lately. But i agree that a general code of conduct for all our forums (mails, IRC, reviews, bugreports, etc)
I hate to point fingers but reading this made me sad :
> So, let's grab one of the existing CoC for KDE, Linux.Conf and/or others, take the best of them and make it our own.
> Anyone feel like taking the lead on that, and drive the discussions until a conclusion?
> Sent from my Nokia N9
> On 6/22/12 1:16 ext Thiago Macieira wrote:
> On sexta-feira, 22 de junho de 2012 08.47.34, Rohan McGovern wrote:
>> Having a code of conduct may anyway be a good thing, but I
>> don't think it would have made a difference to the behavior from
>> non-contributors I think you're referring to in your mail.
>> No matter what you do, jerks will be jerks....
> That is true, but like you said it's a good thing. It's something we can point
> to when things start to get heated, even to non-contributors. And if we do
> need to take action, like moderating or banning someone from a mailing list,
> we can point to it and say it was not an arbitrary decision.
> I'd like to think that common sense should be enough to guide our conduct, but
> experience shows that common sense is not that common. And as the community
> grows, we might get more and more people with different cultures, different
> viewpoints and who might inadvertently step on other people's toes.
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel Open Source Technology Center
> Intel Sweden AB - Registration Number: 556189-6027
> Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
> Development mailing list
> Development at qt-project.org
Alexis Menard (darktears)
openBossa @ INdT - Instituto Nokia de Tecnologia
Development mailing list
Development at qt-project.org
Click https://www.mailcontrol.com/sr/tZs7q5!jSC3TndxI!oX7Us7Qlo!t9IHtzJUV8uV1LUCE1I3QgnPkjW5PWUCnv8VgatMIqsrnApWBj3G9C26e4g== to report this email as spam.
This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.
Please consider the environment before printing this email.
More information about the Development