feat: Add CODE_OF_CONDUCT.md by numinit · Pull Request #15 · JiaT75/STest
-
Regardless of the (undoubtedly funny) nature of that very document, I wish that “codes of conduct” weren’t such a big thing. “Don’t be a dick” is the only rule one would ever need, and there is not much bureaucracy needed to enforce that.
Rather I think what we should wish for is that they be unnecessary, or at least it be unnecessary for them to be as fleshed out as they are. I've found a lot of FOSS communities to be quite casually misogynistic—you could just say to ignore it and focus on the code, but it most certainly makes it harder to focus on the code when the community is subtly hostile towards you. If you think CoCs are unnecessary even for large projects then it's probably because you're not one of the demographics affected by the problems that led to CoCs proliferating. Once a project has enough of a community around it I think a CoC is reasonable enough in the current culture.
-
I’m all in favour of the OpenBSD mantra here: Shut up and code. People aren’t the same, and you can’t expect (e.g.) autists to share the same views about what’s nice and what’s rude as other persons.
The point I’m trying to make is that nice people won’t help the project by being nice people. IT projects are inherently technical, and that should be the only relevant unit of measurement here.
wrote last edited by [email protected]IT projects almost always have several different "correct" answers, which is why they generally lead to debate or discussion. That's where a code of conduct is needed.
Discussion between "shut up and code" people and everyone else doesn't tend to be a positive place to work without some boundaries. If you want people to volunteer for projects, you need to treat them with a baseline respect, and that baseline needs to be agreed on.
-
IT projects almost always have several different "correct" answers, which is why they generally lead to debate or discussion. That's where a code of conduct is needed.
Discussion between "shut up and code" people and everyone else doesn't tend to be a positive place to work without some boundaries. If you want people to volunteer for projects, you need to treat them with a baseline respect, and that baseline needs to be agreed on.
The baseline in technical projects is “make good products” though.
-
Not everyone has high emotional intelligence. There’s a fair bit of overlap between programmers/engineers and people on the spectrum. A good code of conduct effectively spells out how to avoid being a dick.
Being autistic, I am perfectly comfortable with “don’t be a dick”.
-
The baseline in technical projects is “make good products” though.
wrote last edited by [email protected]Sure. How?
Seems deceptively simple, but organizing people, especially people of incredibly divergent experiences and histories that may literally only share the traits of "is human" and "can code to varying degrees" is the complex part.
Saying "just do it right" is akin to saying "we dont need test or qa. Just code without bugs."
People are easily as messy as code itself, if not worse. We need some kind of organizing principles to work together, and thats what codes of conduct are.
-
For anyone out of the loop JiaTan was a malicious user known for the XZ Utils attack which almost caused catastrophic damages across the whole internet.
It's difficult to estimate just what the impact would have been had the attack not been caught by Andres Freund who happened to stumble across the attack while looking into performance issues.
Whoever JiaTan is, you can kindly deport yourself off the face of the planet. Thanks.
Is that their GitHub account or someone using the same name? If the former, how do they still have a GitHub account?
-
Regardless of the (undoubtedly funny) nature of that very document, I wish that “codes of conduct” weren’t such a big thing. “Don’t be a dick” is the only rule one would ever need, and there is not much bureaucracy needed to enforce that.
I don't mind CoC's that much, but I do really dislike Discord server rules that all have the same 10 completely obvious points and then make you search for a password in the rules. I don't see how having to look for a password in 3 pages of rules that says doxing is bad and being nice is good is going to filter out anyone but the impatient.
-
Regardless of the (undoubtedly funny) nature of that very document, I wish that “codes of conduct” weren’t such a big thing. “Don’t be a dick” is the only rule one would ever need, and there is not much bureaucracy needed to enforce that.
That's great until someone says "I'm not being a dick, I'm just telling the truth" while being a dick. This is especially easy to pull off against minorities, because the aforementioned "truth" can be based on stereotypes or inaccurate media portrayals.
-
Being autistic, I am perfectly comfortable with “don’t be a dick”.
What you’re comfortable with as a contributor is irrelevant. What matters is whether you understand the maintainers’ intent and whether the people you’re interacting with think you’re acting like a dick. Someone who’s bad at understanding how other people feel will likely be bad at predicting what behavior will come across as being a dick.
-
Also the proposed CoC is the CIA's Sabotage Field Manual
With an extra chapter, describing how to corrupt open source projects
