The kernel's code of conflict
The kernel's code of conflict
Posted Mar 10, 2015 17:28 UTC (Tue) by jb.1234abcd (guest, #95827)In reply to: The kernel's code of conflict by raven667
Parent article: The kernel's code of conflict
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.
