The Maemo community is the single biggest asset, but I don't view MeeGo as a marriage (imagining merging two existing communities was too hard, and lead to feelings of hurt that Moblin seemed to be providing the technology and Maemo the consumer hardware, Qt-based UI and - probably - developer tooling).

This isn't a marriage, it's a child. It's a new platform and a new community - but the Maemo community seems to have far more power and cohesiveness than the Moblin community, so how do we bring that 5-year old knowledge to MeeGo? Now, I think trying to shove the Moblin folk and the Maemo folks together under meego.com would be a mistake. However, the next council (of which I hope to be part), will have a lot of work to do:

• Should MeeGo have a community governance structure alongside its technical one?
• Will the technology of MeeGo provide a realistic upgrade path for Maemo devices shipped without MeeGo (e.g. N8x0 and N900, even 770). If not, what happens with maemo.org? Will Nokia still pay the bills? Many questions and issues here!
• The maemo.org paid contributors are having their contracts continued, what role can we help them have?
• Who do we need to work with in the Moblin community to bring the constructive elements there over to meego.com?
• What happens with the summit? What happens to key Nokia-based members of the community like Quim? Is/was there an Intel equivalent?
• If there're company app stores like Ovi and AppUpSM, what about Extras? How does the MeeGo community do QA across multiple devices if we/they continue to have community (yum) repositories?

As a developer, I'm not too worried. Yes, it's RPM rather than deb, but Qt Creator, MADDE and the resulting Maemo 6 SDK were game changers anyway. But it's the community that's the real question, and successfully transitioning us without losing too much.