package-based bug weeks -- proposal

[Henrik Nilsen Omma]

Hello Bugsquad!

This is my first post on the list so I should probably introduce myself! 
I'm the token non-developer on the Ubuntu dev team. I mainly look after 
things like the accessibility tools and the WinFOSS collection. But, I 
also have an interest in bugs!

I'd like to propose a new kind of bug week, one focusing on a single 
package.

This would be cool because:

* It lets us focus on a limited section of the bug mountain and work 
more tightly as a team on it

* Before and during that week we would all build up some expertise 
regarding that particular package and so we can help each other do 
quality triaging

* I know we've had single bug days dedicated to individual packages, but 
IMO these are too short for the whole team to build up serious expertise 
on the package. With a full bug week we'll all be experts by the end!

* But most importantly: We'll be able to make a real dent in the 
untriaged bug count of an individual package, which is more satisfying 
psychologically than making a tiny dent in the overall 20.000 open bug count

* This will give the bugsquad something new to blog about each week. It 
could be posted on the Fridge and in the forums, all helping to raise 
bug awareness and recruit more people to the team.


How it would work:

* Every week would be bug week! -- focusing on a new package each time. 
It doesn't have to be as intense as the bug days. The stretched out week 
gives everyone a chance to participate and get up to speed

* 10-14 days before the start of a bug week members of the bugsquad 
would propose a package on this list for special attention and we would 
together (by consensus or vote) pick one for the week after next. 
Packages with high open bug counts are obvious candidates, but other 
factors may also be important.

* The person who proposed the winning package gets a special prize! They 
get a chance to produce a triaging guide for that particular package, 
with examples of common duplicates, stock reply phrases, etc. They have 
about a week to do that. As we get into a pattern we'll have a new 
bugweek with a new topic each week, prepared by someone the week before.

* When the week starts the rest of us will start by reading the howto 
and jump into the sea of bugs for that package!

* As we learn about the intricacies of that one package we can help each 
other do high quality triaging and in the process we all learn better 
techniques.

* We all help improve the triaging guide for the package as we go along, 
ending up with a solid guide for future triagers for all the major packages

* We should invite the package maintainer to first have a look at the 
howto before the week starts to give additional pointers and ideally be 
available during the week to give expert guidance


Workable?

Henrik