@nullplan01
He also added a code of conduct to his repo, namely that he has none. I'm going to say he doesn't like CoC committees very much.
@SaHaRaSquad
"decision of the CoC committee" sounds a lot like the FOSS version of "you have violated our terms of service. Stop asking questions"
@palaashatri
Hey Brodie, have you heard about XLibre???
@YourComputer
That level of dedication is rare, but he's taking on a task where burnout has a significantly high probability of occurring.
@tato-chip7612
CoC is the HR of the FOSS world.
@abit_gray
If it was CoC decision, unless they make their position transparent (even if it was "we cannot host him because he is talking bad about us"), I will put 100% blame on them. In FOSS world having little to no transparency should never happen.
@BulkybearOG
I think freedesktop owes an explanation of why he was banned in the first place for seemingly just foking the project after they continually railroaded patches for years…
@naimatomomade
RedHat employees: X11 is broken beyon repair, abandon it or go and fix it youself, we at RedHat wont do it for you; Someone tried to fix it RedHat employees: you're breaking X11.
@tranthien3932
Wait, I thought this is a Wayland-shill channel.
@fcolecumberri
6:46 Brodie: FreeDesktop This is the biggest mistake that you will ever made. FreeDesktop: naaa... we can do worse.
@guss77
X-org code is often pretty terrible, so taking a lot of time to just move things around to make them less terrible (i.e "cleanups") makes a lot of sense to me - while understandably other devs who want this project to die slowly and quietly remaining mostly unchanged (so it can be reused as an interim compatibility layer) find negative value in such cleanups. I don't think one approach, or the other, is more "right" in this conflict of interests, so forking is the only sane way to move forward.
@Doc4
Everything else aside, I'm really getting tired of how most of the time I hear something about freedesktop it's them interfering with projects they don't like on a basis that has little to nothing to do with whether software is FOSS or is compliant with the rules as stated. I'm tired of the zealotry and purity testing, just get over yourselves and make cool stuff!
@Akselmoi
I'm sure these comments will be full of calm, reasonable and intellectual discussions.
@nordern1
Didn't even call it Y, SMH
@notuxnobux
They are now openly admitting on mastodon that they worked hard to kill Xorg
@John-o5e5j
As Sebastian Wick, a prominent GNOME developer said recently, "We worked hard to kill it" ("it" being Xorg). No wonder they hate it when someone forks it!
@aquapendulum
It has been 0 day since the last Wayland-Xorg drama.
@theredtechengineer1480
I for one am looking forward to the first major X release since the 1980s. Its hard to believe we've been stuck on 11 for so long.
@TyrHeimdal
I've been actively using Wayland for some years now with Hyprland (and KDE before that). What I've come to realize is that the usage has largely been possible due to Vaxry's work. We're talking YEARS of fundamental features missing in lackluster DE's such as Gnome. Speaking of Gnome, it seems they are a hostile entity whom have (for a decade!) slowed down and blocked development of Wayland only to suit their needs of playing catch-up on features. And as such should've been removed from any decision-making capability. Even today we're missing core functionality and I believe this is directly related to Gnome's agenda. Even if I think Wayland makes sense to pursue at this point, forking Xorg totally makes sense. Big tech companies have (unfortunately) infiltrated and taken over open source, turning everything into the vision of corporate needs - rather than the normal users that made everything they benefit so much from.
@BrodieRobertson