Diseased Open Source Software Community - it's about ethics in Code of Conducts

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
IT KEEPS HAPPENING https://www.phoronix.com/scan.php?page=news_item&px=LLVM-Rafael-Espindola (https://archive.fo/YnvcLv)
One Of LLVM's Top Contributors Quits Development Over CoC, Outreach Program
Written by Michael Larabel in LLVM on 2 May 2018 at 04:30 PM EDT. 34 Comments
llvm.jpg

Rafael Avila de Espindola is the fifth most active contributor to LLVM with more than 4,300 commits since 2006, but now he has decided to part ways with the project.

Rafael posted a rather lengthy mailing list message to fellow LLVM developers today entitled I am leaving llvm.

He says the reason for abandoning LLVM development after 12 years is due to changes in the community. In particular, the "social injustice" brought on the organization's new LLVM Code of Conduct and its decision to participate in this year's Outreachy program to encourage women and other minority groups to get involved with free software development.

In part he wrote:
The reason for me leaving are the changes in the community. The current license change discussions unfortunately bring to memory the fsf politics when I was working on gcc. That would still not be sufficient reason to leave. As with the code, llvm will still have the best license and if the only community change was the handling of the license change I would probably keep going.

The community change I cannot take is how the social injustice movement has permeated it. When I joined llvm no one asked or cared about my religion or political view. We all seemed committed to just writing a good compiler framework.
Espindola was one of the most prolific LLVM contributors. I ran some Git statistics today on the code-base to look at his contributions.

commits_by_author.png



Of the 900+ authors to LLVM, Rafael was the fifth most contributor to LLVM by commit count with 4,344 commits (2.65% of all commits0 and in the process added 157,679 lines of code. He had been contributing since 14 May 2006 and was many times the most active LLVM contributor in a given month while working for the likes of Google and Mozilla. In fact, for 2013 through 2015 he was the most active author each year. His contributions will certainly be missed.

The CoC: https://llvm.org/docs/CodeOfConduct.html (https://archive.fo/XnF2y)
LLVM Community Code of Conduct
Note

This document is currently a DRAFT document while it is being discussed by the community.

The LLVM community has always worked to be a welcoming and respectful community, and we want to ensure that doesn’t change as we grow and evolve. To that end, we have a few ground rules that we ask people to adhere to:

This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to communicate and participate in the community.

This code of conduct applies to all spaces managed by the LLVM project or The LLVM Foundation. This includes IRC channels, mailing lists, bug trackers, LLVM events such as the developer meetings and socials, and any other forums created by the project that the community uses for communication. It applies to all of your communication and conduct in these spaces, including emails, chats, things you say, slides, videos, posters, signs, or even t-shirts you display in these spaces. In addition, violations of this code outside these spaces may, in rare cases, affect a person’s ability to participate within them, when the conduct amounts to an egregious violation of this code.

If you believe someone is violating the code of conduct, we ask that you report it by emailing conduct@llvm.org. For more details please see our Reporting Guide.

  • Be friendly and patient.
  • Be welcoming. We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion or lack thereof, and mental and physical ability.
  • Be considerate. Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account. Remember that we’re a world-wide community, so you might not be communicating in someone else’s primary language.
  • Be respectful. Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the LLVM community should be respectful when dealing with other members as well as with people outside the LLVM community.
  • Be careful in the words that you choose and be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behavior aren’t acceptable. This includes, but is not limited to:
    • Violent threats or language directed against another person.
    • Discriminatory jokes and language.
    • Posting sexually explicit or violent material.
    • Posting (or threatening to post) other people’s personally identifying information (“doxing”).
    • Personal insults, especially those using racist or sexist terms.
    • Unwelcome sexual attention.
    • Advocating for, or encouraging, any of the above behavior.
    In general, if someone asks you to stop, then stop. Persisting in such behavior after being asked to stop is considered harassment.
  • When we disagree, try to understand why. Disagreements, both social and technical, happen all the time and LLVM is no exception. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of LLVM comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.
Rafael's departing message: https://lists.llvm.org/pipermail/llvm-dev/2018-May/122922.html (https://archive.fo/SCgWM)
[llvm-dev] I am leaving llvm
Rafael Avila de Espindola via llvm-dev llvm-dev at lists.llvm.org
Wed May 2 09:37:41 PDT 2018
Summary:

I am leaving llvm effectively immediately. I am sorry for any
inconvenience this may cause.

Practicalities:

I can unsubscribe myself from the email lists and I disabled email
notification on bugzilla and phabricator. Could someone please disable
my account on phabricator and delete my svn access? Thanks.

The long story:

I first became aware of llvm during a compiler course at university. I
wanted to write a toy scheme frontend to a real compiler. To my shame
I missed that llvm had a mem2reg pass and selected gcc to avoid having
to compute ssa form myself.

After contributing a few patches to gcc it was clear that the frontend
interface needed some cleanup. At the time llvm was being considered
as a potential new gcc architecture and the idea of a well defined IR
with a textual representation was a revolution.

On my first job (indt) we were using arm cpus and I was able to sell
the idea of starting an llvm backend for arm. My first commit was on
May 14, 2006. I am incredibly grateful to both indt and the llvm
developers for trusting and helping such an inexperienced and unknown
developer with such a large task.

It is only in May 2007 in the dev meeting that I got to meet the other
developers in person. It was an incredibly fun event and people were
as friendly in person as on the list.

In the next few years I was working at google. First as an sre and
then a compiler developer on gcc. During that time I kept llvm as my
20% project as much as possible. Working on it was always a refreshing
experience. It was far easier to change and far less political than gcc
at the time.

My opportunity to be back full time on llvm came with portable native
client (pnacl). They needed to be able to emit elf objects from llvm ir
and so I went to work on elf support for mc.

Unfortunately another job change (mozilla) made llvm a side project
again after that. I still managed to contribute to llvm/clang as I
helped mozilla transition away from gcc 4.2 on OS X.

It is only about 5 years ago that I started working on llvm full time
again. The big item this time was elf support in lld. I was really
excited when Rui posted a new design for a coff linker and did my best
to find a corresponding design for elf.

Unfortunately the last few years haven't been the same. On the
technical side llvm now feels far bigger and slower to change. There
are many incomplete transitions. That, by itself, would not be
sufficient reason to leave. llvm still seems better than the
competition and lld itself is still awesome.

The reason for me leaving are the changes in the community. The
current license change discussions unfortunately bring to memory the
fsf politics when I was working on gcc. That would still not be
sufficient reason to leave. As with the code, llvm will still have the
best license and if the only community change was the handling of the
license change I would probably keep going.

The community change I cannot take is how the social injustice
movement has permeated it. When I joined llvm no one asked or cared
about my religion or political view. We all seemed committed to just
writing a good compiler framework.

Somewhat recently a code of conduct was adopted. It says that the
community tries to welcome people of all "political belief". Except
those whose political belief mean that they don't agree with the code
of conduct. Since agreement is required to take part in the
conferences, I am no longer able to attend.

The last drop was llvm associating itself with an organization that
openly discriminates based on sex and ancestry (1,2). This goes
directly against my ethical views and I think I must leave the project
to not be associated with this.

So long, and thanks for all the bugs,
Rafael
[1] http://lists.llvm.org/pipermail/llvm-dev/2018-February/121161.html
[2] https://www.outreachy.org/apply/eligibility/

https://lists.llvm.org/pipermail/llvm-dev/2018-May/122926.html (https://archive.fo/2Mg0j)
upload_2018-5-2_18-52-16.png

https://lists.llvm.org/pipermail/llvm-dev/2018-May/122929.html (https://archive.fo/LxNmw)
upload_2018-5-2_18-53-6.png


https://lists.llvm.org/pipermail/llvm-dev/2018-May/122928.html (https://archive.fo/3zLCF)
I feel exactly the same way about the CoC. The whole CoC idea is just a
bullshit that brings discord in open source projects.

I haven't seen a project that adopted a CoC and had no members leaved after
that.

https://lists.llvm.org/pipermail/llvm-dev/2018-May/122934.html (https://archive.fo/UVKsL)
upload_2018-5-2_18-54-17.png


4/g/ https://boards.4chan.org/g/thread/65775717 (https://archive.fo/cXIIU)
Phoronix forum: https://www.phoronix.com/forums/for...s-quits-development-over-coc-outreach-program
 
So looking at this CoC:pickle:, it's not too bad. Most of it just consists of just not being a screeching harpy at your co-contributors.

There's a few things that are "stupid but I can stomach it" stuff, like the diversity stuff will probably be used to change some pronouns from "he" to "they" or whatever. That's dumb, but not worth making an issue of.

No, here's the serious fuckup, and if I wasn't reading carefully, I would've missed it:
In addition, violations of this code outside these spaces may, in rare cases, affect a person’s ability to participate within them, when the conduct amounts to an egregious violation of this code.
See, they always slip a little escape clause into it. It's like how VPS agreements always rattle off the standard "don't break the law, blah blah blah" and then finally "we reserve the right to terminate your service for any reason".

Bingo, there you go.

A clause like that is what permits them to convene the Grand Council of the Dangerhairs to boot you from the project (while keeping all your contributions, of course) and out you to the world (and future employers) as an alleged oppressor of, idk, minorities or some shit.
Ellen K. Pao suggesting CEOs of tech companies should have sex with their incel employees https://twitter.com/ekp/status/991817194987114496 (https://archive.fo/LaBFH)
View attachment 440902
Heh, no, incels usually don't have jobs, and rarely good ones.
 
So there was some drama about the glibc project over a fucking joke. The joke was in the manual page for the abort() function and poked fun at the US Government's stance on abortion. A developer submitted a patch to remove it, thinking it'd go about as well as gender neutral pronoun pushes on most projects. What he didn't know is that he was running afoul of the one and only Richard Stallman, who basically reminded everyone that he was in charge and that you had to play by his rules, which meant "don't remove jokes I make".

This resulted in both discussion on the usual places, and nutty "girl programmer" and numale salt.

upload_2018-5-9_1-43-50.png

upload_2018-5-9_1-44-18.png

upload_2018-5-9_1-44-30.png

https://archive.fo/d18Uz
 
So there was some drama about the glibc project over a fucking joke. The joke was in the manual page for the abort() function and poked fun at the US Government's stance on abortion. A developer submitted a patch to remove it, thinking it'd go about as well as gender neutral pronoun pushes on most projects. What he didn't know is that he was running afoul of the one and only Richard Stallman, who basically reminded everyone that he was in charge and that you had to play by his rules, which meant "don't remove jokes I make".

This resulted in both discussion on the usual places, and nutty "girl programmer" and numale salt.

View attachment 445155
View attachment 445156
View attachment 445157
https://archive.fo/d18Uz
Imagine taking something RMS said really seriously and try getting offended by it, you'd have to be completely unfamiliar with rms. We all know how autistic RMS is and I can't help but laugh at the idea of journos running stories against him calling him a misogynist.
 
Imagine taking something RMS said really seriously and try getting offended by it, you'd have to be completely unfamiliar with rms. We all know how autistic RMS is and I can't help but laugh at the idea of journos running stories against him calling him a misogynist.
Some troons already hate RMS too after the libreboot saga, as RMS kept reminding Leah that his friend wasn't fired for being a tranny.
 
So there was some drama about the glibc project over a fucking joke. The joke was in the manual page for the abort() function and poked fun at the US Government's stance on abortion. A developer submitted a patch to remove it, thinking it'd go about as well as gender neutral pronoun pushes on most projects. What he didn't know is that he was running afoul of the one and only Richard Stallman, who basically reminded everyone that he was in charge and that you had to play by his rules, which meant "don't remove jokes I make".

This resulted in both discussion on the usual places, and nutty "girl programmer" and numale salt.

View attachment 445155
View attachment 445156
View attachment 445157
https://archive.fo/d18Uz

I dug around the mailing list, and it's full of numales who don't realise how much of GNU was literally Stallman seeing a need and working to fill it. It's his project.

He makes a better joke being snarky about the criticism https://sourceware.org/ml/libc-alpha/2018-05/msg00017.html
Someone doesn't like Stallman being in charge https://sourceware.org/ml/libc-alpha/2018-05/msg00414.html
Stallman has to explain that it's possible for a male to understand a woman's point of view https://sourceware.org/ml/libc-alpha/2018-05/msg00376.html (referencing this message https://sourceware.org/ml/libc-alpha/2018-05/msg00220.html, where Stallman claims to have read articles about women)
Redhat fag doesn't understand that Stallman is an auteur, references "the community" like the scum he is https://sourceware.org/ml/libc-alpha/2018-05/msg00155.html
Some nobody writes an essay in response to Stallman stating that it's possible to understand the joke without the specific contexthttps://sourceware.org/ml/libc-alpha/2018-05/msg00292.html (personally, I'm not a burger and I found it pretty clear)
Apparently acknowledging the fact that people kill babies at all is a political stance https://sourceware.org/ml/libc-alpha/2018-05/msg00046.html
Stallman has to explain that he is a person who finds some things funny, and he passed that quality to GNU is Not Unix. https://sourceware.org/ml/libc-alpha/2018-05/msg00015.html


And it turns out the joke only shows up in PDF versions of the manual, probably only ever seen by Stallman.
 
So there was some drama about the glibc project over a fucking joke. The joke was in the manual page for the abort() function and poked fun at the US Government's stance on abortion. A developer submitted a patch to remove it, thinking it'd go about as well as gender neutral pronoun pushes on most projects. What he didn't know is that he was running afoul of the one and only Richard Stallman, who basically reminded everyone that he was in charge and that you had to play by his rules, which meant "don't remove jokes I make".

This resulted in both discussion on the usual places, and nutty "girl programmer" and numale salt.

View attachment 445155
View attachment 445156
View attachment 445157
https://archive.fo/d18Uz

Beard.PNG


Please don't invite Uncle Hands to the next Christmas party; Timmy has never been the same after the last year's.
 
Motherboard (of VICE) ironically put out a bad python2 script to help archive websites. Ironically because VICE was one of the first places I noticed actively block archive.is connections, and their writers often derided it on twitter. https://github.com/motherboardgithub/mass_archive/blob/master/mass_archive.py

Not to mention it's a bad script that doesn't work in python3, has no real exception handling. I use the same archiveis lib they use, but from the latest git and with my own improvements. It's fine I guess, but it comes off as version 0.001 babbys first python script that they decided to actually publish and write an article about.
 
  • Informative
  • Agree
Reactions: Marvin and awoo
Python 3 support is not difficult (there are tools like 2to3). I just don't like how they require you to change a string in the source for an API key -that comes off as very unprofessional.
 
Python 3 support is not difficult (there are tools like 2to3). I just don't like how they require you to change a string in the source for an API key -that comes off as very unprofessional.
Forgot to mention it also lacks a license, which GitHub is pretty aggressive about you pushing right away when you create a new repo. Technically making it all rights reserved.
 
I posted this in articles & happenings because its worth of its own thread, but Chad Richard Stallman just fought with a bunch of nerds over gender identity and trigger warnings to maintain an abortion joke in some documentation that he wrote ages ago because he maintained that it was still funny:
https://kiwifarms.net/threads/chad-...-ignoring-triggers-and-gender-identity.42970/

The joke:
upload_2018-5-12_12-48-49-png.447656


Based Chad Richard Stallman's reaction affirming that the joke is funny:
upload_2018-5-12_12-49-58-png.447658



https://www.theregister.co.uk/2018/05/09/gnu_glic_abort_stallman/
 
I personally think Stallman is overstepping his boundaries here. These kind of waste of time issues would not be an issue with someone calmer and pragmatic like Greg Kroah-Hartman.
 
I personally think Stallman is overstepping his boundaries here. These kind of waste of time issues would not be an issue with someone calmer and pragmatic like Greg Kroah-Hartman.

I think if no one is able to enforce definite decisions then you run the risk of severe autism infections.

Bitcoin had a similar issue with "poisonous people" in the past: https://bitcointalk.org/index.php?topic=62037.0
Namely some guy called Luke Jr, although a prolific contributor, caused numerous slapfights with stupid shit.

A project probably benefits from people having differing opinions and you want people to have the freedom to contribute "good" ideas/work but you're also probably better off having someone who has the power of enforcing a final say or someone who guides the project. Bitcoin is the perfect example of this not happening because everything is tied to money so autism is heavily involved and because no one can agree on fucking anything they do a hardfork every 2 days.
 
Back