[Bugsquad] new release, more incoming bugs; what does the future hold?

[zahl+kde at transbay.net]

http://bugs.kde.org/weekly-bug-summary.cgi

All hands on deck? We're starting to drift into the red with all the bugs
coming in from the new release. Let's have a little triage fun in #kde-bugs!

How long do we wait for another BugDay? 
And what do we hit up next?

I suggest we continue to use konqueror as "ongoing triage" and use it to
train random people who are interested in joining, since we have fairly
extensive documentation for it already.

kmail is second in the list... But I suspect that is trickier to triage.
kdelibs is 3rd, kio 4th. I really really doubt we can put novices on that.
Perhaps an "advanced" day can take down some of those?

Leaving us with kopete in 5th place. 527 open bugs.
Will Stephenson/wstephenson says kopete is "even more understaffed than PIM"
And says I can quote him on that along with pointing out that working on
kopete seems to be the surefire way to get hired (suse, mandriva, tt,
canonical).

Anyway, I figure kopete is good because its a popular app, and has fans a la
amarok.

Also, W.S. asks for some experienced triage on systemsettings, as while there
are only 133 open bugs in it, many of the bugs are misassigned. 
eg file associations bugs are probably in kdelibs/kdeui
If you have to bug people on #kde-devel for help, you should probably feel
free, as apparently some of these are tricky to sort.


And thanks to everyone that helped in the last few, because you're really cool.
We've made Seli a little nervous now. We've knocked him off several times, and
currently he's fighting for #10. With the incoming bugs, we really shouldn't
have a problem keeping him off the commit digest. ;) At least, I'm assuming
they're all fixed bugs. ;)

Alex

p.s. if you want to learn about a certain module, you can always pick a person
and follow all their bugs. You can use this to see how they tend to handle 
them, in addition to searching for what they've done. Its under preferences.