2011/4/1 Jussi Liukkonen <[email protected]>: > On 1.4.2011, at 19.07, Arjan van de Ven wrote: > >> Late last year, in the Architecture meeting, we had agreed to include timed, >> MCE, Sharing Framework, >> Non-Graphics-Feedback (NGF), Profiles, and Qt style APIs (QmSystem) >> identified on the >> http://wiki.meego.com/Architecture as new technologies into MeeGo. We had >> hoped that all the >> documentation and source code would end up well integrated into the 1.2 >> release of MeeGo. >> : >> NOTE: this does not mean that we are removing the packages, it ONLY means >> that we aren't requiring these components >> to be included into each and every product based on MeeGo. > > 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. Design/review/maturization work on > providing the covered functionalities in a sustainable way - based on these > implementations or others - should start quickly, and consider migration from > the current interfaces, in order not to disrupt the 1.2-based product vendors > too badly.
Then it's good that the components aren't actually being removed, just not part of the compliant set, just like emacs isn't required to be installed on all MeeGo devices. Reference UX will not be relying on those components either. It'd be good if it some basic information on what the problems are currently with those components could be listed (wiki pages) along with pointers from component maintainers on direction and where to contribute. That way we avoid having a lot of separate versions of the components at vendors as well as a avenue for contribution to provide it again properly as a candidate technology for 1.3 track. BR Carsten Munk > > Disclaimer: I am involved with Harmattan. > > Cheers, > - Jussi > _______________________________________________ > MeeGo-architecture mailing list > [email protected] > http://lists.meego.com/listinfo/meego-architecture > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
