zlacker

>>throwa+(OP)
Well-known developer Enrico Weigelt just forked the X server from freedesktop.org after getting the boot [0].

[0] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...

[1] https://github.com/X11Libre/xserver/commits/xlibre/prepare/

>>throwa+9
Is there any discussion about him being removed from the project on a mailing list or some other channel?

I can't find a "why" in the handful of PRs I opened.

>>sspiff+o4
There’s some drama in https://gitlab.freedesktop.org/xorg/xserver/-/issues/1797

>>ck45+v5
Wow: “xrandr doesn't work anymore on xorg-git” “I do not think this should be specifically on you, it is not unreasonable to expect that the author of a change tries their change before even submitting it upstream.” does not give a warm fuzzy feeling about the author of the at-fault patch leading a fork.

>>cwillu+27
I think it's not the one to blame who broke this but those who implemented everything all the time without adding any tests. Xorg has quite a large codebase but almost no automated tests.

>>micw+Vg1
So we agree that the maintainer is at fault: he wanted to change things and not have to thoroughly test his changes by doing the boring work of adding test coverage to the modified area.

>>cwillu+HB1
There is no arguing about that, the maintainer made a mistake. (Among other people, and it was insignificant anyway.)

So now that we agree on this, what now? How exactly does

  > does not give a warm fuzzy feeling about the author of the at-fault patch leading a fork.

follow? E.g. do you think that none of the Wayland developers ever made any mistakes?