Yep. Open governance for Tizen 3.0 was "unveiled" 3 years ago, yet still applies to exactly zero commercial Tizen devices. We're still waiting.
Let me re-post what I said on this exact topic back in August 2014: ---- The Tizen Project is broken. We will be spending some time apart. AUGUST 13, 2014 BOBSUMMERWILL I’m very sad to have to say this, but the Tizen Project is broken, and we’re going to be spending some time apart. It makes no sense for Kitsilano Software to spend any more time or money on building MonoTizen at the current time. The Tizen OS has got amazing, world-changing potential, but the organization and communication on the project as a whole is terribly broken. I could publish a long laundry list of specific issues and there are many. I would be happy to have a more detailed discussion with anybody who would like to listen and who has any ability to change things. For now though, I’ll keep the feedback really simple. For collaborative projects to work you need trust between partners, you need to do what you say you are going to do and you need lots of open communication. There is no public roadmap for Tizen Mobile, the most important profile. Despite devices being promised on multiple occasions there are still no devices. The Unpacked event in Moscow was cancelled with 48 hours notice and no reason given. There was no further public statement for another week or so. That statement, when it finally arrived just said that there was no future roadmap. I have no idea what is going to happen in the Tizen project tomorrow, let alone next week, next month or next quarter, because there is no public information. No third parties can build a business with no public roadmap. It should be no surprise that the ecosystem is not where we would all like it to be. It makes no business sense for third-parties to engage given all the uncertainty. The worst thing about the apparent cancellation/delay of the Samsung Z phone is that the release of that phone would have given the whole Tizen eco-system something to anchor on. 100% revenue share is a great draw, but 100% of $0 is still $0. We need devices and fast. I really enjoyed myself at the Tizen Developer Conference, and I would like to publicly thank everyone who has helped me get started with Tizen, and welcomed me into the community. I hope to be back in the future, but for now we are going to spend some time apart. It appears that Mono-3.6 has finally been released, so we will release matching Tizen RPMs either later today or tomorrow as our parting gift to Tizen. I really hope that the Tizen Project can change, and can work in the spirit which the governance changes for Tizen 3.0 indicated was planned. ------- See also: - https://kitsilanosoftware.wordpress.com/2014/08/13/the-tizen-project-is-broken-we-will-be-spending-some-time-apart-3/ - https://developer.tizen.org/forums/native-application-development/huge-difference-native-environment-between-2.2.1-and-2.3 - https://www.engadget.com/2015/07/22/tizen-the-emperor-has-no-clothes/ - https://www.engadget.com/2015/09/17/tdc2015-tizen-3-0-first-milestone-what-does-that-mean/ On Tue, Jun 14, 2016 at 4:54 AM, Olivier Nyssen <nysse...@gmail.com> wrote: > I've been a participant in the Tizen project since day one: it was a very > strange journey indeed: > In a nutshell: > Phase 1: HTML5 !! no native > Phase 2: HTML5 and Bada > Phase 3: HTML5 and EFL > Phase 4: EFL and oh, yes ... HTML5 > Phase 5: our new Artik IoT platform ships with Fedora > > Zero consistency, zero communication, zero respect for developers; > and in the meantime: Android has 90% market share, so it's effectively > "game over" for Tizen Mobile > > > On Mon, Jun 6, 2016 at 6:00 AM, Olivier Nyssen <nysse...@gmail.com> wrote: > >> Hello everyone, >> >> Tizen is a big succes for watches and TV but I have big doubts concerning >> the mobile strategy, which is the real difficult part, since Tizen Mobile >> is competing with the almighty Samsung Galaxy division. >> >> The Z1 phone was released in India in January 2015, the Z3 in October >> 2015 and is still only available in India. India is a very big country but >> it's impossible to create an ecosystem with one country: why would a >> developer invest his time in a concept which has zero momentum and no >> roadmap? Developers have been burnt by the Samsung Bada disaster and Tizen >> Mobile seems to have the same destiny... >> >> Regards, >> Olivier >> > > > _______________________________________________ > General mailing list > General@lists.tizen.org > https://lists.tizen.org/listinfo/general > > -- b...@summerwill.net
_______________________________________________ General mailing list General@lists.tizen.org https://lists.tizen.org/listinfo/general
