A long time has passed since the last major release of the X.Org X11 Xserver. Even bugfix releases have become rare. Therefore, this Change proposes replacing the nearly unmaintained upstream with a maintained fork, the X11Libre XServer.
The upstream maintainer of X11Libre had been the most active remaining contributor to the X.Org X11 Xserver before the fork. The Change Owner is well aware of the controversies around the X11Libre upstream maintainer (FreeDesktop.org CoC violations, controversial political views, conspiracy theories, rants against Red Hat), but believes that the benefit of shipping maintained software outweighs the potential annoyances when having to deal with upstream.
There is no intent to ever replace the Xwayland implementation, only the standalone Xserver and its subpackages (Xnest, Xvfb, Xephyr), and possibly the driver packages (xorg-x11-drv-*).
There was a thread about this a few days ago. That guy who did the fork is nuts. A WW2 Nazi apologist.
And as I said then, Xorg is already Libre.
Without some facts to back it up I question phrasing like “most active remaining contributor”. Or “actively maintained” vs what? Just “maintained”? I want to see the stats before I believe this is more than steering the narrative.
This person picked a good time to throw a fit and draw a lot of attention to himself.
People say we should leave politics out of it and concentrate on the software (meritocracy) but I question that. I mean, the way this is going you just can’t leave that guy’s motivations out of the equation.
You can imagine the way the discourse about this proposal is going, but I randomly picked up one comment I wanted to share excerpts of anyhow:
Accepting something this premature into the project would cause stability issues. Even if he was a computing wizard one dev with a day job and conspiracy forms to keep up with is not able to do the maintenance that Xorg needs.
This has bcachefs vibes. I don’t think anyone questions Overstreet’s C competency, but his habit of pushing last minute changes without sufficient testing and ignoring the process to try to sneak in changes outside approved windows displays a similarly cavalier mindset.
Laxity about QC is not a great trait in a project maintainer.
Do you happen to have a link to the thread?