The confusion with the word "Official" could perhaps be avoided by renaming the classifications, but another problem is the QA contacts (which are shared with Fremantle so we can't change them and we don't want to spam Nokia with "our" bugs either).

So, after some consideration I'm leaning towards the separate product option. I propose we create a "community-something" product under Extras, with some pre-defined components based on what patches are currently available, plus a "general" or "other" in case something fresh comes along.

Workflow-wise, should we re-assign the existing bugs to Extras/Community/whatever or clone them?

To be honest, I don't see this as a very long term activity. There are only a finite number of contributed patches we can package after all, and I remain hopeful that Mer^2 and/or Meego will provide a more viable distribution for the OMAP2 devices in the long run.

You mean something other than bugs.maemo.org? I'd like to avoid that if possible for various reasons (the bugs, discussions and patches are already on bmo, users shouldn't have to create yet another account to file bugs etc).

At the moment I'm using the pre-existing versionsing scheme, simply because I didn't want to think too much about it (the testing SSU is '5.2010-09-2" for example, or perhaps it should start with 6?) but it's not cast in stone, ideas welcome. Keep in mind that for all intents and purposes it is a slightly patched Diablo so a radical departure like calling it Elephanta or something would seem misleading/inappropriate.