Ha ha, I have a user page now. And it's a mess.
Pages I use all the time
Bugsquad top level pages
List of people in bugsquad, nonofficial & incomplete.
Pages to move out of userspace
How to triage bugs.
cf User:Grundleborg's version
Annoying bugs so I can find them again
- kio_http ipv6 dns bug: 
- these 2 bugs together are evil^10!! they gave me testing pleasure for about 10 hours :( katastrophe 22:48, 17 June 2008 (CEST)
- poor katastrophe! Note to onlookers: these tend to be reported to the konq component
- konqueror crashes on close: 
(I just actually want the testcase here.)
- makes Der Spiegel unreadable :P (gwenview bug) 
- flash on kde4 messed up because of qt3's gtk engine 
- Quote Pinotree: The reason is simple: do *NOT* use gtk-qt-engine for gtk. Otherwise, your konqueror4 will load the flash plugin, that in turns uses gtk, that in turns loads Qt3 (because of gtk-qt), and the imcompatibility between Qt3 and Qt4 will do the rest. (He closed it as invalid. [Is] a dup.)
Pino's very short triage intro: "pre-filter" or "how to do incoming triage"
- Look at the new bugs, and sort them out (invalid, or reassign them, or marking as dupe if it is, etc)
- Use the "New reports since 3 days" link on your bugs.k.o homepage. That's the start point, or read kde-bugs-dist via www.gmane.org which is: http://news.gmane.org/gmane.comp.kde.devel.bugs
Pages to look at
Bugs I should file/testcase