On Thu, 25 Oct 2007, timeless wrote: > 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.
Obviously someone needs to be looking after the community, or the bugs will be entering a black hole. > 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? No data, but there are nearly daily requests. Sometimes more. Lots of changes, like changing RM (responsible manager) or IE (initial evaluator) do not require approval, but I see the changes. So, I'd say in solaris we probably see at least one category or subcategory change about 5 times a week. > 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) WE try to do that for bugster internally. For example, if it's not actually delivered in solaris, we don't want the bugs tracked under solaris. :-) We do try to only accept new cat/subcategories that make sense for a submitter. There's lots of confusing stuff in there - the data itself has grown over about 15 years (maybe more?). So, all things considered, it's not too bad. Valerie -- Valerie Fenwick, http://blogs.sun.com/bubbva Solaris Security Technologies, Developer, Sun Microsystems, Inc. 17 Network Circle, Menlo Park, CA, 94025. 650-786-0461 _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
