I hope people don't think they can't suggest an idea for an initiative without being on the council! Maemo becoming MeeGo will have an impact on our community which is currently unclear, so it's probably not the time to introduce sweeping new initiatives.

Having said that, I want to allow the monetisation of maemo.org downloads, so we don't have to force community developers to Ovi if they want an easy, and obvious, way of earning a few extra quid. I think Randall's community outreach programme - and the corresponding collateral for use at community events (such as onedotzero) - is an excellent idea which needs further fostering.

This is on top of the "ongoing" activities such as supporting Google Summer of Code, a summit later in the year and so on.

I think there's a desire for transparency from all, and an obvious desire from the paid contributors to concentrate on delivering requirements, rather than page-long weekly reports. The current Qaiku workstream isn't very public, or easy to follow, however the sprint task summary pages are getting better at being maintained, and provides an at-a-glance summary of the current work.

I would rather see effort expanded on key community communications about changes which affect users and developers rather than a requirement for regular reports. For example, the move to drop.maemo.org for uploading to Extras; the move to vcs.maemo.org for version control and the changes to the karma scoring were all very poorly communicated by their task owners. Developers were left scrabbling around deep into mailing list threads for answers, and consensus-driven karma changes were tweaked "because it could be an improvement".

This increase in accountability could, I think, be achieved by the maemo.org paid contributors better setting and running their own priorities. Instead of the council chairing the sprint meeting, it should be done by themselves in public; chaired by X-Fade. This could continue to be done via IRC, or be mailing list or locked forum (whatever works for them). The group have two customers: Nokia and the community; and these two customers should feed in requirements (the first via Quim Gil & Tero Kojo; the second from the council). These would be put into the pot with the internal-driven work. I believe this would result in a clearer set of tasks and a more managable sprint process.

Having been involved in the creation of the council, and been a member twice, I hope to "scratch the itches" which have developed over the last six months. It's been great to watch another group of people make the role their own, but stepping back has given me a clearer vision as to how community facilitation could be improved.

I also hope to shape the formation of the MeeGo community and its interaction with the commercial MeeGo stakeholders; the chance to set that on the right path will mean we could get a great sense of satisfaction looking back in 5 years at a successful ecosystem which we shaped.

Being a professional software developer/consultant/architect means I'm used to listening to end-users with a limited technical understanding (as their focus is, quite rightly, on their roles). I think this gives me experience and professionalism which could serve as an example to others.

It'll be shipping, as a default OS, on one core mobile phone device (e.g. the N900 successor); and a number of manufacturers using it as an open source base (e.g. LG). I don't think we'll see any netbooks shipping with it as standard, although a larger tablet device may ship with it, depending on how the iPad is received on launch.

I think MeeGo will, a year from now, be facing many of the problems Android has faced in the last year or so: multiple manufacturers not really coordinating very well (beyond a core set of manufacturers), with many shipping custom "value-add" user interfaces. (Value-add applications is fine, but changing the fundamental UI interactions of the platform is a recipe for disaster with no third party application really able to blend in). This fragmentation is causing real pain for Android users and developers, but will be overcome. If MeeGo goes through the same pain, it may not be able to catch Android up.

Eek, this sounds like a job interview! Going back into a mode of trying not to get my heckles raised by trolls and always trying to present a professional demeanour. I don't think it'll be too hard, as it's something I have to do on a daily basis anyway, but will have to keep up in my spare time.