Wayland 1.2.0 Released, Joined By Weston Compositor

[intellivision]

I suggest that you actually browse the code.
The Flora License is only used for a handful of front-end applications in the /apps/home repositories. It makes no sense to incorporate that code into GPL projects anyway.

The back-end framewors are all under regular free licenses (Apache, BSD/MIT, (L)GPL). Random examples:

https://review.tizen.org/git/?p=framework/telephony/libtcore.git;a=blob_plain;f=LICENSE;hb=HEAD

https://review.tizen.org/git/?p=framework/system/sensor-framework.git;a=blob_plain;f=LICENSE;hb=HEAD

https://review.tizen.org/git/?p=framework/uifw/ecore.git;a=blob_plain;f=COPYING;hb=HEAD

https://review.tizen.org/git/?p=plat...03e06d;hb=HEAD

That still doesn't excuse their use, there may be ways to incorporate that code into other projects and the Flora license still actively prevents the integration of that code into projects that want to remain OSI compliant.
Also, as mentioned before, the official SDK is still released under a very restrictive license compared to most other open source projects.

[Awesomeness]

However insignificant you see it, the patent grant for certain implementations puts further restrictions on what a developer is allowed to do, and as such the OSI has still not approved it as an open source license. These restrictions would also make those components licensed under the Flora license to be GPL incompatible, which would stop that code being used in a majority of FOSS projects.

I suggest that you actually browse the code.
The Flora License is only used for a handful of front-end applications in the /apps/home repositories. It makes no sense to incorporate that code into GPL projects anyway.

The back-end framewors are all under regular free licenses (Apache, BSD/MIT, (L)GPL). Random examples:

https://review.tizen.org/git/?p=framework/telephony/libtcore.git;a=blob_plain;f=LICENSE;hb=HEAD

https://review.tizen.org/git/?p=framework/system/sensor-framework.git;a=blob_plain;f=LICENSE;hb=HEAD

https://review.tizen.org/git/?p=framework/uifw/ecore.git;a=blob_plain;f=COPYING;hb=HEAD

https://review.tizen.org/git/?p=platform/upstream/ofono.git;a=blob;f=COPYING;h=3912109b5cd65a68039d473c11c9f7ac2303e06d;hb=HEAD

[intellivision]

That Wikipedia article is bullshit. The only provision in question is the patent grant for certified implementations. But aside from Apache's no other BSD-like license even grants any patents at all, so that's not really a problem unless it's highly likely that the code uses patented techniques.
Flora License is also only used in a handful of Tizen components.

However insignificant you see it, the patent grant for certain implementations puts further restrictions on what a developer is allowed to do, and as such the OSI has still not approved it as an open source license. These restrictions would also make those components licensed under the Flora license to be GPL incompatible, which would stop that code being used in a majority of FOSS projects.

Furthermore, the Tizen SDK ships under an even more restrictive license, here: https://developer.tizen.org/ko/node/1279
The integration of closed source Bada components doesn't help the situation either.

[jayrulez]

It certainly changed to one with far less official emphasis, & subsequently EFL was jettisoned (somewhat unceremoniously) in favour of C++.

http://slashdot.org/submission/2505829/tizen-not-as-open-source-drops-efl-to-merge-with-bada

https://twitter.com/migueldeicaza/status/304690722156716034

Unless things have changed quite a bit since the end of February...

That is your interpretation of what happened. The EFL APIs were superseded by an API that is more geared towards mobile development with proper application life cycle management for mobile devices i.e. the OSP framework that was used with Bada. There is even a graphical UI builder in the SDK for OSP applications. There is no reduced emphasis on the native framework now. It is even more complete than the web runtime framework and is as well documented. You can check it out: https://developer.tizen.org/document...cover_page.htm

All sample WRT apps in the source tree also have OSP equivalents and some EFL equivalents.

A side note, EFL is still present in Tizen, it is used as the backend to the OSP.

You can find all the info you could want about tizen on the tizen.org website or one of their community websites, no need to rely on opinions posted on slashdot.

[Awesomeness]

I would be wary using it as its license isn't exactly FOSS (https://en.wikipedia.org/wiki/Flora_License).

That Wikipedia article is bullshit. The only provision in question is the patent grant for certified implementations. But aside from Apache's no other BSD-like license even grants any patents at all, so that's not really a problem unless it's highly likely that the code uses patented techniques.
Flora License is also only used in a handful of Tizen components.

[skriticos]

So, with everyone just pulling in the xkbcommon library, is there any chance that we get a decent documentation for it? I have spent considarable time trying to figure out how it works in the last few weeks creating a customized Dvorak layout with emphasis on programming (yea, I know there is stock one, I don't like it). Anyway, the XKB configuration - while being very powerfull - is also one with the worst documentation.. ever. Try to create a keyboard configuration with multiple levels and map shift level switches to normal alphanumerical keys and let them behave differently (be different shift/control keys) on various shift levels? You are in for a good ride there. Not to mention all the legacy convention in there. My head hurts.

[MartinN]

Congratulations gentlemen

Keep up the awesome work-it is as important as what Linus did 13+ years ago. It will give the world the best desktop while bridging the X legacy into the future.

[jalyst]

The articles were probably wrong as native development didn't go anywhere.
The license only matters if you want to fork the project, otherwise it is a non-issue. You could also use the unofficial Qt SDK to create tizen apps with native code.

It certainly changed to one with far less official emphasis, & subsequently EFL was jettisoned (somewhat unceremoniously) in favour of C++.

http://slashdot.org/submission/2505829/tizen-not-as-open-source-drops-efl-to-merge-with-bada

https://twitter.com/migueldeicaza/status/304690722156716034

Unless things have changed quite a bit since the end of February...

[jayrulez]

I know what it was, the Tizen SDK 1.0 only had HTML5 support. They seem to have brought it back in later releases.

Qt isn't officially supported on Tizen. A service similar to Ministro II on Android would be needed before any Qt applications could be run.

Also the clause You may not load or install any of the Tizen SDK onto mobile phones or any other devices, except a personal computer. in the Flora license is quite strange to have in a project that is supposedly open source and developed in conjunction with the Linux Foundation.

You could always bundle Qt with the application. Qt is not the monolithic framework it was. It may be a bit larger than using the tizen apis but it's no bigger than Xamarin.Android and Unity which are very popular.

I don't think many if anyone will be developing mobile apps with their phones and tablets so that clause shouldn't be a problem for developers.

[LinuxGamer]

Looks Like we may see KDE running on Wayland soon

"My notbeook has been using a KDE+Wayland session for a complete day. Let's see how long it will last :-)"

https://plus.google.com/115606635748721265446/posts/ZpRpYG2uv3L