Patrick Lauer posted on Sat, 06 Feb 2016 09:09:13 +0100 as excerpted:
> Maybe we could add a "Assign to maintainer(s)" button visible only to
> certain groups of users, so that a bugwrangler who decides this bug is
> valid just has to hit one button instead of figuring out the details of
> assignment?
>
> There seems to be valid criticism about fully automating the workflow,
> but partial automation can still save huge amounts of time ...
Talking about which, I've toyed with asking for bug-assignment privileges
for awhile, but haven't known who to ask, or if the privilege model is
fine grained enough to give me that without giving me stuff I probably
shouldn't have.
Such a button that could be made available to selected users, or even in
general, since we already trust users with setting CC, adding archs, and
even (controversially) with setting importance. Arguably, even making
this button available to all users would be but a small extension from
that.
Meanwhile, lately I've started ccing the maintainer, based on equery
meta's results for the package. So far for this try I've had good
results and faster bug resolution as I effectively bypassed wrangling,
but awhile back I tried that on a bug and when wranglers did assign, they
didn't take the CC out so the dev was getting two notices on changes and
was a bit cranky about that. So I make it a point to mention the CC now,
so hopefully if a wrangler gets to it before the CCed dev, they can unCC
at the same time they assign.
Too bad most of the components aren't fine grained enough to do direct
assignment, as they do for kde and (IIRC) portage bugs, for instance. I
always thought gentoo's bz organization there was buggy, as it made a lot
more sense to me to have say applications or libraries at the product
level, and the cat/pkg at the component level, or even category as the
product and package as the component. But it was already too late to
change that when I became a gentooer in 2004, let alone now.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
