And to finish with http://tabulacrypticum.wordpress.com...teps-for-2010/

If the expectation and the parameter of measure is "open source" then yes, Maemo has been carrying many problems, in fact since its origins. Ultimately these problems go down to the mixture of open and closed components and processes, that impede to satisfy the expectations of an open source community. MeeGo is the solution proposed to this problem, aiming to push an open project with open dialog, evolutionary architecture and releases, all around a developer community.

If the expectation and the parameter of measure is "mobile platform" then I believe Maemo still is better than many alternatives in terms of openness, dialog and community. Product continuity is another story, but again if you look at the obstacles you will find that they are rooted in the closed/business parts of the project.

And well, it's always easy to blame the closed/business side of things but in the case of Maemo they have been crucial making this project scale in the agenda and priorities of a company like Nokia, instead of ending up like other alternative that didn't have such closed/business driver but then...

This is a company releasing products, competing in markets. Our salaries to do this work and the big investment to make these products come from somewhere. The community is extremely important but without the business all we would be somewhere else now.