On Wed, 24 Oct 2007 22:05:52 -0400 Bill Sommerfeld <[EMAIL PROTECTED]> wrote: > while it's a stretch, how about "responsible community" as a strawman > analog for RM.
On 10/25/07, Max Kanat-Alexander <[EMAIL PROTECTED]> wrote: > From my experience, that doesn't work. You have to have a > person designated. If there's no person, it can fall back on the person > designated to manage the product. I hate being seen as simply agreeing with people, but it's true, either there's a person, or there isn't. In terms of making changes to a product, you can have a group which can edit the product and assign members to the group, but you still want a real person who is generally expected to do the work. It's ok to have a couple of alternates who will do it if they notice a need (i.e., they will get to it sooner if their load is lighter.), but you really need a person who is responsible for the task. Note that in the Bugzilla's with which I work, the QA field is just a watchable entity, but that's different from claiming the entity is responsible for anything, in fact it's about as close as saying that no one in particular is responsible for it. For external projects isn't there a voucher? or does that come later? Valerie: do you happen to have numbers showing how often do you need to add/change/remove categories? It sounds like each major category has its own rules, and a hint about where related things should go if "not here". Assuming a category is mapped to a Product, this could be done by adding a second paragraph to the Product's description indicating what does belong in it and which other Products to see for other related things. (Trying to make things self documenting, both for people who add items and for reporters trying to decide where to file them) To see these descriptions, try using these urls instead of the normal enter_bug link: http://defect.opensolaris.org/bz/enter_bug.cgi?format=guided http://defect.opensolaris.org/bz/enter_bug.cgi?classification=Unclassified&format=guided _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
