launchpad-dev team mailing list archive

[curtis Hovey <curtis.hovey@xxxxxxxxxxxxx>]

On 10/05/2011 09:24 AM, Gary Poster wrote:
> Wow.  That's a freaking lot of tags. :-)  Are they really all useful?
>
> I missed that wiki page list entirely. I knew we had a bunch, but I didn't regard them all as a triaging responsibility.  For myself, I'm certainly guilty of not using these.  I try to use oops, regression, ui, and maybe occasionally javascript, chr, and api.  If I notice that something is in soyuz, I might try typing "soyuz" in the tagger and see if something vaguely useful pops up.
>
> I suspect that we will get better tagging if we can expect someone to actually hold the valuable tags in their brain at once, or at least hold prefixes in their brain with tag completion to help out with the rest.  Moreover, I won't know in all cases what applies.  A random example of many is "package-diff: A bug affecting the PackageDiff soyuz subsystem".  I don't know that subsystem.
>
> To make this not merely a complaint :-P , I'll try for a straw man clean-up proposal.
>
> 0) The changes I propose below are for the tags we expect LP-dev bug filers and CHR triagers to actually use.  When I propose eliminating tags, I mean from this list.  We can certainly have other tags, maintained by people that love them.
>
> 1) We eliminate old or rarely used tags from this list.  I have a hunch that this group might include tags like "tour," "bounty-tracker," "codeofconduct," "team-voting," and more.  Similarly, does tagging "tech-debt" actually provide any searchable value?
>
> 2) We agree on a very few tags or tag prefixes.  I propose that the tags are "oops," "regression," "timeout," "ui," "javascript," "infrastructure," (folding in build-infrastructure) "email," and "api".  Prefixes include "translations-," "bugs-," "code-," "soyuz-," "teams-", "projects-", "users-".
>
> 3) Prefixes are available individually for people who know "that's soyuz, but that's all I can tell you".
Prefixes are unneeded, search support all or any tags. I tag bugs along
two axis. I first tag the bug to describe the affect objects (teams,
bugs, mirrors projects codereviews). I then tag the interaction (api,
ui, email, tech-debt). Some bugs get extra tags to describe scope
(trivial for fixable in an hour or easy for a day)

Every day I view Lp's bug sorted from newest to oldest, and I tag the
bugs that recognise.

-- 
Curtis Hovey
http://launchpad.net/~sinzui

Attachment: signature.asc
Description: OpenPGP digital signature