Dialler application for MeeGo gets openness boost
Intel's Shane Bryan has posted an announcement intended to stimulate contributions to MeeGo's reference dialler application: In an attempt to improve communication among the currently active (and increasing daily) dialer contributors and to increase general community awareness, I will be kicking off the first weekly Dialer Project meeting on #meego-meeting starting next Tuesday, April 5th, at 15:00 UTC (07:00 PST).
Intel's MeeGo Tablet UX Components are now available for Ubuntu development
Antonio Aloisio has announced that Intel's MeeGo Tablet UX Components are now packaged for Ubuntu by Forum Nokia: Intel´s MeeGo components are now ready for Ubuntu! You can download the packages from our FN PPA repository. As noted in the thread about the open sourcing (see our Annoucements page), the MeeGo Tablet UX Components are supposed to be building on top of the base provided by the official Qt Quick Components.
Another MeeGo architecture direction mail
Following the previous architecture announcement (and the flurry of concerned and confused emails it caused), another MeeGo architecture announcement mail came to MeeGo-dev last week. Again from Arjan van de Ven, 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 thehttp://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. 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. Once again it's unclear how "we" is to be defined here, given last time it didn't actually include the Nokia half of the MeeGo architecture team. It's also unclear where, and with whom, the discussions took place (and whether the meeting minutes are public).
It remains concerning that the governance described in the documentation still doesn't seem to match up with reality. As it stands, the closed-door unilateral direction certain things seem to be moving in isn't likely to encourage much in the way of outside contribution in the future. If the process is invisible and impenetrable, well, you're not going to get a lot of interest (excepting the negative sort).
Multi-button headset protocol progress
Joerg Reisenweber and Jacek Milewicz have been looking again at the communication mechanism used by multi-button (that is, play/pause/next track and so on) headsets, but still would appreciate information from engineers in the know: Brilliant Mr. jacekowski checked serial protocol of multibutton headsets for DocScrutinizer, so we got a clue now how to finally support those on N900. Nevertheless info from Nokia regarding specific format/codes on that interface much appreciated and asked for.