budoslavic
International Playboy
     
Posts: 4,602
Joined: Aug 2015
Reputation: 25
|
RE: Linux has been infiltrated by SJWs
As a long time Linux user - since early 2000's - openSUSE, Debian - just been catching up on the latest Linux gossip regarding the CoC bullshit.
Vox Day's been following this and came out with a couple of insightful posts.
Code of Conduct, working as designed:
Quote:Mark [email protected]
I tweeted that Linux’s new code of conduct would be abused to witch hunt devs.
Right on cue, 3 or 5 devs tried to use my opposition of the code of conduct to try to accuse me of violating it.
All the while using behavior that was against the code of conduct.
I rest my case.
Mark [email protected]
You can add one @ZDNet reporter to the list of witch hunters. Came after me just today.
[email protected]
I dunno man, I think having codes of conduct to allow mediocre programmers to police good programmers is precisely the way to move the industry into the direction of a giant bureaucracy. What could go wrong with that?
Corey @corey5135
I've been called out for "aggressive behavior" because I stated that I had already evaluated a suggested implementation & decided it was the wrong way to go (different project). They were putting me in my place for daring to disagree. Last patch they got from me.
Tucker [email protected]ckerGoodrich
Yeah, there's a lot Vox Day says that I don't like, but I think his analysis of codes of conduct is spot on.
"...the Code of Conduct is working as designed when it chases off the productive members of the project"
[url=]The most pyrrhic victory in history[/url]
Quote:Coraline Ada [email protected]
40,000 open source projects, including Linux, Rails, Golang, and everything OSS produced by Google, Microsoft, and Apple have adopted my code of conduct. You can make me have a bad day, but it doesn’t change the fact that we have won and you have lost.
Wanna bet? I just wish xir could convince Marvel and DC and IDW and Dark Horse to adopt xir's code of conduct too. The more completely an organization converges, the faster they will collapse.
This isn't a defeat for us, this is a vast horizon of opportunity being handed to us on a platter.
Killswitch the Linux Code of Conduct
Quote:Don't wait to be ejected from the Linux Kernel Community, contributors. Throw the killswitch, rescind your license grants NOW, and force the SJWs who are trying to converge your project to permanently withdraw the cancerous Code of Conduct.
Date Thu, 20 Sep 2018 09:28:14 +0000
From [email protected] ...
Subject Re: A Plea to Unfuck our Codes of Conduct
Regarding those who are ejected from the Linux Kernel Community after this CoC:
Contributors can, at any time, rescind the license grant regarding their property via written notice to those whom they are rescinding the grant from (regarding their property (code)) .
The GPL version 2 lacks a no-rescission clause (the GPL version 3 has such a clause: to attempt furnish defendants with an estoppel defense, the Linux Kernel is licensed under version 2, however, as are the past contributions).
When the defendants ignore the rescission and continue using the plaintiff's code, the plaintiff can sue under the copyright statute.
Banned contributors _should_ do this (note: plaintiff is to register their copyright prior to filing suit, the copyright does not have to be registered at the time of the violation however)
Additionally when said banned contributors joined the Linux team, they were under the impression that it was a meritocracy: in-fact this belief was stated or ratified by those within the governing body regarding Linux when the contributors began their work (whatever that body was at that time, it could have been simply Linus, or Linus and a few associates).
The remuneration for the work was implied to be, or perhaps stated, to be fame as-well as a potential increase in the contributors stature, in addition to membership in the Linux Kernel club or association, or whatever it is that the Linux Kernel Community actually is (which a court may determine... it is something, suffice to say).
Thusly for work, consideration was promised by (Linus? Others? There are years of mailing list archives with which to determine).
And now that consideration has been clawed-back and the contributors image has been tarnished.
Thus the worker did work, however the other side of the implied, or perhaps written (email memorandums), understanding has been violated (once the contributor has been banned under the new non-meritocratic "CoC").
Damages could be recovered under: breach of contract, quazi-contract, libel, false-light. (services rendered for the contractual claims, future lost income for the libel claims). In addition to copyright claims. (statutory damages, profits)
For greatest effect, all rescission should be done at once in a bloc. (With other banned contributors).
Contributors: You were promised something, you laboured for that promise, and now the promise has become a lie. You have remedies available to you now, as-well as in the close future .
Additionally, regarding those who promoted the Code of Conduct to be used against the linux kernel contributors, knowing full well the effect it would have and desiring those effects; recovery for the ejected contributors via a tortious interference claim may be possible.
Most of the legal babble is the usual ignorant nonsense, but the license rescinding threat is both real and significant. And in this case, because the Code of Conduct has already been imposed, all the non-SJW contributors would be advised to act now and force a complete retreat by those who are successfully attempting to converge the project. We know how this always turns out.
These losers did the same in the comic industry and the gaming industry and now they are trying it in the open source community.
Fortunately, some contributors are seriously considering withdrawing their code, although they need to simply go ahead and do it now. Dire threats and warnings never, ever work with these lunatics. They always - and usually correctly - assume that you're going to back down.
My company is already considering the full withdrawal of all contributed code to the kernel project and related embedded kernel projects. You literally can’t run embedded Linux on industrial controls or handheld scanners without this code.
Assuming the Code of Conduct can be removed, an anti-SJW inquisition would be the correct next step, followed by permanent exclusion and ideological policing. Because, as you have been openly warned, the Code of Conduct is an SJW weapon and it is only a prelude of ruthless enforcement and even worse things to come.
Coraline Ada Ehmke @CoralineAda
Sep 20
Adopting a code of conduct is STEP ONE and does nothing to address systemic issues. The hard work is in designing an enforcement process, answering some hard questions about accountability and safety, and following through.
Coraline Ada [email protected]
Sep 20
Looking for community financial support. Having a CoC is a first step, but fair enforcement is what makes all the difference. I’m working on an open source SaaS app to make this easier.
Fortunately, some in the Linux community are clearly aware of the SJW threat to their open source projects, their technology, and their careers.
With the recent Social Justice capture of the Linux kernel, many in the open source world may find this guide from Vox Day to be useful. I present it here as a public service; you can find the original PDF here. If you are interested in how to resist the introduction of the Contributor Convenant and other Social Justice derived Codes of Conduct, you may wish to watch this presentation or see the slides for it.
Some readers will recall that I specifically warned about Cancer Coraline and xir Codes of Conduct in SJWs Always Double Down.
The two primary weapons utilized by corporate SJWs to marginalize opponents of convergence are the now-ubiquitous Code of Conduct and the Community Committee. While codes of conduct sound sensible enough in theory, in practice they are very vaguely worded documents that serve much the same purpose for the Community Committees responsible for enforcing them that petty traffic laws do for the police. Namely, they permit the Community Committee, which may be named the Steering Committee or even the Code of Conduct Committee, to charge anyone who is insufficiently enthusiastic about the organization’s new social justice priorities with Code of Conduct violations. Since both looking at another individual and not looking at another individual can be deemed violations of the vast majority of these codes of conduct, you can probably see how they can be weaponized in order to freeze, isolate, and eliminate opponents.
In practice, codes of conduct are also used to smoke out and identify opposition to the SJWs, as the initial skeptics who are the most able to understand the danger posed by a proposed code of conduct will usually tend to serve as the nexus of the resistance against it.
(This post was last modified: 10-18-2018 10:15 PM by budoslavic.)
|
|