Hi,

the number of reported bugs and indeed the number of comments in bugs.maemo.org strongly increases these weeks. I think it's not easy to triage alle the incoming stuff in all areas of interest in bugzilla.

Maybe one way to be more efficient in triaging is to differentiate the attention in bugzilla. To get an better overview who is whatching what I made a little list in the bugsquad wiki page:
http://wiki.maemo.org/Bugsquad#Bugsquad_Members

Please feel free to add your preferences there or improve this section of the wiki page.

We also can discuss this subject here and in the community mailing list.

Best regards,
Uwe aka jukey

--
Uwe Kaminski
http://internettabletblog.de

Highly welcome, thanks, as lots of people have more knowledge and expertise in their fields of interest than the bugmaster guy who tries to cover every report from the kernel patch to the non-working UI button and hence often asks really weird and completely clueless questions. :-)

I was just writing something else, and I had this random thought. Could someone add a line to the bug-comment box that said something like "Are you adding anything new to this bug? If your comment is 'me too' please vote for the bug instead".

Sorry - probably not relevent. But I know that 'me too' comments are becoming a problem and giving Bugzilla indigestion.

That's actually a suggested feature in my proposed device-based bug reporter.

Like https://bugs.maemo.org/show_bug.cgi?id=8551 ? :-)
All possible once Bugzilla 3.4 is in place (Karsten is working on it, should be done next month).

Um, when was my name removed from the list of members? . . .

I made the new lsit using copy and paste. Maybe I deleted your name accidentally. If so, my apologies! I'll have a look for the history of the page and re-add your name.

Update: Yes It was my fault and it's corrected now.

Please see the QA group proposal at MeeGo.com: http://wiki.meego.com/Proposal_for_a..._working_group

This isn't really relevant here (even though there may be some overlap of interests).

However, since you brought it up, how should we go about planning the meego bugtracker? I think bugzilla is a given, but that still leaves a lot of details to be discussed like scope (eg whether it will also host community projects), status and resolution values, product/component structure, default search options, etc.

It's relevant to some who are currently looking to span both worlds.

As for MeeGo bug tracking... there's some preliminary exploratory work being done that will go public soon, after initial testing and feedback. Everything you brought up will be part of the public discussion.