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.
In case anyone needs any more proof to the theory that red hat is an absolute cancer on FOSS


FFS like vultures
 
  • Like
Reactions: Yotsubaaa
I'm surprised no one's posted this yet: some developer pulled down (his master copy of) an open-source tool because he thought ICE was possibly using it.

This is going to have interesting implications for the open-source movement if more people start pulling stunts like this. Interesting in the "Chinese curse" sense of the term.
 
I'm surprised no one's posted this yet: some developer pulled down (his master copy of) an open-source tool because he thought ICE was possibly using it.

This is going to have interesting implications for the open-source movement if more people start pulling stunts like this. Interesting in the "Chinese curse" sense of the term.
What's this guy's problem? Apparently he quit his job with that company back in 2014 because people didn't want to use his workflow tool that he imposed on them, and so they were saying mean things to him on the internet? If he can't stand being disliked then why does he do the things that he does?
 
I'm surprised no one's posted this yet: some developer pulled down (his master copy of) an open-source tool because he thought ICE was possibly using it.

This is going to have interesting implications for the open-source movement if more people start pulling stunts like this. Interesting in the "Chinese curse" sense of the term.
lol it'd be great if ICE reuploaded it under their own github account (according to the terms) and just continued development of it.
 
lol it'd be great if ICE reuploaded it under their own github account (according to the terms) and just continued development of it.

That's more or less what happened, apparently.

From the article:
...former Chef employee Seth Vargo removed several Chef-related open source tools that he had hosted on two code repositories. They included Sugar, a tool designed to make it easier to work with Chef’s software that’s widely used by Chef customers, though it’s not clear if ICE uses it. "I have removed my code from the Chef ecosystem," Vargo wrote on the code hosting site GitHub. "I have a moral and ethical obligation to prevent my source (code) from being used for evil."

That got the company’s attention. Users who already had copies of Sugar were able to keep using it after Vargo deleted the software. Chef CTO Corey Scobie says it's hard to say how many users were affected. Vargo’s move, he says, “caused a significant impact on the global Chef community."

Chef didn’t cancel its contract with ICE. Instead, it republished Sugar.
So people who already had the Sugar software were fine, it's not even known for sure whether ICE uses the software, and his former employers promptly republished the software anyway (hurrah for open source!)
 
The sperging continues. Some more samples collected from /g/ (gloves were used)
The usual suspects pushing for a license which would define modes of use:
1569292944376.png
Some of the old free software guys might have been lefty weirdos, but at they were tolerant, open, and meritocratic.
"The paradox of tolerance" my tired ass. These parasites would rather rule over the ruins than participate in or watch (do they like watching) something successful?
1569293063311.png
"waaaaa RMS made me feel unwelcome"
I'd fucking do it again. Never thought about it before the crazies brought it up, but should be done unironically as a defensive mechanism.
1569293229326.png
 
Some of the old free software guys might have been lefty weirdos, but at they were tolerant, open, and meritocratic.
"The paradox of tolerance" my tired ass. These parasites would rather rule over the ruins than participate in or watch (do they like watching) something successful?

Fuck that phrase. The fact that people are intolerant to the point of death allergy to disagreement doesn't make something a "paradox." You being too fucking dumb to understand something isn't a "paradox."
 
The sperging continues. Some more samples collected from /g/ (gloves were used)
The usual suspects pushing for a license which would define modes of use:
View attachment 946770

The post where this license is announced is worth a look for all the craziness. It's also explicitly not a 'do no harm' license as they say, it's a license against perceived "punching down", as it only prevents harmful use against the "underprivileged".
 
I'm surprised no one's posted this yet: some developer pulled down (his master copy of) an open-source tool because he thought ICE was possibly using it.

This is going to have interesting implications for the open-source movement if more people start pulling stunts like this. Interesting in the "Chinese curse" sense of the term.
I've seen quite a few stunts like this, with the highest profile example before this being a npm developer deleting his repos over a copyright dispute and breaking things as a result.

Quite a few developers have become like pissed off internet artists in the sense that they love to DFE when they feel like it. The difference here is deleting your scribbles doesn't break software relying on some dependencies. It also has the effect of only breaking things for a day or two before people just make copies of these repos. It'll teach smarter companies and developers to make backups of these for sure in the case the developer has a meltdown online.
 
The post where this license is announced is worth a look for all the craziness. It's also explicitly not a 'do no harm' license as they say, it's a license against perceived "punching down", as it only prevents harmful use against the "underprivileged".

So if a white homeless guy used it to oppress a black millionaire, he wouldn't be allowed to do that.
 
The post where this license is announced is worth a look for all the craziness. It's also explicitly not a 'do no harm' license as they say, it's a license against perceived "punching down", as it only prevents harmful use against the "underprivileged".
Actually, Corey is misstating the terms of the license. It only says you can't use the software to violate someone's human rights according to the UN, which applies to white people too.
 
  • Agree
Reactions: Yotsubaaa
Actually, Corey is misstating the terms of the license. It only says you can't use the software to violate someone's human rights according to the UN, which applies to white people too.

You're correct as of the present time. I didn't think they actually would change it, so no archive, but thankfully they put the license up on GitHub, where you can see the related discussion.
 
  • Informative
Reactions: Marvin
I'm worried that the lesson smarter companies will take is "Start a private fork and maintain it in-house, because internet loonies are too much of a liability".
Happening already, to a degree. Balancing the risk of being accused of breaking the license vs losing the ability to build because some fuckwit deleted the source repo is a no-brainer. The most common solution is to publish a read-only clone of the source so that the license issues don't bite.
 
I also see another movement though. Technology interested people who are more conservative, and also really see the value in elegance, minimalism and coding merit, in the vein of the old school hackers of Stallmans younger days, just with a political spin on top. In stark contrast to your average nu-male/soyboy tranny "webdev-diversity-consultant-something" guy. I have the feeling this could swell those ranks. The culture wars have come to tech. I know I'm being optimistic as hell but long term, that might not be a bad thing.
When you say minimalism I sure as hell hope you're not refering to Suckless or Cat-v.
 
  • Like
Reactions: Shoggoth
I thought it might be interesting to check in on the progress of the GIMP fork now with added political correctness. And.... Oh. Oh dear.

Despite inheriting a years old code base that compiles and runs cleanly on multiple systems, they've still not even managed to ship a build with some updated branding. Meanwhile, every single file in the codebase still contains the word GIMP dozens of times and good luck fixing that even with the most impressive refactoring tools on the market.

As a bonus, they've been forced to drop Mac OS X support apparently because none of these simpletons can figure out how to type "./configure; make; make install" on an Apple system. Which is unfortunate since I guess Apple using mouth-breathers would be their core audience. Funnily enough, the GIMP project manages to ship up to date builds for OS X by some magic process known only to wizards.

You've got to wonder at the sheer hubris of these people who've never worked on the codebase before coming in and deciding that they know what's best for the project, the mainline is dead because it has the wrong name and that they're now the maintainers. There's so much hubris involved in that that I wonder if it's someone's idea of a short con. They are collecting money, albeit not a lot, for this pathetic excuse for a project.
 
I've seen quite a few stunts like this, with the highest profile example before this being a npm developer deleting his repos over a copyright dispute and breaking things as a result.

Quite a few developers have become like pissed off internet artists in the sense that they love to DFE when they feel like it. The difference here is deleting your scribbles doesn't break software relying on some dependencies. It also has the effect of only breaking things for a day or two before people just make copies of these repos. It'll teach smarter companies and developers to make backups of these for sure in the case the developer has a meltdown online.
If you rely on automatic versioning for your libs and only have one source repo that you don't control, you deserve everything that happens to you.

Here's some food for thought: the majority of the world's software running this very second would fail to run if you removed every line of code ever written by a dangerhair out of existence, so respect your own shit, and make sure your dependencies are immutable.
 
If you rely on automatic versioning for your libs and only have one source repo that you don't control, you deserve everything that happens to you.

Here's some food for thought: the majority of the world's software running this very second would fail to run if you removed every line of code ever written by a dangerhair out of existence, so respect your own shit, and make sure your dependencies are immutable.
... are you sure anyone would even notice if that happened?
 
Back