3 ms·
Yeah really! cperciva had a great tweet on this a few days ago: "Probably the most important thing to keep in mind when reading the FreeBSD Code of Conduct is
by jdp23 9y ago
Yeah really! cperciva had a great tweet on this a few days ago: "Probably the most important thing to keep in mind when reading the FreeBSD Code of Conduct is that we weren't trying to change any rules. Rather, we were trying to elaborate on the rule under which the FreeBSD project has operated for years: Don't Be An Asshole."
- rurban 9y agoIt rather looks like an elaboration on the rule: "be free to label your critic as asshole"
- mwfunk 9y agoWell that's easy to avoid- don't give anyone ammunition with which to dismiss you as an asshole. It's totally unrelated to whether or not someone really is an asshole. It's trivially easy, and if it's not trivially easy, well that's a big giant glowing arrow pointing at an impending personal growth opportunity with a reward:effort ratio that's off the charts. Whether or not someone is an actual asshole, the ability to avoid misunderstandings is critical to moving forward and getting stuff done and not wasting time on distractions and petty arguments. CoC's are simply an organization's defense mechanism against pointless interpersonal chaos that doesn't belong on their mailing lists (or whatever) in the first place. Source: genetically inclined to be a total and complete asshole, have spent the last few decades trying to get better though.
- Joky 9y agoExactly what happened in LLVM as well: let make it explicit what the expectations have always been and how everyone (most) already behave! https://llvm.org/docs/CodeOfConduct.html https://llvm.org/docs/CodeOfConduct.html