On Friday, 30 de September de 2011 14:25:56 Dave Neary wrote: > Another added advantage: MeeGo 1.3 was, I hear, below quality and > running late. By moving to an SLP based platform, MeeGo gets an existing > platform that's actually shipping in devices and has been proven to > work. Of course, this advantage also comes with challenges: parts of SLP > were closed, and moving to it will result in significant investment in > MeeGo being dropped.
I think this is a difficult statement to prove or disprove.
You're comparing a hypothetical state (MeeGo 1.3 if development were still
100% when it launched) to a future state (SLP turned Tizen 1.0).
This is one of those "we'll never know".
In any case, the situation we're faced with is that: there is no Tizen
codebase, repository or even community infrastructure right now. The choices
presented are:
a) continue working with MeeGo as it is today, given the infrastructure
already present
b) stop, wait for the new releases and resume from there once they open up
At this point, it looks to me like a no-brainer decision. The big question
will come when Tizen has something to show and the community can join. In the
meantime, the community can do some soul-searching and figure out how it wants
to answer that question.
And as more information on Tizen becomes available, the community can start
adjusting MeeGo to go in that same direction (assuming aligning is what it
chooses to do).
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
