Edit: In other word its open source today but Canonical have the rights to make it not so. Although the same is true for Wayland with the MIT licence a company can fork it and not release the code so its much the same either way.
Last edited by timothyja; 06-28-2013 at 10:45 AM.
Also projects like KWin have no intrests in GPLv3 license and want to remain GPLv2+ so they can't really use code from Mir at all.
Originally Posted by seb24--Source, so yes they can make it proprietary and stop releasing code under GPLv3-license.To give a simple example, suppose a company launches a new GPL-licensed project and asks contributors to sign a Harmony copyright assignment agreement with the “only OSI-approved licenses” outbound option selected. The company is then entirely free to license out all contributions under, say, the (OSI-approved) 3-clause BSD license, which in turn does nothing to restrict the company from privately licensing the project code, including contributions, under a proprietary, closed-source license. This is not some novel scenario, but what Harmony adds is the illusion of constraint, which I am concerned may mislead contributors who are relatively unfamiliar with open source licensing.
I understand that can do some sub-licence but always licence in the original licence too.As a condition on the exercise of this right, We agree to also
license the Contribution under the terms of the license or
licenses which We are using for the Material on the
XMir only exists due to years of Wayland development (it is XWayland renamed).
The Android driver support exists due to Wayland development (libhybris).
Wayland has a lot more involvement from the general ecosystem.
Basically, Canonical came in after years of the Wayland developers doing all the grunt work, put the pieces together with new names and let everybody think they had done something amazingly quickly.
1. first surprise for the ubutrolls wayland protocol is 95% ready and the only thing left is tackling the corner cases and has been ready to go since december 2012.
2. second surprise we are not waiting for wayland at all this days, we are waiting for the toolkit that started to migrate full stem ahead, as far as i can tell SDL2.0/Qt5.1/gtk3.10/EFL git
3. third surprise Video support is here vdpau/vaapi/mplayer/gstreamer/HW overlays [ofc most code is still in git]
4. fourth surprise Gnome git can actually run on wayland except GDM [still have few porting glitches if you don't use gtk+ git]
5. Qt5.1 apps like Qtcreator/qtdesigner run on wayland already and QML/C++ classes QCompositor already works pretty impressively
6. Mir was developed faster? just amuse me and check of the LOC and refactor needed in the entire graphic stack to make something like Mir/wayland even technically feasibly?[hint it ways passes the couple of millons of LOC in Glamor/cairo/mesa/kernel code/DDX/dri2-3/Drivers/etc] and this technical miracle that required to rewrite basically every part of the graphic stack almost from scratch for years has 0 Canonical contributions.
So yes mir got coded faster because wayland + community did all the massive heavy lifting while canonical waited[without 1 freaking commit] until it was good enough for them to start and in some cases take solutions from wayland code[read their bazaar and wayland git and you will see some funny things in there]
So wayland being more community don't have cool demos[we are geeks after all, we don't demo we port] but the next release of every major desktop environment[except unity] will support wayland natively, not demos or layers just native[EFL will come first and then Gnome and last KDE SC 5]