Re: [GMG-Devel] Code of conduct

[Alex M (Coyo)]

On 04/14/2013 12:12 PM, Mu wrote:

Comments below.

2013/4/14 Christopher Allan Webber <address@hidden>

I've been thinking recently about the kind of community we've worked to
build in MediaGoblin.  I'm proud of this community... we've worked hard
to make this a welcoming place for newcomers and everyone.  I want it to
stay that way.

I currently don't have the energy to work in GMG, but the short time I did, I have to say that I felt this as a very very nice community. I wrote in Barrapunto (Spanish Slashdot): "And if you want to take a look of the community, try the IRC channel, you will see that they are a very nice people, far from the kind of hackers that are full of arrogance"

Not that anyone cares what I think, but to mediagoblin's credit, the mediagoblin team is relatively friendly to new users and contributors.

Mediagoblin is relatively free of the usual arrogance, cowardice, hypocrasy and deceitfulness I've come to associate with many FOSS project teams.

Thoughts?

I don't know if it would be appropriate to put into that document, or even if I will be able to express that in English. But one thing that I've learned is very important when you work with people is to try to think the best about the other persons, at least at the beginning.

For instance, if some guy says something that could be interpreted as sexist or not sexist, assume that he didn't mean that. If you have to correct him, instead of "that is very sexist" you could say "be careful that can be interpreted as sexist".

Another example, if you do some work and someone says that it is not an intelligent solution, assume that probably he does not mean to say that you are stupid.

Sometimes I've seen nasty conflicts between people that do not end because they think bad about the other. Applying this technique you can mediate between them explaining each other point of view.

As I said, I don't know if it is worth of reflecting into the CoC, but I wanted to share something that I learned and that have served me a lot when working with other people in difficult situations.

All I'll say on this subject is that it's the official policy of FreeNode, and expected in FOSS project teams.

However, there is a distinction between competent resolution of conflicts and shoving issues under the rug and pretending they don't exist.

With many FOSS projects, it's almost like they learned the theory of having a positive discussion by rote, but have zero comprehension of what any of that actually means, much less the reality of how to apply those, and when those rules do NOT apply.

Some anvils need to be dropped. Sometimes, the best thing you can do for a project is play devil's advocate. It's a thankless job, and being called a troll and idiot merely because you care enough to expend the time, energy, attention span and effort to point out flaws and possible improvements gets old pretty fast.

I've been called a troll many times, however the term "troll" has a very VERY specific meaning and definition. It is not a catch-all term for people you don't like, or people who say things you don't like to hear.

Trolls are individuals who have no life, no day job, no education, nothing to do but cause trouble.

Trolls have a very specific and well-documented mindset.

They are bored, and want to elicit a reaction out of you for their own amusement. That's it.

If I were a troll, there are more entertaining communities I could provoke. That's putting it VERY politely.

So, if anyone here wishes to insult me, all I ask is that you actually TRY.