The kernel's code of conflict

Raven667, I agree with you completely. Incivility and rude behaviour are allowed and expected in war. But this isn't war; this is communal cooperation. And no community will long stand when one group of its members appear to strive to keep most members at each others' throats.

If submitted code stinks, say it stinks, explain why it stinks, and offer suggestions how to make it less smelly. In other words, take the opportunity to teach someone who probably wants to learn. People who have spent a lifetime learning and perfecting have a duty to pass along what they've learned to a new generation, and have a duty to recognize when they need to take a break from answering the same questions day after day, month after month, year after year, when the questions come from newbs who want to learn, who try to learn, who want to contribute to the community.

In a sentence, it takes a lot more energy to build than to raze. Build anyway.

Your hesitation is warranted, otherwise you would be misreading.
Every time you try to legislate that it is only a matter of time and you see
the poisonous effects of it. There are loosers only.
You do not want to be treated like crap, act accordingly. There is a good chance you will find support from others, unexpectedly.

The kernel's "code of conflict" is an act of deliberate laziness - passing
a problem to other people and expecting them to find a solution to YOUR
problem.
You could not work it out in your all wisdom, but you expect it from
others.
And if that leads to more rules, laws, and bylaws the better for everybody.
Really ?
Do you remember the convoluted Debian TC process regarding systemd adoption ? Pretty scary.
So, now you want to have a replay of that at Linux Foundation ?
In other words, the initiators of this idea placed a stinker in
Foundation's courtyard.
And the peanut gallery will enjoy it greatly from now on.