More steps:

The process for handling MeeGo requirements is now open. Sami explains the details at http://meego.com/community/blogs/sam...o-requirements

Basically, http://bugs.meego.com is used as the tool for proposing features and manage requirements. There is now a new classification "MeeGo Features" where new proposals must be filed.

There are already more that 240 features submitted, most of them targetting the MeeGo 1.1 release: http://bit.ly/d8lBCL

The requirements process is managed in combination with the roadmapping process: http://meego.com/developers/meego-roadmap

In Maemo we never achieved this level of open planning. There were attempts through bugs.maemo.org and then the maemo.org Brainstorm. The conclusion was that this process can only work if it's pushed directly by the real product managers, and this is how it works in MeeGo. It was also quite clear that a majority of people involved in the real work preferred the well known Bugzilla over yet another tool.

Please watch, vote and comment to the feature requests that matter you most. You are also invited to submit new proposals.