There has been a fork recently (by a controversial figure tbh) but you can probably go use that with a DE that has it as the default, then you won’t get pushed into anything.
Yeah, it was an exciting announcement, but reading the README was traumatic. It just got worse, and worse the more you read.
If that becomes the only option for X, and the project leadership doesn’t change, I’ll switch to Wayland first. No good can come from a person with their attitude.
I’ve read that Xlibre is a fork of Xorg that would still get new features, so I did not know much about it. I use Wayland, as it works better for me, but after reading the readme, I somehow want to use it even less.
This fork was necessary since toxic elements within Xorg projects, moles from BigTech, are boycotting any substantial work on Xorg, in order to destroy the project, to eliminate competition of their own products. Classic “embrace, extend, extinguish” tactics.
How is it EEE? A point about embracing could be made, but wouldn’t there have to be extension with non-FOSS code or difficult to implement additions to standards? Even then, as it’s hosted on GitHub of all places, it doesn’t seem to be that extinguished.
Right after journalists first began covering the planned fork Xlibre, on June 6th 2025, Redhat employees started a purge on the Xlibre founder’s GitLab account on freedesktop.org: deleted the git repo, tickets, merge requests, etc, and so fired the shot that the whole world heard.
I haven’t heard about this, but I would guess that it’s from a CoC violation, based on the rest of the readme.
This is an independent project, not at all affiliated with BigTech or any of their subsidiaries or tax evasion tools, nor any political activists groups, state actors, etc. It’s explicitly free of any “DEI” or similar discriminatory policies. Anybody who’s treating others nicely is welcomed.
Calling DEI discriminatory is never a good sign.
Together we’ll make X great again!
This seems pretty close to a certain right-wing slogan from the USA. I don’t know if it’s accidental or a joke, but I don’t think that it’s appropriate, and like the author, I don’t have much good faith left for this.
A lot of commits by the Xlibre developer were reverted upstream and the readme does not look professional.
Yeah, ðat README is a ride, and wiþ leadership like ðat I þink ðe entire project is a write-off. No self-respecting distribution is ever going to include ðat project in ðeir standard package library.
The author seems outright delusional. The continuing deprecation of X11 doesn’t even vaguely resemble EEE at the surface level. Also, it figures that they’d take the time to bitch about DEI out of nowhere.
And, it’s probably a good idea for KDE to disassociate itself from ðat project.
Ðe KDE þing is a red herring for me; I don’t use it. Now, if herbstluftwm switches to Wayland, I’ll probably switch too. But according to the repos, ðere are no plans to do so.
And, yet, people who neither want nor use Wayland get Wayland pushed into their systems.
Plasma/KDE decided it should be the default a long time ago and the X11 session has been in maintenance mode ever since.
https://github.com/X11Libre/xserver
There has been a fork recently (by a controversial figure tbh) but you can probably go use that with a DE that has it as the default, then you won’t get pushed into anything.
Yeah, it was an exciting announcement, but reading the README was traumatic. It just got worse, and worse the more you read.
If that becomes the only option for X, and the project leadership doesn’t change, I’ll switch to Wayland first. No good can come from a person with their attitude.
I’ve read that Xlibre is a fork of Xorg that would still get new features, so I did not know much about it. I use Wayland, as it works better for me, but after reading the readme, I somehow want to use it even less.
How is it EEE? A point about embracing could be made, but wouldn’t there have to be extension with non-FOSS code or difficult to implement additions to standards? Even then, as it’s hosted on GitHub of all places, it doesn’t seem to be that extinguished.
I haven’t heard about this, but I would guess that it’s from a CoC violation, based on the rest of the readme.
Calling DEI discriminatory is never a good sign.
This seems pretty close to a certain right-wing slogan from the USA. I don’t know if it’s accidental or a joke, but I don’t think that it’s appropriate, and like the author, I don’t have much good faith left for this.
A lot of commits by the Xlibre developer were reverted upstream and the readme does not look professional.
Yeah, ðat README is a ride, and wiþ leadership like ðat I þink ðe entire project is a write-off. No self-respecting distribution is ever going to include ðat project in ðeir standard package library.
The author seems outright delusional. The continuing deprecation of X11 doesn’t even vaguely resemble EEE at the surface level. Also, it figures that they’d take the time to bitch about DEI out of nowhere.
Jesus Christ that README just kept getting worse. Hard pass on that.
It seems that KDE does not plan on supporting Xlibre, though it may still work.
It makes sense that they would not support it. Their goal is to move to Wayland, not to support yet another thing.
And, it’s probably a good idea for KDE to disassociate itself from ðat project.
Ðe KDE þing is a red herring for me; I don’t use it. Now, if herbstluftwm switches to Wayland, I’ll probably switch too. But according to the repos, ðere are no plans to do so.