On 10/26/07, Valerie Bubb Fenwick <[EMAIL PROTECTED]> wrote: > Obviously someone needs to be looking after the community, or the > bugs will be entering a black hole.
I'm working on trying to recover another project from this black hole, I know Sun is much less at risk from this than we are, but it can happen (and believe me you don't want to go there). I wrote: > 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. On 10/26/07, Valerie Bubb Fenwick <[EMAIL PROTECTED]> wrote: > No data, but there are nearly daily requests. Sometimes more. I'm partly trying to understand how much time is devoted to this work, and whether we're trying to streamline it or just reproduce it (I don't mind either way, since you seem comfortable with it). > Lots of changes, like changing RM (responsible manager) or > IE (initial evaluator) do not require approval, but I see the changes. Interesting, is this a useful feature (it's essentially a form of logging), are there times when you've needed to react to this? > So, I'd say in solaris we probably see at least one category or > subcategory change about 5 times a week. Wow, would it help if categories could have people responsible for making changes within their category (and not capable of making such changes outside)? Or are you relying on yourself to make sure the overall bigger picture is maintained? (Bugzilla 3 allows for perproduct editcomponents, <http://www.bugzilla.org/releases/3.0/new-features.html#v30_feat_ppp>) ... A couple of notes about using watchable entities. First the ones that don't require authorization/administrative interaction: * anyone can add a watch (note: watching a person doesn't give you access to mail you wouldn't be able to get on your own, it just gives you the opportunity had you been able to get the mail) * anyone can stop watching someone * If the watched account is a real person, the account can see who is watching it * if the watched account is not a real person, there are ways for people to recognize who is watching it (they're unfortunately spammy since you create a new bug and restrict all the fields to you+it, which leaves the db w/ an extra bug). Things an administrator could do (this is IMO the "correct" way) - it generates log mail to the account indicating who did the impersonating and the reason they gave. Impersonate users to add watches - if for some incomprehensible reason the watcher refuses to use Bugzilla directly Impersonate users to view who is watching them It's probably worth considering adding a feature to the describecomponents.cgi view to show who is watching the listed accounts. As I've indicated above, watching/being watched is not really private, and accounts that are default assignee/qa contacts are essentially very "unprivate". If people think this is worthwhile, I can see about upstreaming this idea. > 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. _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
