The following component will most probably be removed from MeeGo 1.2 compliance specification and architecture diagrams
Arjan van de Ven explains:
Recently we have been evaluating these features and feel that these technologies, as integrated into MeeGo, haven’t reached the maturity that we want to commit them into MeeGo 1.2 core.
As a result we are proposing to, for MeeGo 1.2, not include these components in the official architecture diagram or the compliance spec since either means a compatibility commitment going forward as well as a requirement for everyone who makes products with the MeeGo brand to include these components. As these things mature going forward, we hope that for MeeGo 1.3 we can put a much more mature policy layer as part of the core architecture and compliance set.
He also notes that the components are not removed, but as the result of removing them from the compliance specification not all MeeGo 1.2 products have to include them.
On follow-up Jussi Liukkonen points out:
I would consider this a prudent approach. APIs we cannot comfortably commit to, we should not commit to. And these APIs have not settled yet.
However, the functionalities these components implement are quite important for actual products. I expect we’ll see a number of 1.2 based products, more or less relying on these implementations.
These components are mostly driven by Nokia. This move just might be a test for Nokia to see if they are truly engaged to MeeGo in the future. If Nokia does the necessary work to keep them for 1.3 and truly shows the motivation and engagement then the components will be available in the future, too.
On the other hand if Nokia drops the ball completely and stops maintaining these components I’m not sure if Intel is willing to drag them along alone. By removing these components from compliance specification Intel can drop them in the future if no one is left to maintain and develop them further.