Quim Gil thoughts

Quim Gil is Nokia's MeeGo Community Manager, and has been involved in Maemo for years. In a post on talk.maemo.org, he describes his thoughts so far: I have to say that I'm waiting for more news to come in relation to Qt and MeeGo, from Nokia, from my colleagues working in these teams and from other Qt and MeeGo stakeholders. Mobile World Congress hasn't even started and the dust from yesterday's announcements is far from settled.

I understand how someone reading yesterday's headlines and trying to catch up with all the heated feedback and rumors can get to fast conclusions about Nokia and its role around Qt and MeeGo. Even to fast conclusions about Qt and MeeGo themselves. With the news only coming out on Friday, it's obvious that Nokia as an organisation needs to digest the changes before people and projects understand the full impact.

What now for MeeGo? Some proposals

Fallout from Nokia's recent announcements is still on its way down, but David Greaves is looking towards the future: So Nokia has dramatically reduced commitment to MeeGo and has cited, amongst other things, MeeGo's inability to deliver a focussed baseline with sufficient speed. I happen to agree with this failure (and given Nokia was a significant part of MeeGo's management I don't think there's a blame issue - more a how do we fix it issue) David goes on to list a focus on providing a base for vendors, and a platform for developers, as realistic deliverables for the MeeGo project; something your editor happens to agree with. MeeGo can target vendors as an open provider of an "ecosystem in a box". This is effectively what Elop wanted, but couldn't wait for MeeGo to deliver. Providing vendors with a ready base, app stores and a slew of developers is the best way forward in your editor's opinion.