Linux Community To Adopt New Code of Conduct (kernel.org)

Following Linus Torvalds' public apology for his behavior over the years, the Linux Community said it will be adopting a new "Code of Conduct", which pledges to make "participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation."

Comments

Oh thank god

[Anonymous Coward]

Just imagine how quickly kernel technology will advance now that the mailing list is a designated safe space for special snowflakes.

Re:Oh thank god

[CoolVibe]

Patch rejected because the use of pointers is offensive. Pointing is rude, you know?

Re:Oh thank god

[CoolVibe]

Or, grow a skin and fix your damn code.

Re:Oh thank god

[cybe]

Decisions, decisions. Protect fragile **egos** from entitled children and get nothing done, or state things like they are and/or come off as a jerk in the process, while getting shit fixed... I'll take the latter.

Just fixing shit, don't get offended now.

Re:Oh thank god

[Crashmarik]

Or, more contributors will stick around because now they don't have to deal with abusive dicks like you

Someone thinks because they wear a man bun , a fedora, and attended a couple month how to code camp they are actually skilled and knowledgeable.

I am sure the project is going to love having more people working on it

https://en.wikipedia.org/wiki/...

https://en.wikipedia.org/wiki/...

Hopefully Linus is taking a break to hone his language skills so he can better destroy truly annoying people that have no business being near the kernel.

Re:Oh thank god

[Reservoir Penguin]

Well how many? And how many bullshit ideas were accepted because criticizing == triggering or worse denying "lived-in experience"?

Re:Oh thank god

[Crashmarik]

Your argument fails in the fact perhaps that guy with the man bun or a fedora and attended those code camps are actually a brilliant person who can really contribute.

LOL

Or you do want Linux coded by all guys with a short hair cut, suites, and has PHDs.

Have. But you can haz cheezberger

Coding is 25% intelligence and 75% effort.

For bad programmers.

What's really amazing is that you were too stupid to understand what the Fred Brooks software engineering links meant but you just tried to lecture someone who has been at it, longer than you have been alive.

Yeah I see Linux doing real well now / sarcasm

Re:Oh thank god

[techsoldaten]

None.

Linux is what it is as a result of the environment through which it arose.

There are no incredible ideas that went unnoticed because someone chose not to participate. There are very few original ideas about kernel development to begin with, inspiration comes mostly from hardware-side innovations that need to be incorporated. The idea that some meek, solitary genius would be the only one to notice is ridiculous.

Re:Oh thank god

[iMadeGhostzilla]

If he is too afraid to speak he can not be brilliant -- he hasn't had a chance to achieve brilliance without engaging with others and correcting, or standing his ground, based on their feedback.

Re: Oh thank god

[Anonymous Coward]

Exactly, the snowflakes need to understand that criticizing their idea doesn't mean that they as a person are being abused.

But too many people these days think they've been insulted just because someone doesn't agree with them.

Code of Conduct - Exact Text

[sinij]

Our Pledge
===========

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and
expression, level of experience, education, socio-economic status, nationality,
personal appearance, race, religion, or sexual identity and orientation.

Our Standards
=============

Examples of behavior that contributes to creating a positive environment
include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members


Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others’ private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting


Our Responsibilities
====================

Maintainers are responsible for clarifying the standards of acceptable behavior
and are expected to take appropriate and fair corrective action in response to
any instances of unacceptable behavior.

Maintainers have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, or to ban temporarily or permanently any
contributor for other behaviors that they deem inappropriate, threatening,
offensive, or harmful.

Scope
=====

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

Enforcement
===========

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the Technical Advisory Board (TAB) at
. All complaints will be reviewed and
investigated and will result in a response that is deemed necessary and
appropriate to the circumstances. The TAB is obligated to maintain
confidentiality with regard to the reporter of an incident. Further details of
specific enforcement policies may be posted separately.

Maintainers who do not follow or enforce the Code of Conduct in good faith may
face temporary or permanent repercussions as determined by other members of the
project’s leadership.

Re:Code of Conduct - Exact Text

[sinij]

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Looks good. So if you are not acting on behalf of the project, use official project email for communication, or were officially appointed representative, then your conduct has no relationship with this. Extreme example - Nazi would still be able to contribute as long as Nazi-related speech is kept out of commits, discussions, mailing list, and group events.

Representation of a project may be further defined and clarified by project maintainers.

Ugh, what? Why bother defining the above applicability rules and then inserting this gigantic "scope is what project maintainers decide the scope is"? This seems like a huge flaw that has to be fixed.

Re:Code of Conduct - Exact Text

[Anonymous Coward]

One thing is certain - codes of conduct exist to take projects away from maintainers. That's their purpose. They've been forced onto one project after another - they are the open source/free software version of entryism. Woolly wording... fuck all to do with actual technology... vague enough to be used to crucify men based on anonymous, worthless allegations.

Linus will end up regretting this. He'll be forced off the project by some bullshit made-up claim.

It's how this always happens. Mark my words.

Re:Code of Conduct - Exact Text

[bsDaemon]

Meanwhile, what was removed:

-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.

So, the language that states "best possible solution" has been replaced language related to the "good of the community." Personally, I don't interact with Linux as a community (if my name isn't enough of a tip-off). I consume it as a product, and I want the best product I can get in order to go do something else, because work. If they think they can still get the best product while airing all this drama in public and trying to build sticks to hit each other with, whatever. Good on them. What I fear will happen is more "my ignorance is just as valid as your expertise, and if you don't think so i'm going to beat you with the CoC until you stop hurting my feelings." That's not going to result in a better product.

But, not my community, not my responsibility. But now that most of the world runs on this stack, I just want to see a consistently high level of quality. Lack of quality makes it my problem, regardless of whether or not it is my responsibility.

Re: Code of Conduct - Exact Text

[bsDaemon]

FreeBSD has a lot of its own drama, yes. It also has some technical shortcomings that prevent me from using it at work. Some of of the attempts to fix those shortcomings have resulted in drama. The problem with literally everything is people, which sucks and can't be gotten away from. The further problem with open source is for some people it's a hobby, and for some people its work. And if it's your hobby, no one wants to be told your baby is ugly. If its work, you don't really want to deal with people insulting each other's babies. You just want to get your product done, with as few defects as possible.

But once you have a job, a family, and property and other stuff that needs attention and protection, interacting with the community becomes less of priority. And once it is, none of the shouting and jabbing and pushing around is worth it. I'm in the camp of "ignore the politics and just use the software" at this point, but in today's 24/7 live-streamed outrage culture, it is impossible to ignore the politics. The people with an agenda won't let themselves be ignored as long as you're plugged in.

So, computers for work only. Not really interested in spending hobby time on it anymore. I haven't been on IRC in months. I quit twitter because I couldn't spend more than 45 seconds on it without hating the whole world. Facebook is a time sink that isn't worth it. Frankly, Slashdot jumped the shark like 10 years ago but I still keep coming here anyway for reasons unknown. I should probably review that...

Re:Code of Conduct - Exact Text

[guruevi]

Actually, this is generally what happens to a project. It adopts a CoC or enough anonymous/SJW complaints are created, big contributors leave or are forced out, the project dies or slows because it is spending inane amounts of energy on political discussions rather than technical.

It happened with NodeJS, Kubernetes, LLVM, Tor, Debian all of which are decent projects but kind of 'stuck' now that boards and bug lists are overrun by "complaints" rather than technical discussions. If the SJW's don't get their way, they fork the code, take a number of core developers and none of those forks have actually produced a decent competitor to their parent rather, some of them have spawned their own forks because SJW infighting. Instead of getting a better product, a bunch of energy and time is wasted.

It's happening with Python and Linux now. Expect Linux to slow down immensely.

Re:Code of Conduct - Exact Text

[sinij]

Linux Community isn't a social network, support group, or law enforcement organization. It has a clearly defined purpose - to produce Linux kernel of best possible quality in shortest amount of time. You are trying to subvert and re-purpose this organization to suit your priorities and in doing so you are presuming to impose your values and your priorities on others. You are welcome to fork Linux and focus forked project on your specific list of priorities.

Re:Code of Conduct - Exact Text

[guruevi]

You don't see a clear trend in the graph you've provided? Contributions are trending upwards until the CoC is introduced, then they trend downwards until someone quits. I don't think we have enough data to see what the effect on the main contributors quitting is but you can see similar trends in other projects.

I'm not saying LLVM is dead, but as someone else said, there is a huge brain drain BACK to GCC which was the entire reason people jumped onto LLVM.

Same for NodeJS, there too you can see a huge difference, even though the number of contributors has risen, the number of commits goes down. Parts of this has to do that the SJW's split off NodeJS (a fork that is now dead), the leadership thought this was an issue back then, in a panic introduced a CoC which allowed the SJW to persecute another developer, the SJW then split it onto Ayo (now also dead). This drama keeps people from using their free time to do what they want as far as contributions and now they have to deal with leftist politics, it saps people from working on the core projects because either they start working on a fork that doesn't pan out or they just stay away from the drama.

I am a firm believer in free speech. Don't like what someone has to say, then ignore them. Persecutions and witch hunts kill organizations. I've seen it happen locally in various settings too, various clubs are dying because everyone has to introduce 'safe spaces' and falls over each other not to hurt someone's feelings.

Exceptions

[c]

I assume "works for Intel" is still fair game, right?

Re:Am I missing something?

[CoolVibe]

No clue. But they could have cut out complete swaths of text just by stating "We don't care what you are, what you do, or what your opinions are. Just show us the code. If it's good, we'll take it. If it's not, we'll see what we can salvage". All this fluffy bullshit is just that. Fluffy bullshit.

Can't be examined in isolation

[Etcetera]

I really, really, really wish these had been handled non-concurrently. It's virtually impossible not to analyze or comment on the two events together, which leads to some unsettling connotations for some.

While I think Linus taking a breather to maybe not be as much of a dick while still demanding high quality code is an admirable moment of self-reflection, the roots of this Code of Conduct are quite unsettling.

One really can't discuss the wording of the CoC without discussing the Contributor Covenant and the larger philosophical goals of the Post-Meritocracy manifesto.

From the CC:

A Code of Conduct for Open Source Projects
Open Source has always been a foundation of the Internet, and with the advent of social open source networks this is more true than ever. But free, libre, and open source projects suffer from a startling lack of diversity, with dramatically low representation by women, people of color, and other marginalized populations.

Part of this problem lies with the very structure of some projects: the use of insensitive language, thoughtless use of pronouns, assumptions of gender, and even sexualized or culturally insensitive names.

Marginalized people also suffer some of the unintended consequences of dogmatic insistence on meritocratic principles of governance. Studies have shown that organizational cultures that value meritocracy often result in greater inequality.

From the PMM:

Meritocracy is a founding principle of the open source movement, and the ideal of meritocracy is perpetuated throughout our field in the way people are recruited, hired, retained, promoted, and valued.

But meritocracy has consistently shown itself to mainly benefit those with privilege, to the exclusion of underrepresented people in technology. The idea of merit is in fact never clearly defined; rather, it seems to be a form of recognition, an acknowledgement that “this person is valuable insofar as they are like me.”

(If you are not familiar with criticisms of meritocracy, please refer to the resources on this page.)

It is time that we as an industry abandon the notion that merit is something that can be measured, can be pursued on equal terms by every individual, and can ever be distributed fairly.

These are explicitly political documents... and they should be addressed as such. I don't think anyone has a problem with "don't be a jerk, and don't make it personal" in an open source project. Arguably, Linus has stepped over the line on occasion. The adoption of this document goes far beyond rectifying a mere lack of teeth in telling people to "Be excellent to each other"

Re:Can't be examined in isolation

[sinij]

One really can't discuss the wording of the CoC without discussing the Contributor Covenant and the larger philosophical goals of the Post-Meritocracy manifesto

I think you can. Nothing in CoC states that you must also adopt the manifesto. Sure, this CoC was produced by dubious people with very questionable intentions. Likewise, GPL license is based on Stallman's ideas. This doesn't mean that we have to adopt all of the Stallman's extreme views about software in their entirety. I am still hopeful that sanity will prevail and it won't go past CoC. However, I do understand and share your concerns.

Re:Can't be examined in isolation

[atriusofbricia]

One really can't discuss the wording of the CoC without discussing the Contributor Covenant and the larger philosophical goals of the Post-Meritocracy manifesto

I think you can. Nothing in CoC states that you must also adopt the manifesto. Sure, this CoC was produced by dubious people with very questionable intentions. Likewise, GPL license is based on Stallman's ideas. This doesn't mean that we have to adopt all of the Stallman's extreme views about software in their entirety. I am still hopeful that sanity will prevail and it won't go past CoC. However, I do understand and share your concerns.

You're correct, the CoC doesn't absolutely require adopting the PMM. However, it would be very hard to ignore the fact that both were written by the same person with the same overall agenda in mind and what the previous person said is 100% correct, this is a political agenda and has nothing to do with technology and only relates to being respectful to people insofar as the ways in which that advances the political agenda in question.

The previous "code" Linux had was fine. If a change was needed, an amendment of "Also, don't be a dick" would have worked. However, they have ripped out a code which specifically called for quality and good engineering above all and replaced it with one written by someone who is, by their own words a "Notorious Social Justice Warrior". I don't know the person, I could be misinterpreting their words and maybe it is tongue-in-cheek. I tend to doubt it.

Linux: survived Microsoft, killed by SJWs

[IGnatius T Foobar]

This is the end of Linux as we know it. The "Code of Conduct" is teeming with words and phrases that indicate the project is now going to be policed by Social Justice Warriors who will micro-manage everything. It means that the Linux kernel is no longer a meritocracy.

The only "code of conduct" ought to be: "my code doesn't care about your feelings". You can't develop good code in a Safe Space.

Re:Linux: survived Microsoft, killed by SJWs

[Anonymous Coward]

"The end of Linux as we know it"? Gee, overreach much?

No, it won't be the end of Linux as we know it. If anything it could make Linux better by not pushing away code contributors thanks to a sometimes toxic community.

The issue, which you surely know and are willfully ignoring/misrepresenting is NOT that my code cares about your feelings, but that people in the development community shouldn't be assholes when dealing with each other.

And you can write good code in a "Safe Space". I've worked at several companies that had very strict rules about conduct in code reviews, problem reporting, and, more generally, meetings. And you know what? We did good and sometimes great work, because we could focus on our work, the stuff we loved about coding, and not the petty personal crap that tends to creep into nearly all workplaces. If someone got out of line, no one even had to complain; word of what happened would inevitably get to mgmt who would discreetly step in, talk to the offender behind closed doors, and that would be the end of it.

If you value your opportunities to be a jerk more than creating a comfortable, productive work environment, then there's nothing anyone can do to help you.

Re:Linux: survived Microsoft, killed by SJWs

[religionofpeas]

For example: "fostering an open and welcoming environment", plus all notes relating to that.

It would be better if the environment was not particularly welcoming and friendly to those people who can't produce the highest quality code. If you can't keep up, get out of the way.

Re:Linux: survived Microsoft, killed by SJWs

[frank_adrian314159]

You can't develop good code in a Safe Space.

Personally, I don't see how you develop good software in the middle of a jerk factory bro party either other than by pure luck. But that's me.

fun game out of context, totally apropos:

[Thud457]

BULLSHIT.
-- Linus Torvalds, LKML, 21/1/2018

COMPLETE AND UTTER GARBAGE.
-- Linus Torvalds, LKML, 21/1/2018

WHAT THE F*CK IS GOING ON?
-- Linus Torvalds, LKML, 21/1/2018

Re:fun game out of context, totally apropos:

[wed128]

Yeah, but he's right.

Re:fun game out of context, totally apropos:

[phantomfive]

In context, those posts are unusually tame and restrained. If you trust Linus, the Intel guy lied about what the patches were doing (or the Intel guy didn't understand what they were doing and someone had lied to him, one of those two).

Re: fun game out of context, totally apropos:

[Archangel Michael]

Ever deal with a retard that thinks himself a genius? Sometimes being offensive is the only way to blow past the idiocy efficiently.

Re: fun game out of context, totally apropos:

[Penguinisto]

This, this right the fuck here.

I've seen more than my share of soi-disant developer gods (who, well, weren't), and sometimes the only way to shut them the hell up and make them listen is to nuke their ego from orbit and use a few harsh words to drive the point home while you do it.

This method works perfectly in the Military (has for literal centuries), and adapts nicely to the dev world.

Re:fun game out of context, totally apropos:

[iMadeGhostzilla]

And this is why he's right:

"So somebody isn't telling the truth here. Somebody is pushing complete garbage for unclear reasons. Sorry for having to point that out."

He never trashes the human being, only the stupid thing they did, and people do stupid things and need feedback and correction. But the SJW culture has people focusing on their feelings and their fragile egos instead of what is being built.

Re:fun game out of context, totally apropos:

[huckamania]

Thanks for the edit, but most adults, and even some children, can do this on their own, usually while in the act of reading.

Interesting that your sig is labeling anyone who uses the term SJW a fuckwit. I almost self-edited that out. But that's okay cause being consistent is not in any way a trait of progressives.

Re: fun game out of context, totally apropos:

[Obfuscant]

and sometimes the only way to shut them the hell up and make them listen is to nuke their ego from orbit and use a few harsh words to drive the point home while you do it.

There is an old leadership principle which goes something like "praise in public, criticize in private".

If your goal is to "nuke someone's ego", then you can do that in private. When you do it in public you 1) look like a dick, and 2) scare away people who very well may have good ideas but don't care to deal with your arrogant and insulting outbursts. Volunteers have a limited amount of time, and a lot of them already understand that wasting their time participating in a system where they can expect to get their ego "nuked" isn't worth it to them.

No, the goal of someone who uses "a few harsh words" in public to criticize others isn't to deal with that one person, it's to demonstrate their own power and scare off anyone else who would dare challenge it.

This method works perfectly in the Military

That you think a software development project has the same needs and concerns as a group where people can be and are ordered to their death, and failure to obey orders can result in other people dying, is interesting. The fact that we are having this discussion shows that no, it does not adapt "nicely" to the software development world. And "nicely" may have been deliberately ironic on your part, but I doubt it.

Re: fun game out of context, totally apropos:

[HornWumpus]

James Damour. Fired for being right.

Re:fun game out of context, totally apropos:

[The Cynical Critic]

The fact that you actually take issue with things as tiny as Linus calling patches he's explained how they've been badly done "garbage" and what they do "insane" or using the expression of drinking the cool-aid when people refuse to see legitimate problems.

It's one thing to go on one of his really early rants about how he's amazed someone hasn't gotten themselves decapitated by a door and the hypersensitive language policing you're doing. If you really can't stand something as tiny as the slightly harsh language relating to a very serious set of issues then I recommend you get off the internet for a few weeks and try to put your life into perspective because if something as tiny as that irks you, then your priorities could use some re-organizing or you've got a really easy life.

Re:Wheaton's law - Don't be a Dick

[jimmifett]

Except Wheaton is one of the biggest violators of that.

It's going to be a bad thing

[MikeRT]

This is going to be what is used most of the time:

* Using welcoming and inclusive language

What that actually means in practice is that you cannot safely go through someone's code review and leave honest comments that demonstrate that the product is fundamentally bad. Welcoming and inclusive refer to a specific emotion which is to make things as warm and bubbly and positive as you can. Well, a lot of the time you can't do that.

What they want is to create for FOSS the same space they have in corporate America where HR, not line management, deals with things like personality conflicts that blow up. It's not going to make people polite, it's going to make people afraid to just be blunt with active, thin-skinned people who cannot stand to hear that their contribution is not good enough.

Re:Am I missing something?

[religionofpeas]

I don't see why somebody's gender or sexual preferences even need to come up in the first place on a mailing list discussing technical issues about the code.

Somebody Else's Problem

[nagora]

The kernel is an engineering project. As such, meritocracy is the only sane way to run it - just like building bridges or ships - if your code is good then it's in, no matter who you are or what you or anyone else identifies you as. There's simply no reason to accept someone or their work if it's sub-standard no matter how hard their lives have been (or are perceived to have been).

The issue of diversity is a social issue and has to be/needs to be solved elsewhere.