On Fri, 2005-09-16 at 10:55 +0900, Horms wrote: > On Thu, Sep 15, 2005 at 12:30:33PM -0700, Matt Taggart wrote: > > > > dann frazier writes... > > > > > On Thu, 2005-09-15 at 18:19 +0900, Horms wrote: > > > > I'm thinging that if the use of the BTS is really to allow > > > > users to track all problems in a package, its probably > > > > useful to have a separate, but linked BTS, that allows > > > > the maintainers to track what they are actually working on. > > > > > > Have you looked at user tags for that? I haven't yet, but Matt Taggart > > > has been using something like that for a while now to track lsb issues. > > > > That thing I had been using for a last couple years was an LSB > > specific hacked cgi script that AJ provided. It has been replaced by > > the new generic user tags stuff that AJ announced on d-d-a recently. > > It should do exactly what you want. I recommend setting up a general > > namespace for "[email protected]" that various people > > edit and also each developer could have their own which maybe the wiki > > could have pointers to. Then people would have an easy way to see the > > different views of the world. > > That sounds like an excellent idea. We already make some use > of the wiki to note policy about patches, the status of > updates, and stuff like that. So that seems like a good place to put > this.
Agreed. > Perhaps kernel-team, or dkt, as a space for the team, > then suffix details after that. I'm not sure that we need > per-user stuff for members of the team, but that could easily be added. > Is something like this appropriate > > dkt-unimplemented > dkt-work-in-progress-upstram > dkt-work-in-progress > dkt-backport-is-too-damn-hard-update-to-newer-version Your tag names sound good, though we should have some definitions to go along with them. For the work-in-progress type, we could also use the "owner" tag to specify the person working on it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
