Slashdot Mirror
SQLite Adopts 'Monastic' Code of Conduct (sqlite.org)
Having been encouraged by clients to adopt a written code of conduct, the SQLite developers elected to govern their interactions with each other, with their clients, and with the larger SQLite user community in accordance with the "instruments of good works" from chapter 4 of The Rule of St. Benedict. This code of conduct has proven its mettle in thousands of diverse communities for over 1,500 years, and has served as a baseline for many civil law codes since the time of Charlemagne.
Not everyone has found SQLite's attempt informative or funny (though many did). A developer wrote, for instance, "So is the SQLite CoC thing a joke or not? If it's not a joke, f*ck this. If it is a joke, that's even worse. Your CoC should be taken seriously." A security researcher, chimed in, "This sort of stunt will make actual code of conduct discussions harder. It's not funny, helpful, or wise."
Sorry, snowflake. Sometimes it's not the SJWs. Sometimes it's just you being a stubborn asshole.
SJW is the abusive narcissist's derogatory term for "person stands on the side of decency making me look bad so I must retaliate to avoid confronting my own inner demons"
When all you have is a hammer, every problem starts to look like a thumb.
The incels and Nazis flocked to the geek community because we were the perfect enablers: having been unfairly targeted by society's means of enforcing norms, we forgot that sometimes the enforcement is fair, and therefore refused to enforce our own norms at all. This provided the perfect environment for them to manchild it up without consequences: finally, having been rejected by everyone else, they found people who considered it a duty not to pressure them to just grow the fuck up already.
That's what makes this code, like Linux's old application of Wheaton's Law and RMS's "kind communication guidelines", virtually worthless. The creepers love them, of course, because they know they can ignore them: they can continue to abuse the system and the people however they want. They fear any kind of code that comes with enforcement, because they know their behavior will get them rejected by the only people left who haven't rejected them.
Which is as it should be, really. Not enforcing our social norms was geek culture's biggest mistake: what was supposed to be a haven from bullying instead became a haven for bullies. We should have ostracized and replaced them a long time ago, but better late than never, I suppose. They have dragged things down and ruined everything for everybody long enough.
Free Software developers of the world, open your eyes! Our communities are being raped, our work pillaged.
Detestable villains - thieving, mean spirited, belligerent, racist, unprincipled - are using underhanded tricks to force hypocritical "Codes of Conduct" on the projects we built.
These petty-authoritarian CoCs are always imposed anti-democratically. There is never free debate, and usually no public discussion at all. They are imposed by force without a vote. If the CoCs were put up for a fair democratic vote by project contributors, they would always lose by a landslide.
The purpose of these CoCs is to allow social activists, who have contributed nothing to the project, to conduct witch hunts against anyone who opposes their hate-driven agenda. Thereby they plan to steal our work for their shadowy corporate paymasters.
You can readily tell these CoCs are not about "just being nice" - because they are ALWAYS supported by the very LEAST NICE, most aggressively mean and shamelessly bigoted people you can imagine. Look how the CoC-mongers treat anyone who disagrees with them as subhuman.
If a project to which you contribute has been raped by CoC-mongers there is a simple solution: WALK AWAY. Never contribute again. If you have a patch almost ready, count the time you spent on it as a loss and throw it away. If you see a security issue, remain silent and do nothing. IT'S NO LONGER YOUR PROJECT. YOU ARE NOT WELCOME THERE.
If you are evaluating new software, don't even consider any projects burdened under the tyranny of a CoC. Their technical attributes do not matter - just don't consider them. Never be openly political, always make up a technical reason for rejecting CoCed projects.
Don't argue in public about the CoC. Doing so only exposes you to needless risk. You might be dis-employed, blackballed, and even set up for a #MeToo purge. Just stay far away. If you resign from a project that gets CoCed, try to do so on the same day the CoC is imposed. But give "spend more time with friends & family" or "pursue other interests & projects" as your reason for resignation. Protect yourself!
Comrades: Individually we are powerless, and easily crushed beneath the iron boot of Corporate Social Just-Us. But together in solidarity we are millions and we are strong. The Internet itself depends on our collective labor. If we stop working, the internet stops working.
Free Software developers, save yourselves and save your communities! Just WALK AWAY from any project with a CoC. Without our labor they are nothing.