| 1 |
Jim Ramsay <lack@g.o> posted 20080701112956.143dbd22@vrm378-02, |
| 2 |
excerpted below, on Tue, 01 Jul 2008 11:29:56 -0400: |
| 3 |
|
| 4 |
> Mark Loeser <halcy0n@g.o> wrote: |
| 5 |
>> Its a good idea, but since our users don't always provide useful |
| 6 |
>> reports, it seems like we are just shifting work around. |
| 7 |
> |
| 8 |
> I'd suggest that this would /spread/ work around - Instead of a few |
| 9 |
> folks wrangling bugs, everyone would be doing it. |
| 10 |
> |
| 11 |
> That said, I have no idea how many duplicate / incomplete bugs I have |
| 12 |
> never seen due to the wonderful work of the wranglers. In some ways it |
| 13 |
> would be a shame to lose that quality pre-reading of the bugs. |
| 14 |
|
| 15 |
Perhaps the best solution is to get the implementation in place, but not |
| 16 |
completely automate it. Put the tools there so if it looks right, all |
| 17 |
the wrangler needs to do is a single click, and it's auto-assigned, but |
| 18 |
that single click is still necessary so that a human actually gets to |
| 19 |
review things before doing the assignment. |
| 20 |
|
| 21 |
That would make it /much/ easier for the wranglers. |
| 22 |
|
| 23 |
If desired, a cron script or some such could then be setup to go thru and |
| 24 |
automatically assign anything that wasn't assigned yet and that hadn't |
| 25 |
been touched (no comments asking for more info, etc) for some period, say |
| 26 |
a week, just to catch anything that fell thru the cracks or if the |
| 27 |
wranglers all disappeared or went on strike/vacation/whatever. Then if |
| 28 |
folks ever suddenly find themselves inundated with "raw" bugs, it'd be a |
| 29 |
serious indication that the wranglers needed some help. |
| 30 |
|
| 31 |
-- |
| 32 |
Duncan - List replies preferred. No HTML msgs. |
| 33 |
"Every nonfree program has a lord, a master -- |
| 34 |
and if you use the program, he is your master." Richard Stallman |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@l.g.o mailing list |
Archives