5 ms·
The current push for codes of conduct in software projects isn't about harassment per se. Realistically anyone can be harassed out of a community regardless of
by ajross 8y ago
The current push for codes of conduct in software projects isn't about harassment per se. Realistically anyone can be harassed out of a community regardless of rules. The point of the rules is to change the norms such that behavior that would otherwise have been exclusionary or just off-putting is specifically called out and recognized as "wrong".
"This code is fucking garbage and you should be ashamed" may or may not be "harassement" according to the intent of the writer or interpretation of the reader. But it's still wrong and we don't want that.
- frogeg 8y agoDo you really need a CoC to know someone who says "This code is fucking garbage and you should be ashamed" is an idiot? Do you really need a CoC to kick out someone who says that?
- ajross 8y agoThat kind of behavior is endemic in our community. So... yes, I guess we do.
- sp332 8y agoJust the opposite: you need the CoC to make sure they do get kicked out. Because for example if the writer of that comment is friends with the moderators of the forum, they might get a slap on the wrist and allowed to continue. Having a written CoC lets people know that the mods can be held accountable to the document. Another example making the same point, this time of actual harassment being ignored: https://www.youtube.com/watch?v=oxLENeCf3OA https://www.youtube.com/watch?v=oxLENeCf3OA
- iambvk 8y agoInstead of punishing the other party, you have a choice to ignore that person by setting a filter for that person's email. This way, if enough people filter-out, the person will be silenced. Others, who are more forgiving, would continue to receive that person's contributions. My rule is, I make decisions for myself and only myself.
- sp332 8y agoAt that point the abusers who move in will realize you can't see them and will harass your members with impunity. That doesn't seem like good community management. Actually it seems like throwing new members into the deep end (exposing them to every bad actor you already knew about) and at some point I suspect the only people who join your site will be malicious.
- jki275 8y agoYou can't be harassed if you don't listen.
- s73v3r_ 8y agoThat is flat out not true. Someone constantly attacking your character to others is going to have an effect. Those other people may be influenced by what that person says, and that will affect how they perceive you, which will in turn affect your involvement in the project.
- colllectorof 8y ago>Just the opposite: you need the CoC to make sure they do get kicked out. No, you don't. You don't need a CoC for sensible moderation. Good moderation is a combination of clear, actionable rules, good intentions and wisdom. Documents like Contributor's Covenant do not help with any of that. They're vague, their intentions are debatable, above all they're the exact opposite of "wise".
- mlazos 8y agoI would like to say no, but the world has proven me wrong in numerous projects that I’ve seen.
- pjc50 8y agoWell, Linus has been doing that for years and widely praised for it. And because kicking him out was inconceivable, people did nothing and concluded nothing could be done.
- bitL 8y agoWhat if the code was indeed garbage, and it cost a lot of time (super precious asset) and brain power (a precious asset) to evaluate and reject? Such a reaction would be understandable even if hurtful. No wonder people leaning towards the Asperger/autistic spectrum of brutal honesty would state that; such is their nature. What would you propose for addressing it? Ghosting? Silent blacklisting? English-style "there is a minor hiccup with the code"? A compiled list of what is wrong with the code (taking another few hours to prepare)? Any realistic ideas?
- yebyen 8y agoI honestly have long agreed with your premise, but I have to say I can't bring myself to agree with your whole statement. I see it more often each passing year, that someone who behaves a certain way is "charitably" accused of having some disorder, or "being on the spectrum." I do not accept this. And you can do better than "this code is fucking garbage." Even "this code is poorly done, try harder" is much better. It is more polite, and the more times I see this discussion, the more I like the idea that you should just treat your colleagues like ladies and gentlemen, or whatever. At a given point in my TDD learnings, I thought I invented a new term for a really powerful idea – "Shame-Driven Development" – turns out I was not the first person who named this idea. My idea of "SDD" is basically that noticing a failing test will motivate you to fix your code, so it's imperative that we set up CI early in development and shine a light on those failing tests at every opportunity. My idea is not important, if you google the term, you'll see that it really is a bigger idea than that, and all of the top links are perhaps obviously not presenting it in a positive light. You don't want "shame-driven development." Embarrassment is only a powerful motivator for the people you haven't used it on yet. Other people will seek to avoid being embarrassed, but the person you embarrass will only be left feeling bad.
- bitL 8y agoI don't believe SDD would work for these reasons: 1) people that start a serious open source product must be self-assured and innately isolated from any external community/pressure in order to avoid distractions from their goal. Shame has likely 0 effect, or negative (i.e. the person/group doing the shaming would get banned from any future interaction). It takes a certain type of person that is likely "very thorny" to the outside world unless persuaded by desired qualities in other people that want to interact. 2) those projects often start as angry reactions to what is happening in the outside "meatspace" (corruption, vendor lock-in, "voluntary" censorship, you-can-buy-everyone, selling underwhelming/dangerous stuff for a lot of money etc.); doing things differently when they start working inevitably invokes feelings of superiority over people that "just don't get it"/"noobs" and it's difficult to resist temptation of showing off. Or external people are viewed as "conformists to old ways" that would prevent better things from happening in order not to disrupt current status quo they benefit from, hence interacting with them is not desirable (and arguably dangerous until project really makes it) 3) having to wade through a lot of new issues daily and cherry pick the ones that are worth examining is time consuming and tiring. After doing this for a while it likely leads to anger and telling off someone is a way to vent 4) popular free/open source projects that made it are often targeted by people trying to subvert them for their hidden agendas; any original developer intelligent enough can be at least disturbed if not outraged by that; harsh reactions following. "How would you punish those subverters?" is a better question than to penalize a developer that was easily provoked to an angry outburst by those poking at their weak areas (and that's often trivial with honest technical folks) 5) priority of creators is often getting things done as fast as they could; "unnecessary social talk" is often viewed as a waste of effort/time, and honestly it often is, unfortunately. If they decide that at some point "talking nice" is leading to being more efficient, they would do work on it, but not before they perceive it that way. 6) Many junior developers think that they are entitled to some coding celebrity's special attention instead of taking the hard way, improving themselves and then contributing when they are finally able to.