Proposal: assign people to specific jobs

[t u]

Vassilis Pandis wrote:
> --- t u <towsonu2003 at gmail.com> wrote:
> 
> 
>> a sub-team of bugsquad that only assigns bugs to packages [no other
>> triaging task involved] might work. the job of this squad would be to
>> triage incoming (new) as well as old bugs without specified packages
>> only to packages. it's fairly easy and works nice because package
>> developers get feedback on bugs in a more efficient way. For example, a
>> couple of bugs for which I only did this got their way up to 6.10
>> milestone.
>>
> 
> I can see your point with the unassigned packages. Is an entire team neccessary
> though? What about a hug day with only this target in mind, to clear up the backlog
> that has been created. After it's over, let's just try to put bugs where they
> belong (and if neccessary hold a similar hug day in a few months' time).
> 
well, as the sub-team will be voluntary, we can see how participation
goes for a year-long review period.

the backlog seems to be too much. this link
https://launchpad.net/distros/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=Unconfirmed&assignee_option=any&field.assignee=&field.owner=&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_no_package.used=&field.has_no_package=on&search=Search
shows 1746 bugs for only unconfirmed ones. also, I expect that we are
getting many no-package-specified bugs (we have a newbie user base) by
the minute (exageration). It would be nice to have a team (I expect to
have only 4-5 people sign up to such a team) that processes those bugs
as they come, as fast as possible.

just to clarify myself, this should be a sub-team. so anyone who is a
member of that team will be a member of bugsquad, hence will do other
bug work as well. but they will have in mind a primary goal: no
no-package-bugs.

all this team should need is a wiki page of "common cases". no email
list etc is necessary as they can communicate via bugsquad email list
-why not, we don't get much email anyway? or maybe I'm wrong-. chatroom
isn't necessary either.

this team would also be a great place for absolute newbies (me!
ehueheh). all you need to know is which package is causing the bad
behavior.