Currently winning is A new category/switcher should be implemented in HAM: great, fantastic, wonderful. It's an excellent suggestion; we've even discussed it in the thread. Except who's going to do the coding? Will Nokia accept the patch? Which MU is it going to be scheduled for? When will it get into users' hands? What do we do in the meantime?

Second most popular is Add a new catalog for all CLI and library items. Two obvious problems with this:

1. It suggests putting codecs for gstreamer & other sorts of plugins in there too. Hang on, why? The use cases for command-line apps which require parameters and transparent enrichment of the Media Player are totally different.
2. How do we handle the QA process? Is it a duplication of -devel, -testing and Extras? Just the first two? What features in maemo.org/packages/ and elsewhere get delayed whilst Niels works on it?

Brainstorm rant:
This is the fundamental problem with Brainstorm: solutions don't have pros/cons stored against them. Solutions are presented as being equal. Positions can't change and people's opinions move; the debate never changes and there's no scope for consensus. The more we use it, the more I'm convinced it's a fundamentally flawed approach. Since when was the most popular technical solution the right one?

Selecting a technical solution is a case of experts and stakeholders getting together to discuss the issues and come out with a consensus, reflecting the technically possible; the pragmatic and the underlying requirements. Technical problem solving by committee and popular vote - show me an instance where this has ever worked. Please!