[scaladev]

I am a happy Wayland user, and have been for a long time. There are many more out there. You don't often hear us because we don't spend every waking hour shitting on Xorg and praising Wayland for how good it is (maybe we should?)

>I wonder if it will ever reach the adoption level of x11

It will, considering that Xorg is effectively no longer maintained and its developers have switched to working on Wayland protocols long ago, which they have stated on multiple occasions.

Somehow I doubt that the loudmouths you often hear will step up to maintain X.

[sprash]

What is the process to become a release manager for X11 without forking it? I assume you can't just walk in there and say "I'll do that".

[tinus_hn]

I assume it starts with showing you’re up to it by putting in the work. You don’t need to be the release manager to contribute patches.

[codewiz]

But who will review your patches, if all the core devs have already moved on to Wayland?

[tinus_hn]

Who will give you maintainership?

[iampivot]

It's open source, you can provide your own distribution of it.

[bombcar]

You fork it and your fork becomes the mainly used one is how it normally happens.

[sergeykish]

Who would risk stability? And what is the issue with forking? ffmpeg/libav, openssl/libressl managed fine. No fork is the symptom.

[sprash]

The other forks you are mentioning are a completely different problem because there were inherent philosophical differences among developers.

X11 just needs "a release" so that package maintainers and distros can push updates. If you fork it you only make things worse.

[sergeykish]

Just needs a release that could contain bugs, could contain exploits. And current maintainers are not going to risk? I'm typing on X11 system, and it works, proving previous maintainers got it right. I am fine if active developers make a fork, prove its worth, some distributions adopting it, finally fork merged into base with new leadership.