View Single Post
Posts: 968 | Thanked: 974 times | Joined on Nov 2008 @ Ohio
#9
Originally Posted by Stskeeps View Post
Only thing really added on top is the compliance stuff which is in it's early stages but needed to deliver on one of MeeGo's benefits, which is the promise that a MeeGo compliant app will run on a MeeGo compliant device. And that there's things to be solved (stating our faults instead of it being one big marketing slide praising MeeGo)
So, is there a roadmap / timeline for completing the compliance stuff? Or is it something that will be quickly addressed so that one of the major players can release a MeeGo (or MeeGo instance) device?

As has been noted in other discussions, nobody can release a "MeeGo" device unitl the compliance standard is set. It's assumed that anyone who releases a "MeeGo" device before the standards are set is by default non-compliant, and would likely end up discussing this with legal council.

So, to a degree, it doesn't matter if MeeGo is on 1.2, 1.3 or 2.3 if the compliance issues aren't addressed.
__________________
*Consumer*, not a developer! I apologize for any inconvenience.
My script to backup /home and /opt
Samsung Galaxy S Vibrant, Huawei S7, N900(retired), N800(retired)