[gentoo-project] Re: [gentoo-core] Gentoo Code of Conduct

[hasufell <hasufell@gentoo.org>]

On 05/22/2013 04:48 PM, Luca Barbato wrote:
> On 05/22/2013 04:25 PM, hasufell wrote:
>> That's why I explained what I meant in more detail. It's not about
>> establishing a happy environment, but a professionel environment. We
>> are not primarily devs to have fun alltogether and make friends and
>> buddies.
>> Ofc, if that comes with our work, then it's fine.
> 
> You got your priorities wrong then.
> 
> You must get along with people, "professional" means nothing.
> 

Professional means to get along with people despite your personal
opinion/feelings about them, to point out their mistakes and to admit
your own mistakes.

So I think I got my priorities right.

>> In many professional environments yelling is the most efficient way to
>> prevent mistakes from happening again. It still does not imply insults
>> or disrespecting another person.
> 
> Not productive, not nice, not here please.
> 

I definitely made different experiences about that and I will continue
that behavior, because it does not collide with the code of conduct.

Example: when you break my ebuilds I will yell at you depending on how
severe that breakage is:
flaming/trolling? -- no, just being blunt and honest with you
Posting/participating only to incite drama or negativity? -- no, I'd PM
you anyway
Being judgmental, mean-spirited or insulting -- no, I'm only interested
in resolving the issue and to make sure it does not happen again
Constantly purveying misinformation -- unrelated

>> It's about making a lot of noise if something bad happened. And making
>> NO noise if nothing bad happened.
>> The latter is quite important too.
> 
> Making noise just makes difficult to get any kind of signal.
> 

FOSS does not work without noise, which just means pulling attention for
important problems and making people aware of their mistakes.

If you do not make noise, people will ignore the issue.

>> In the end it still does affect thousands(?) of users if we do stupid
>> things.
> 
> Not really, we have layers of protection to avoid that. Being careful is
> what prevents us from impacting users, not being rude.
> 

There is no layer of protection against eclass commits that break the tree.

If nobody yells when that happens, then it will happen again. And it does.

On 05/22/2013 05:10 PM, Rich Freeman wrote:> On Wed, May 22, 2013 at
10:48 AM, Luca Barbato <lu_zero@gentoo.org> wrote:
>> On 05/22/2013 04:25 PM, hasufell wrote:
>>> In many professional environments yelling is the most efficient way to
>>> prevent mistakes from happening again. It still does not imply insults
>>> or disrespecting another person.
>>
>> Not productive, not nice, not here please.
>
> Ditto.  And frankly, I've never worked in a corporation that would
> consider yelling acceptable behavior under any circumstances beyond
> overcoming ambient noise (the literal kind - like in a machine room).
>

Now I am unsure if you understood what I meant with "yelling", since I'm
not a native english speaker.
I do not mean shouting, but to make sure the other person is aware that
I am angry about what happened.
I have never worked anywhere, where this was not part of the hierarchy.
If you mess up and cause a hell of trouble my boss would not just
approach me and say "hey dude, there was a little problem".


I find parts of this discussion really silly to be honest.
If someone gets angry with me for a technical reason I do not have _any_
problem with that.
The problem is rather that people get angry without any technical
reason. Now I have a few theories why that is, but I'll keep that to myself.