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

[Markass the Worst]

Looks like there's been some fuckery going on with commits to the Linux kernel tree concerning the 6.15 release.

https://www.phoronix.com/news/Linux-6.16-Git-Gone-Wrong
https://archive.is/bZnMn

I don't buy that it was just a buggy script. Surely if it's fucking up history like that, wouldn't you notice it and fix it? Or if you don't notice it, then you're not actively reviewing the tree and that is its own security risk.

 

[Pluciferous]

I don't buy that it was just a buggy script. Surely if it's fucking up history like that, wouldn't you notice it and fix it? Or if you don't notice it, then you're not actively reviewing the tree and that is its own security risk.

It’s a shame that Kees is now going to be known as the guy who doesn’t review his git branches AT ALL before asking Linus to pull them.

He should be known as the guy who plagiarizes and/or shittily reimplements other people’s security code.

 

[teriyakiburns]

https://www.phoronix.com/news/Linux-6.16-Git-Gone-Wrong

Bunch of pussies in the comments crying that Linus was "insulting" and disrespectful to the fuckup. Some things are eternal.

 

[Sargon's wife's son]

It’s a shame that Kees is now going to be known as the guy who doesn’t review his git branches AT ALL before asking Linus to pull them.

Terry was 100 percent worried about lying as Torba.

 

[BigGuyOS 6 : Jovial Janny]

An example of this is involving interacting with APIs for vendor products, Copilot literally just makes up REST endpoints that sound like what you want since it has very shallow knowledge. Given the Copilot tribe doesn't understand how this magic box works, they assume it can work with anything and get led around for sometimes days at a time until they finally come begging for help.

What are you doing using Copilot in the year 2025? This isn't 2023, you should be using Cursor or Void or something else with MCP and linting and agentfiles. Using base VScode or just copy and pasting is going to turn out horrendously.

 

[CrunkLord420]

Qwen 2.5 Coder 32B is shit and I'm not paying a penny for corpo AI.

 

[George Lucas]

Some drama is brewing in the PCEmu space:
https://kiwifarms.net/threads/mooch...darius-melissa-goad-mooch.94504/post-21622494

 

[Mikoyan]

Bunch of pussies in the comments crying that Linus was "insulting" and disrespectful to the fuckup. Some things are eternal.

I was pretty amused by the comments last night. The one guy claiming he never got such treatment while working on the kernel and making huge contributions getting replied to with "It was a kernel Linus wasn't involved with or you're a liar" sent me.

 

[analrapist]

This is, IMO, where the topic ought to be discussed, as Xorg is multiplatform, but figured it was worth a mention here for those of you who don't do Linux.

>try to find the link for the repository
>find it
>404'd
>check the profile of the dev
>"Blocked user" (meaning banned)
FreeDesktop trannies never fail to entertain

(Source) (Archive)

A [somewhat based] fellow (Enrico Weigelt AKA metux) forks X, fixes some old issues, adds a new security layer, and for his efforts, Freedesktop banishes him. Real Mean Girls vibes. (But don't worry, he just moved over to GitHub! https://github.com/X11Libre/xserver )

 

[AmpleApricots]

forks X,

I knew it'd eventually happen, but still - finally. There's been so many patches (e.g. tearfree for modesetting drivers) that have been purposefully withheld from X releases to boost wayland the cripple, it's ridiculous. A well maintained fork could give hope to more sane windowing toolkits and maybe deshittify the linux GUI landscape somewhat. We will see what happens.

Also lol at banning him. Totally not mad you guys.

 

[Combustion Engine]

and for his efforts, Freedesktop banishes him

Why are those "people" like this? RedHat has done irreparable damage allowing those freaks to spread all over the place. Every single project they touch turns into cancer.

Spoiler: Closed merge requests

(archive link by someone yesterday)

 

[306h4Ge5eJUJ]

Why are those "people" like this? RedHat has done irreparable damage allowing those freaks to spread all over the place. Every single project they touch turns into cancer.
View attachment 7464854

Spoiler: Closed merge requests

View attachment 7464853
(archive link by someone yesterday)

What in the fuck is that merge request list? Did this guy just spam a merge request for every minor cleanup fix? No fucking wonder he got banned, imagine having to deal with this.

 

[volatile puar]

What in the fuck is that merge request list? Did this guy just spam a merge request for every minor cleanup fix? No fucking wonder he got banned, imagine having to deal with this.

Look closer, these aren't all consecutive numbers, and go back quite far, Herbst just got really mad and closed all of his historical merge requests.

 

[But Nuster]

This is, IMO, where the topic ought to be discussed, as Xorg is multiplatform, but figured it was worth a mention here for those of you who don't do Linux.



A [somewhat based] fellow (Enrico Weigelt AKA metux) forks X, fixes some old issues, adds a new security layer, and for his efforts, Freedesktop banishes him. Real Mean Girls vibes. (But don't worry, he just moved over to GitHub! https://github.com/X11Libre/xserver )

This (a) got a chuckle out of me:

 

[Combustion Engine]

Did this guy just spam a merge request for every minor cleanup fix?

You can read his stance on commits in this now-closed CONTRIBUTING.md merge request:

each commit should solve one particular problem and be self-consistent, ie. complete in itself and not break anything else

I think it's reasonable, or rather: X11 has been declared dead in maintenance mode years ago and they've always been very protective of anything that doesn't reflect that level of activity and contribution, most of which those aren't. The classic "patches are welcome" -> "No, I won't merge this" pipeline, except here they are discouraged unless it's for safety, and pushing contributors to move to Wayland instead. I don't know if this person is the right one for the job, but someone needs to take all those projects away from them, one by one.

It seems like he was reckless with changes and broke some stuff before, just a few months (archive) ago:

In the same thread there's some discussion about the usefulness of his changes, whether they have introduced more bugs, and the usual reminder Xorg is dead anyway:

Spoiler: comments

 

[306h4Ge5eJUJ]

You can read his stance on commits in this now-closed CONTRIBUTING.md merge request:

These aren't commits, they're merge requests; the commits are even more fine-grained. Fair enough though, even if I think this is excessive. Pointing out one typo isn't very helpful, but pointing out all typos is, and all that.

The linked issue thread in your cap (L, A) is worth quoting here by the way:

My thoughts:

- We are breaking module ABI far too often for things like small logging cleanups. Please stop making changes that break ABI -- it is massively disruptive, and the small amounts of "code cleanups" we get as a result are not worth the pain.
- It is irresponsible to mark an ABI break with "(trivial)" in the commit message, and makes me not trust any patch @metux writes going forward.

Honestly, I would strongly recommend just not merging anything @metux does from now on. I do not feel that their presence here has been a net positive -- I have seen zero actual bugs solved by any of their code changes. What I have seen is build breakage, ABI breakage, and ecosystem churn from moving code around and deleting code.
Xorg could use some actual maintenance, but that means fixing actual bugs and solving real problems.

Sounds like this isn't just Red Hat troons being Red Hat troons.

 

[Kendall Motor Oil]

The linked issue thread in your cap (L, A) is worth quoting here by the way:

Xorg could use some actual maintenance, but that means fixing actual bugs and solving real problems.

The issue with this reasoning is that it's never the right bugs or solving the right problems to the maintainers and then project stays dead which seems to be the goal.


Wayland is just as bad about this and using Wayland outside of office lady light desktop use is fraught with bugs and missing features(many of which are purposely missing because of "security"). That lack of stability is okay but X getting decades old features isn't.

It's as if the Linux desktop experience has regressed but the maintainers around the two projects have layers of justification and hand waving for it.

 

[Kola]

 

[Frederica Bernkastel]

Hyprland went through the same shit with wayland because its the same fucking people. ICE any project with anyone in Herbst's orbit, and you've just saved it from hostile takeover by trannies and nigger commies

 

[jeff7989]

Apparently r*ddit jannies are sweeping any mention of Xlibre. I'm really curious whether anything will come out of this fork since I can't be bothered with Wayland on my desktop.