[MeeGo-dev] Where's the evidence that Tizen will contain *any* MeeGo code?
alchaiken at gmail.com
Fri Sep 30 16:24:04 UTC 2011
with its lack of even one mention of MeeGo. One conclusion
consistent with known facts is
***Intel is abandoning MeeGo for LiMo just as Nokia abandoned MeeGo
for Window Phone 7.***
I haven't seen any statement from anyone who *knows* what's going on
to indicate that Tizen will actually incorporate even one line of
MeeGo code. Tizen might just be a new name for LiMo to save face
for Intel and Linux Foundation. Sure, Tizen will contain bluez and
likely ofono and connman (both because they're both totally awesome
and they're created by Intel), but does that make it MeeGo?
I welcome Joost Poortvliet's friendly outreach. I believe that we,
as a community of independent developers, should consider bodily
joining the OpenSUSE project to continue work on MeeGo under their
auspices. LiFo owns "MeeGo" and won't let us the name, to be sure,
but we can call it "OpenMobMo" or "OpenMaeLin" if you like. (That
joke is bound to have turned someone's stomach.)
But seriously, if the worst case occurs and Tizen bears nearly no
resemblance to MeeGo, why shouldn't we consider working on Qt
development with Ubuntu Core, which is focused on ARM? With
Intel's possible complete departure, MeeGo development on Atom may
completely stop, while Ubuntu Core is completely focused on ARM.
Yes, I know that would mean going back to .deb's, and I am completely
familiar with what a PITA that would be, but if we do nothing as a
community, MeeGo is about to die.
(650) 279-5600 (cell)
"What you do for a living is not be creative, what you do is ship." --
Seth Godin, vimeo.com/5895898
More information about the MeeGo-dev