So, here's the summary.
There should be "user tags" which allows users to tag bugs however they see fit, without bothering anyone else. Maintainers shouldn't get mailed, and the default view shouldn't include any user tags. You should be able to select on user tags, and filter on them. Each user tag should be associated with an individual, probably by an email address.
Choosing which tags you're viewing should be doable from the CGIs (obviously).
Having this at the bottom of pkgreport.cgi should work:
- [x] azure.humbug.org.au (sent-a-patch, affects-me, affects-pkg-of-mine)
- [x] women.debian.org (easy, hard, lang-c, lang-python, ...)
[_] ___________________________
Also needs a button to commit changes. Adding multiple collections can be done by space separating.
Usertags should be modified by control@
It would be interesting for modifications to usertags to be cc'ed to the email address or similar.
It might be useful to be able to include abbreviations/aliases for email addresses, but it's not clear how that'd work.
Not using actual email addresses would probably be a win, but what to use instead isn't clear. Maybe just hostnames would work? (azure.humbug.org.au, qa.debian.org, women.alioth.debian.org, etc). Using *.hostname is probably best, with the premise being "only add the * bit if you aren't going to hand that out as a subdomain to someone else".
This has been announced, and there's some discussion of usage and missing features.
It might be a good idea to limit the categories to being 10 chars or more ("debian.org" is 10) to stop people being pathetic about trying to get short names.
Followup
- Documentation. Done (more or less)
- Limit tags so people don't use underscores and find they don't work. Done.
- Include @packages.debian.org usertags by default. Done.
Make the pkgreport.cgi code not be butt ugly. Too hard
- Make it possible to set usertags when submitting a bug
All the rest seems to be categorisation work. Leet!