@SaHaRaSquad
"decision of the CoC committee" sounds a lot like the FOSS version of "you have violated our terms of service. Stop asking questions"
@YourComputer
That level of dedication is rare, but he's taking on a task where burnout has a significantly high probability of occurring.
@fcolecumberri
6:46 Brodie: FreeDesktop This is the biggest mistake that you will ever made. FreeDesktop: naaa... we can do worse.
@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.
@tranthien3932
Wait, I thought this is a Wayland-shill channel.
@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…
@palaashatri
Hey Brodie, have you heard about XLibre???
@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.
@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.
@Akselmoi
I'm sure these comments will be full of calm, reasonable and intellectual discussions.
@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!
@tato-chip7612
CoC is the HR of the FOSS world.
@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!
@nordern1
Didn't even call it Y, SMH
@dnman192
Least unhinged FOSS developer.
@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.
@-1_void
I'll watch this man's career with great interest. This is gonna be fun.
@Skarsnikum
For people that are missing context : Wayland is way behind xorg in terms of features, even though it provides things xorg is missing, which was fine like 5+ years ago. But now it starts to show since we are way past the point "Yeah it provide stable display" and people want to have the missing thing back (Accessibility features are a major issue, for example). I will not say one is better than another (probably depends on your needs), but killing xorg totally was extreme. It's actually a good thing to have people working on maintaining it and maybe that will make Wayland make faster progress toward it missing critical features.
@notuxnobux
They are now openly admitting on mastodon that they worked hard to kill Xorg
@BrodieRobertson