How to have meego.com work for vendors, but eat its own dog food

David Greaves has a proposal for how the MeeGo Project can interact with the MeeGo Developer Edition which aims, for the N900, to deliver a day-to-day usable operating system by the more technically minded: Justify the DE project by extending the "DE Project Vision" to include "Be a reference vendor". Extend the deliverables to include documentation about processes, organisational layout and tool usage. Test, challenge and improve the MeeGo <-> Vendor interface. Certainly the MeeGo Project needs to better define its deliverables: is it an end-user OS that people can download for their existing hardware (a la Ubuntu); is it the well-known stack which is delivered, with a few customisations, to consumers preinstalled on their devices (a la Android); or is it a stack, available to OEMs, which allow them to shortcut the development of their own OS (a la LiMo, or - increasingly - Android)? Without this clarity, every feature request and architectural decision will be discussed with differing viewpoints of what it is the project should be delivering.

Intel's AppUp "Submit Early, Submit MeeGo" deadline interpretation?

Attila Csipa (current Maemo Community Council representative) has raised an interesting issue on the MeeGo-community mailing list about the specifics of Intel's AppUp "Submit Early, Submit MeeGo" contest deadline rules: As many of you might know AppUp has a submit early, submit MeeGo program where they plan on rewarding some of the first MeeGo application developers... (very good, thumbs up for that). However, it seems the busy-bee coders managed to swamp the AppUp validation queue and the rule clarifications implied that only applications that actually get VALIDATED before the deadline are eligible. My question is, knowing that there are a lot of Intel/AppUp folks here: Would it be possible to (as a sign of good will and support for early No response from the contest organizers as yet.

Qt homescreen widgets: failing with Maemo 5 CSSU?

Alberto Mardegan has had reports that Oculo, his new web content home screen widget, does not work with the latest Community SSU: Some users running CSSU reported that my homescreen widget (written in Qt) does not appear in their homescreen. I did a quick search on the forums, and found that the issue affects also some other widget. Does anyone have any ideas of what could be wrong? It seems that the widget loads and works properly, but it's simply invisible.

In the latest email, Alberto is considering "conflicting" with the CSSU's version of Qt which is in testing. This is certainly in nobody's interest: the aim of the Community SSU is to get bug fixes out to users. In your editor's opinion, if the bug cannot be easily fixed, a stabilisation branch of the CSSU should be branched off without the Qt upgrade and this further tested and polished to become a "stable" release.