I think Dave's point is longer lived than right now. Managing the maemo.org staff is not the job of the council - we're customers and stakeholders who want "things" done in a timely and open way. By moving to a position where we state our requirements and it's up to the team to organise themselves to deliver them, alongside their internally generated requirements (BAU) and Nokia priorities. As Dave kick started this, the council was discussing with Niels (X-Fade) the handover of the administration of the sprints to the maemo.org team themselves. The council, and Nokia, would feed our priorities into that process - and the process would be open for everyone to see as the team split up the tasks, take ownership and deliver them. Volunteers from the community would be able to chip in in either specific areas (and the council can act as a rallying point if needs be) or on whole tasks of interest.
With that, some of the requirements from the Council are, in rough priority order: Finalise SSO for maemo.org; including Talk account merging. Bugzilla easier to use (requires upgrade?):Bugzilla style improvements Bugzilla voting improvements ("me too" button?) maemo.org/packages/ QA improvements for maintainers and testers Consolidated documentation for developers (see Info Center thread for my thoughts) Autobuilder auto-optification Donation framework on maemo.org for authors to accept donations, if they so wish Items #1 & 2 have no real benefit to a future MeeGo transition, but meet immediate problems. Item #5 may help as appplications are increasingly written with tools like Nokia Qt SDK and we need the auto-builder to improve them. The others will give experience we can translate to meego.com, and possibly even implementations.