I look forward to reading the Q&A here on tmo, at least I hope to. It sounds as though they are very interesting.
This is the main organised point of contact between Nokia, the paid
contributors and the community, however the maemo.org sprint process
is quite heavy for volunteers and it often seems to be a checklist
affair; rather than a collaborative planning exercise.
1) Do you see any flaws in it, and how do you think it can be improved?
2) What are your thoughts on ongoing communication during the sprint?
MeeGo is, IMHO, the single biggest thing to happen to Maemo since the
770. In many ways, it's the opening up of the design processes that
many of us have wanted in Maemo for so long. As Maemo as an operating
system disappears, this will have a big effect on the community.
3) As we move from "day zero" to "day one", what do you think the
priorities for the MeeGo community should be?
4) Should leaders in the MeeGo community (whether from a Moblin or
Maemo background) try to move the existing communities with them to
form the MeeGo community; or should a new community form around the
operating system and its devices?
4a) If yes, what steps should be taken to prevent overreactions and
allegations of "take over" that happened when internettablettalk.com's
theme changed to match the rest of maemo.org?
4b) If no, how do you see the relationship between the Maemo community
which has been "left behind" and the MeeGo community? How does the
Maemo community stay vibrant if large portions on moving on to Maemo's
successor, or drifting away to other mobile platforms?
5) What are your thoughts about existing maemo.org resources (such as
Extras, auto-builder, Bugzilla) as Nokia, and the paid contributors,
look to the future?
6) How can we encourage more, and higher quality, applications for
Maemo - and specifically through Extras?