Comment 5 for bug 827178

> Also, I assumed practice would be to subscribe someone and ask a question directly. Is this not the case? If it is, how is this breaking down due to large numbers of bugs. I know I get my mail differently when directly subscribed. But I do recognize that I don't get the same volume of mail as Ubuntu devs.

It certainly is possible to set up mail filter rules to promote subscription bugs, but this assumes the person in question has taken the time to set it up; often they haven't, and so the subscription emails end up in their general launchpad email pool (which in Ubuntu's case can be rather large.) So it doesn't seem to work reliably in practice.

The established practice in Ubuntu now is rather than subscription, to assign to the appropriate Canonical team. This puts the bug on that team's weekly agenda to review and assign out accordingly. This seems to work quite reliably in practice. But it's not intuitively obvious as a regular reporter that this is what you're supposed to do.

Ursula's right that this is a clumsy process.

It seems that subscription is used for three purposes: a) bugs that affect me, b) bugs I want to bookmark to follow, and c) bugs someone needs my input on. Perhaps rethinking how these three different cases are handled would be worthwhile?