> To summarize what recently happened in the Python community: Someone uploaded a package named "slut". Their CoC-equivalent immediately removed it, bypassing all normal process. And then a long standing and well liked developer of many years was banned, fully (even Guido van Rossum wasn't allowed to speak with him!) for three months, for having the temerity to argue with the wrong people.
ah god i'm too tired for the need to take the python and linux foundation out behind the woodshed right now
@mangeurdenuage i think the fact their answer to "why do you need ultimate authority that bypasses the board?" is "ban :neocat_bottom:" is enough evidence the concept should be purged across all communities, but what do i know
@mangeurdenuage I think he is brushing over the issues with Rust in the kernel, it seems to me there is blame on both sides but the Rust people are definitely asking for changes to how things have been done in the kernel forever with regard to API compatibility between releases. My conclusion at the end of it was, if you want Rust in your kernel make your own kernel using Rust from the ground up, it's a burden to force Rust requirements on a very large and old C project
@mangeurdenuage some people whose opinion I trust are telling me that the author of the article is causing some of this because of a kind of style on the mailing list that unnecessarily puts people in defensive mode and isn't conducive to solving problems. I don't know but I supposed it is possible both that this person caused their own problems to get taken up with the CoC, while also being true that CoCs operating without transparency are scummy.
@icedquinn@mangeurdenuage My current belief is that while the idea is plausible in theory, in practice they all were created in bad faith to purge people using vague rules.
@icedquinn@mangeurdenuage a fundamental problem, and one I have had to grapple with from running this site, is it's impossible to write a set of rules to cover all misbehavior but the more rules you add the more you're killing the golden goose.
people went along with it because most of the docs were basically just re-stating netiquette and what was already the platform rules for the most part. but there is zero reason to have cock "teams" let alone weird bypass powers where they don't answer to anyone and have dictatorial control over the boards and shit.
@asa@mangeurdenuage he's better than he used to be but like the russian maintainer thing proved he'll still be a dickhead when he knows he can get away with it.
@sun@mangeurdenuage the problem is controllers are great at optics and you are basically staging a huge walkout over something they've successfully mindfucked people in to believing is a good thing.
they will counter-PR with the usual nazi drivel, and you'd need nontrivial resources to set up a proper fork and organize a "drop cock or walk" campaign
@sun@asa I think the matter is more complex considering the fundings of the LFoundation. But I don't want to elaborate on "politics". To say it could have been done in a much more peaceful (and punk) matter.
@sun@mangeurdenuage the good news is as the sociopaths accumulate cases of confirmed abuse it becomes easier to hold up that list as counter-evidence to justify a purge, but it still requires enough high profile people get unfairly injured to use that tactic
@mangeurdenuage@asa I don't want to re-litigate it but I'll restate my position: yes the LF is bound by US sanctions, Yes the sanctions make sense at a national level, yes it is justifiably offensive to people to see it happen anyway, yes tons of people were going to be unhappy when this inevitably happened, yes kernel core needed to communicate this as clearly as legally possible, no instead of doing that they did it in the way that was guaranteed to create the most conflict, yes it was completely unnecessary to do that.
@asa@sun All GPL project are by nature decentralized as it doesn't require a central authority. People can gladly contribute to the main linux kernel if they wish AND if they are accepted. If they are not then they are free as in freedom to fork and do the changes they do. Such is what is for example the linux-libre project. And it doesn't stop the main kernel people to bring back peaces made in the linux-libre fork into the main kernel. as the GPL allows sharing.
@sun@mangeurdenuage This is all on the record on the the Linux Kernel Mailing List (LKML)! Could someone provide links to relevant threads instead of all this vagueness?
And they have a point about in the message they link to "Get your head examined. And get the fuck out of here with this shit." but it seems to be an entirely appropriate thing to say, or what back in the days when the Linux project cared about the very difficult task of quality in a mass of C code they frequently didn't understand the behavior of.
The guy he's replying to is non-responsive, which might or might not be legit, but the claims both technical and hammering language seem to be legit, "Michal, if you think crashing processes is an acceptable alternative to error handling you have no business writing kernel code."
And he's being attacked by a notorious pajeet woman SJW in her CoC role, who is not working in good faith
And unless he's lying through his teeth the MM team was not working in good faith. He also apologized in the email thread.... Thus the pajeet's demands for a public apology are as someone in the thread noted a humiliation ritual, exactly what we've learned to expect from people from the subcontinent.
That said, Overstreet was (and maybe still is?) absolutely refusing to work with Team Linus/Kernel using the necessary technical processes they've developed, he just doesn't respect it one can infer. But this is not the way to address that problem, I wouldn't be surprised if this CoC committee action is also an underhanded effort to push him out of kernel development altogether.
I'll reply in my next posting on how all this mess has revealed the Linux kernel is in DEFCON 2 and I am moving to DEFCON 1 in looking at alternates.
In more detail, he says he apologized directly and privately to the Team Memory Management guy he insulted and implicitly says that almost immediately, and then after the CoC's ban published that email. He also made at least three other apologies in the email thread before that point.
I went through the whole thing again to confirm and correct my memory, here's the receipts including some reactions to the CoC mess:
And that sealed his fate, no way a woman pajeet is going to accept being called out like that. In general, putting pajeets including women in positions of power over others—technically not in their jati and at or below them in caste, but that's very likely or for the former guaranteed with non-pajeets— results in utterly callous treatment.
At base, no matter how much they seem to have adapted to Western culture with its claimed universal values, I'm pretty sure they just don't view these people as human or fully human. And, yes, I've experienced this first hand several times (but I know as peers moved to the US they can be OK or better).
@ThatWouldBeTelling@mangeurdenuage tbh I understand why people don't like him. he shouldn't be banned and coc rulings should be consistent and applied equally
"There are no instances anyone can point to where I've caused regressions in other subsystems, in the course of developing bcachefs. I have had people introduce regressions into my code without following proper channels, though."
Linus cited here was some error he made somewhere for bigendian systems.
@sun@icedquinn@mangeurdenuage this is evident if you dig into coraline ada ehmke (but i assume everyone knows already, i'm just here to give a keyword to google)
@sun@PostingHellbound@mangeurdenuage didn't foursquare try it too? i know this was like the leading conspiracy theory when people started gamifying crowd mobbing a place.
@sun@PostingHellbound@mangeurdenuage maybe whoever backed pokemon was inspired by the crowd mobbing mechanics that were being tried by the other places.
those were mostly marketing gimmicks to get you to go to a particular venue tho