- Would go back in time, and re-base itself on code from February of 2024 (almost 2 years ago) and
- Rename their branch from master to main.
Putting aside the obviously woke main branch name change
The goal here appears to be to make new releases of Xorg which have as little influence as possible from past contributions by the main developer of @XLibreDev.
While the motivation of Xorg seems obvious Xorg has personal animosity towards the lead developer of XLibre, stemming from a combination of him forking Xorg as well as him having non-Leftist political views (which is not allowed) the fact that Xorg is looking to make an effort at new releases *at all* is more than a little peculiar.
Over the last few years, key developers of Xorg (and Wayland) have made it clear that a primary goal of the Xorg Foundation is to, ultimately, kill off Xorg entirely (in order to drive adoption of Wayland, by force). And, to that end, they have been working quite hard, refusing (literally) thousands of code submissions over many years and dragging their feet on significant features and fixes (many of which are already incorporated into the XLibre fork).
Is this a reaction to the widespread adoption of XLibre, which appears to be gaining momentum? Or, perhaps, is this bizarre strategy prompted by the fact that Wayland adoption has stagnated (sharing roughly equal market share as Xorg/XLibre), despite forcing Wayland on users for several years?
Will this approach be formally adopted? It appears likely, as this is a proposal from Alan Coopersmith, an Xorg Foundation Board member and Xorg release manager.
https://t.co/LF8oFJ8TO5
media (112):
ca75dcec9cf8aef15323d3ec834a46300ffe64fbb3eed74006df8f899ac71e99media (112):
985f30ed054a00872081251d1cd45af630e9f5fc8bf35f9f9e4b511b28742421time (10): 1768903572
time orig (10): 1768885585
id (19): 2013553642247258616
id orig (19): 2013478195199176852
uid (27): 1464280101638799360 akrmn21
uid orig (34): 1413994775267643396 LundukeJournal
