2025-1-8 Linux Code of Conduct Why you need to Apologize

This is my thoughts put in anarchical order... have fun!

Why is it bad

  • affect community
  • affect trust in the project
  • affect funding

MAKE CLEAR THAT ITS NOT ONLY ONE ACT BUT MUTIPLE THAT WILL CORRUPT

lets think about how we can make a working system

  • we know that its bad so we need enforcement
  • so we need a Code of Conduct Committee that should also be in check by a higher auth Technical Advisory Board (TAB)
  • we see this situation, what would be the easiest way to solve? an apology
  • not done? the org need a way to show that they don't agree with the action so punitive action are needed.

Funny quotes from canada

https://en.wikipedia.org/wiki/Unparliamentary_language#Canada

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.

https://lore.kernel.org/citv2v6f33hoidq75xd2spaqxf7nl5wbmmzma4wgmrwpoqidhj@k453tmq7vdrk

FYI, without taking any stance on the issue under debate here, I find the

language used by Shuah on behalf of the Code of Conduct committee

extremely patronising and passive aggressive. This might be because I

do not have an American academic class background, but I would suggest

that the code of conduct committee should educate itself about

communicating without projecting this implicit cultural and class bias

so blatantly.

example of "A large number of people agreeing on anything does not automatically make

it right." when Tso said that most agree with COC enforcement approach

I'd suggest to avoid any kind of power-play like "we are more than you" in here.

I gave up long ago in the block layer after

the two people in charge there had repeatedly introduced silent data

corruption bugs into core block layer code that I'd written, without

CCing me, which I then had to debug, which they then ignored or put up

ridiculous fights over when reported, and now have turned petty on

subsequent block layer patches.

Also, let's rehash a bit:

  • This was worked out months ago, at Linus's behest
  • Scanning back through the original thread, I'm reminded by how very

much not one sided this was

  • And there hasn't been any hope of intelligent conversation with Shuah,

just broken record "we need you to do to this", so...

This is no longer a process I can take seriously. Linus will pull my

code, or he won't; it's out of my hands...

Night all.

Enforcement

The Code of Conduct Committee works with the individual to bring about change in their understanding of the importance to repair the damage caused by their behavior to the injured party and the long term negative impact on the community.

The goal is to reach a resolution which is agreeable to all parties. If working with the individual fails to bring about the desired outcome, the Code of Conduct Committee will evaluate other measures such as seeking public apology to repair the damage.

Seek public apology for the violation

The Code of Conduct Committee publicly calls out the behavior in the setting in which the violation has taken place, seeking public apology for the violation.

A public apology for the violation is the first step towards rebuilding the trust. Trust is essential for the continued success and health of the community which operates on trust and respect.