If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.
We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to express, please simply give that post a instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.
Please note that this is an advisory “straw poll” meant to gauge sentiment. It isn’t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.
Labwc, KWin, Wayfire, Hyprland, Sway, River and Niri
Are officially tested Wayland compositors for LXQt. They never mentioned miriway in any way.
Kwin is likely the best supported one (in Fedora), and the only one that supports a few features in the panel.
Labwc is very lightweight, RaspberryPi OS switched to it too, formerly used Wayfire.
I think it sounds more reasonable to bundle in ANY of those, and I think kwin would be the best option (if automatic installation of a ton more packages can be limited to the minimum)
What is so great about Mir? I found that miriway is the floating, miracle is the tiling variant of it.
While I like KWin, the other members of the LXQt SIG were wary of pulling in KDE components because of the perception of “bloat”. The technical argument that swayed me was that the KDE portal (which goes alongside KWin) doesn’t really work outside of KDE Plasma without some significant work.
Most of these other window manager compositors are kind of a pain to integrate into a desktop environment.
The Mir team is interested in supporting an effort for a portal implementation that can integrate with desktops well without requiring every desktop to build one from scratch.
Miriway is designed to be the “let’s combine Mir with an existing desktop” compositor, whereas most of these others do not have that as a goal. And the portal system is basically a requirement for functional Wayland environments these days, so the fact that the Mir team is interested in supporting that alongside the protocols-based approach that a lot of Wayland CLI tools use makes it a very appealing option.
It also helps that Mir has a much better ABI stability story than wlroots, which leads to less headaches overall.
For some more details about this, I gave a talk (alongside Alan Griffiths from the Mir team) at the Ubuntu Summit about Miriway and demonstrated Fedora LXQt running on Miriway.
Summary
instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.