Slashdot Mirror
Linux Kernel Adopts 'Code of Conflict'
Motor was one of several readers to note that a small patch recently added to the Linux kernel contains guidelines for discourse and dispute resolution within the community. It's called the "Code of Conflict." Quoting:
Your code and ideas behind it will be carefully reviewed, often resulting in critique and criticism. The review will almost always require improvements to the code before it can be included in the kernel. Know that this happens because everyone involved wants to see the best possible solution for the overall success of Linux. .... If however, anyone feels personally abused, threatened, or otherwise uncomfortable due to this process, that is not acceptable. ... As a reviewer of code, please strive to keep things civil and focused on the technical issues involved.
I guess Linus needs a new job.
Point 1, Out in the non open source world, you have to deal with dicks all the time. People who will scupper a project rather than not get their way and will constantly whine about everything. Why do you think most companies produce mediocre software products and the bigger they are, the closer to junk their stuff is.
To get those thick skin callouses, you have to have had a tough time, and that in turns means a bit of hurt. Its the same with software, you need to suffer these idiots a few times to not care about their whining.
**********
Point 2, This is about systemd isn't it? Really its the systemd thing again, people are deeply unhappy about this POS and you don't like them whining about it. They whine because they're unhappy, so what, you don't make them happy by forcing them to shut up, you make them happy by replacing the POS.
*********
Point 3, Offtopic, but I was late for the NSA Apple hack. I can't believe nobody pointed to the Linux backdoor attempt. The attempt to insert a backdoor that was added to code in the Linux Repository:
https://freedom-to-tinker.com/blog/felten/the-linux-backdoor-attempt-of-2003/
if ((options == (__WCLONE|__WALL)) && (current->uid = 0))
retval = -EINVAL;
So I guess links like this won't be appreciated.
Monstar L
The mean Linux team doesn't love my bad code!
The Linux kernel development effort is a very personal process compared to "traditional" ways of developing software. Your code and ideas behind it will be carefully reviewed, often resulting in critique and criticism. The review will almost always require improvements to the code before it can be included in the kernel. Know that this happens because everyone involved wants to see the best possible solution for the overall success of Linux. This development process has been proven to create the most robust operating system kernel ever, and we do not want to do anything to cause the quality of submission and eventual result to ever decrease.
If however, anyone feels personally abused, threatened, or otherwise uncomfortable due to this process, that is not acceptable. If so, please contact the Linux Foundation's Technical Advisory Board at , or the individual members, and they will work to resolve the issue to the best of their ability. For more information on who is on the Technical Advisory Board and what their role is, please see: http://www.linuxfoundation.org...
As a reviewer of code, please strive to keep things civil and focused on the technical issues involved. We are all humans, and frustrations can be high on both sides of the process. Try to keep in mind the immortal words of Bill and Ted, "Be excellent to each other."
"First they came for the slanderers and i said nothing."
One fragment leaves.
They can't even write civil code these days.
Don't be so sure of that.
The same thing was said when unwanted changes started happening to GNOME, Firefox and Debian.
With GNOME and Firefox, it was said early on that bad UI changes were just experimental, and could be ignored. If they were bad, they'd be reverted. Well, they did turn out to be bad. They were very bad, in fact. Yet they were not reverted. Once they were in place, they were pretty much considered as being locked in. Any critics were ridiculed and silenced. There was no going back at that point. What is the end result? GNOME is basically a dead project, and Firefox is near death.
A more recent example is, of course, Debian and systemd. Despite being absolutely disastrous for many Debian users (I'm talking about systems that no longer booted properly, which is about as bad as it gets), systemd is still being pushed upon the entire Debian community. Given its many flaws, it should never have made it into Debian in the first place, and even now that it has, it should be removed. But it won't be. Any critics are ridiculed and silenced. Like with GNOME and Firefox, we're seeing Debian dying before our very eyes.
Linus' leadership role is on its way out, I fear. Linux is done, too. It's suffering from the same disease that has affected GNOME, Firefox and Debian: technological correctness taking a backseat to political correctness. It's no longer considered acceptable to point out technical flaws with people's work. Instead, shitty software is accepted and even admired in some cases, while those who stand for doing things right get treated like utter shit and censored.
The only problem with Forking is then follows the Code of the Mafia
People on the whole are very Intolerant and Dangerous, if you code they share come.. and probably Not with good intentions
Its shear Lunacy to announce a Code Fork
Now those who stand in the way of important change, such as systemd like refactorizations, can be swept aside by claiming they violate this code of conflict when they criticize those trying to force a sea change.
Just like in Debian!
Standing in the way of progress... hmm your technical arguments are sound.
But it seems you dislike feminists / gays / women / minorities so we're gunna hafta let you go! Don't let the door hit you on the ass!
HAHAAA and we never even paied the fool a dime!
Death by political correctness hops onto the horizon.
It must have been something you assimilated. . . .
I fully expect Linux development to be destroyed by drama after this. More time will be devoted to coddling people's feelings than getting stuff done.
It recently came to me that the kind of behavior they talk about has traditionally been inoculation against the Dunning-Krueger effect.
This is exactly why I release my code as a proprietary open source license. Users are free to view and modify the source for their own purposes but not distribute modifications of it. Any ideas, and I do mean ANY that anyone has submitted as code or suggestion my teammates or I can (re)code from scratch with less headache on every front from code style to copyright assignment to implementation details, and even SJW nonsense like which pronouns comments should have (He, since it's the gender neutral one according to etymology) .
This means our team does more coding than project management, but we enjoy the former, not the latter.
April Fools Day is still weeks away. Hasn't anyone bothered to tell Linus that comedy is all about timing?
was a codename for systemd
It does not matter how every person feels. There are some people who get offended about almost anything. The above quote seems to be part of the extreme political correctness that is infecting society—I never imagined that Linux development would go that way. Additionally, if people feel “uncomfortable”, that might well be well warranted and help them to develop.
The quote would be better replaced by something that omits mention of feelings (which are internal and cannot be independently assessed). I suggest appealing to the “reasonable person”, as is commonly done in law. Here is an example: “Personal abuse and threats are unacceptable, as is any behavior that reasonable people would deem to be highly or persistently offensive”.
"If however, anyone feels personally abused, threatened, or otherwise uncomfortable due to this process, that is not acceptable."
I agree that's not acceptable. Stop feeling that way, you pansies.
It's great. So now feeling personally abused, threatened, or otherwise uncomfortable due to the process of critical examination of one's code is officially unacceptable. I'm liking that a lot. No one should care about anyone's "precious feelings". Let's keep things professional and emotion-free.
"If however, anyone feels personally abused, threatened, or otherwise uncomfortable due to this process, that is not acceptable."
It's not acceptable to feel abused/threatened/uncomfortable? That could have been worded better.
Let's see how this gets abused. There's plenty of people with far more delicate feels than skills at kernel-grade C.
Sometimes the masses have to learn it the hard way.
Yes, god forbid we should ever make anybody feel uncomfortable.
Might want to re-word that a bit.
Waterfox - a Firefox fork with legacy extension support, security updates and better privacy by default.
which pronouns comments should have (He, since it's the gender neutral one according to etymology) .
When I point that out, I always end it with a "That is the queen's English, after all."
Instead, shitty software is accepted and even admired in some cases, while those who stand for doing things right get treated like utter shit and censored.
The cult of hacked-together bash scripts needs to die.
You seem to take it for granted that the changes made to Firefox were universally bad for all users, and that everyone hates them.
As a regular user of Firefox on multiple platforms (Android, Fedora, and Windows), I have no problem with the changes they have made. I like the customization of the new menus and I like my tabs on top (though I could of course revert back to the old way if I wanted to, because they made it customizable and configurable). Almost everything they've done with Firefox from the 3.x releases up to the latest stable has been a net positive change for me, even when I've occasionally scratched my head at questionable decisions. Even their choices to completely disable certain broken websites have turned out for the better, because in every case where I've had such a broken website that I depended upon, the developers have come around to fixing the problem instead of making people run IE 6 or a patched browser that's deliberately insecure.
The UI changes are not what is killing Firefox. The disruptive security policy enhancements that break sites are not what is killing Firefox.
What's killing Firefox is the critical mass of Google Chrome, because it's being pre-loaded onto PCs out of the shop; is much faster for general use (faster page rendering and startup, so don't give me JS benchmark results), and more compatible with more sites. There is huge word of mouth support for Chrome among Joe User type people now -- people who swore by IE just a couple years ago. There's also Chrome's app store, which is causing many third party devs to release stuff that only supports Chrome, leaving competitors in the dust. Firefox may be able to match Chrome in some limited respect in some of these things, but they simply don't have the same word of mouth support that Chrome does among the vast majority of users. Oh, and it's the default browser on the mobile OS with the largest installed base in the world (since ICS anyway).
Rather than Firefox being especially bad in any particular way (except for its abysmal startup time on mechanical hard drives when the files aren't in page cache), it's pretty much just that Chrome is better for your regular user who doesn't care about privacy, just functionality and speed. They are losing to a superior competitor. Even though they are accelerating the rate at which Firefox is getting better, Chrome is accelerating way faster than they can muster.
Where the fuck did the systemd people get their mandate.
It's a coup.
Linux, as we knew it, is done.
The entire thing needs to be forked. From kernel to userland.
Linus is a balls-in-fat-woman's-purse git
.