[23:34] <jsgrant_> What is the last version of Mir, before it started to transition to (as I understand it) somefactor of 'just another compositor' for Wayland?
[23:41] <RAOF> jsgrant_: Mir 1.0 is about to be released.
[23:41] <RAOF> But what, specifically, do you want?
[23:42] <RAOF> Because Mir has been able to present a Wayland socket for quite some time (I believe my branch guess back to 2015?)
[23:44] <RAOF> And Mir has always been designed to support multiple client frontends, right back to the time when there was a Binder frontend.
[23:45] <jsgrant_> RAOF: Ah, so this is a secondary function? The way I've heard people phrasing this -- is that it was being wholesale rebranded/shifted as a wayland-compositor.
[23:45] <jsgrant_> This was Reddit ... so take that for what it's worth. :^P
[23:47] <RAOF> We'll probably drop our own client protocol sometime in the distant future 😀
[23:49] <RAOF> And we'll be unlikely to add much to it - it's much less work to use the existing Wayland backends that toolkits, EGL, Vulkan, Firefox, etc have.
[23:50] <RAOF> So now that there aren't as many people working on it, focusing on the server bit is a more valuable use of time.
[23:51] <RAOF> Also, now that we don't have a requirement for convergence the fact that the existing Wayland window manager protocols aren't suitable for that is less of an issue 😀
[23:54]  * jsgrant_ is academically interested in Mir; Not too sure if he'll end up using it for anything sans that -- kinda sad I can't find even a toy tiling-wm implemented on it. 
[23:54] <jsgrant_> RAOF: Also sad, about the convergence bit.
[23:56] <RAOF> jsgrant_: there's a toy tiling wm in the demo server!
[23:56] <jsgrant_> :^D
[23:56]  * jsgrant_ pokes around.
[23:57] <RAOF> miral-shell is the relevant bit.
[23:57] <RAOF> (in trunk, which is soon to be 1.0)
[23:58] <jsgrant_> Yeah, just found http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/examples/miral-shell/tiling_window_manager.cpp :^)
[23:58] <jsgrant_> Not too chunky-either.