Well, they might do it the canonical way. Take all the hard work from others - eg take the Wayland solution of how this minimize thing has been solved - , put some ubuntu sauce on it, so it can't be used anywhere else and call it their own, superior Mir solution.
Just a thought.
less coolness pls
first, i supposed that leveraging the hard work from others (so that you can "stand on the shoulders of giants") was the whole point of the GPL - now becomes a crime?
second, AFAIK (correct me if im wrong) Wayland puts much window management awareness onto clients, and involves communication between clients, the WM and the compositor) involving - whereas if i understand it correctly, Mir wants to achieve single process operation and as transparent window management as possible - that sais diametrically opposite approaches to me
thus, if wayland code is looked at (difficult, going tdd implies writing one testcase > one code line > one testcase > one code line, thus only ad hoc code ends up in place) that would be for the basics (like the redraw loop) or as a reference how not to do things
Hahaha the Wayland that is done, that is version 1.0, released, the greatest thing ever so good it's not in any distro since nobody deserves them, couldn't minimize? Sure, Wayland is complete...riiight...
The 1.0 release was to mark that the Wayland protocol and API was declared rather stable so that developers could start working on their software and not expect it to break every new Wayland release.
As I understand, Wayland has come pretty far.
What remains is improvements to the Wayland backend for GTK and Qt, and also XWayland.
GTK's Wayland backend is probably getting in pretty good shape for GTK 3.8.
XWayland is a bit unstable and needs work.
Many applications needs to be ported from GTK2 to GTK3 and from Qt4 to Qt5.
Many applications needs to stop using X11 calls and not rely on Xlib.
Mir still has to do a lot that is already done in Wayland, in addition to getting support added to toolkits (which is mostly done for Wayland), waiting for those apps to be ported to (or compiled with) versions of those toolkits which support Mir, and making apps less dependant on X.org (which, thanks to Wayland, is already in progress).
Now look at Mir's todo list and say with a straight face that Mir has less to do than Wayland before it's finished.