Linux CoC Announces Decision Following Recent Bcachefs Drama | Hacker News Reader

Linux CoC Announces Decision Following Recent Bcachefs Drama

phoronix.com

16 pointslaktak11 comments

You are big meanie, so we won’t take your FREE LABOUR THAT BENEFITS US all? What matter of mental illness is this? We’ll punish you voluntarily giving us free labour by not taking it? This is from the same series as “I’ll piss off the lottery people by not accepting my winnings”?

I genuinely hope he takes the hint and never contributes again. If this is the thanks you get for thousands of hours of free work, act accordingly.

What would you propose as punishments for CoC violations like these?

A nursery rhyme. “Sticks and stones may break my bones, but words will never hurt me”

Toxic people do hurt communities though, especially volunteer communities. If you let people be their worst selves, you'll lose a bunch of people who don't want to deal with that.

I wouldn't think that'd be a hard sell here, you've seen the HN guidelines, right? Those and the moderation in practice are a lot of why anyone is here.

Did you read the discussion on the mailing list in question? I advise reading it so you may properly form your own opinion instead of assuming based on headline

Yes, I did.

I prefer people stay civil but CoC is not a smoking gun. CoC easily turns into another form of toxic. I've seen it happen on a few projects, NixOs is a great example of CoC Stasi going crazy.

Doesn't appear to be what's happening here though, or in Linux in general.

Linux seems to have f bomb drama every few years. I disagree about the CoC thing though any place that treats "our Community Guidelines" like it's the Constitution are weird. Not everyone likes to report. After X revisions and N years it excludes the people who didn't want to (or couldn't) report.

Five Rosaries and seventeen TPS reports filed in triplicate.

the offending message seems to say:

> Michal, if you think crashing processes is an acceptable alternative to error handling _you have no business writing kernel code_.

> You have been stridently arguing for one bad idea after another, and it's an insult to those of us who do give a shit about writing reliable software.

> You're arguing against basic precepts of kernel programming.

> Get your head examined. And get the fuck out of here with this shit.

Reply on news.ycombinator.com