| 1 |
Sebastian Pipping posted on Tue, 02 Mar 2010 01:02:05 +0100 as excerpted: |
| 2 |
|
| 3 |
> Quoting Ioannis Aslanidis <aslanidis@×××××.com>: |
| 4 |
>> I would prefer to keep the keyword for Bugday Members to administer. |
| 5 |
> |
| 6 |
> I don't think that sending mails would work well. If you want extra |
| 7 |
> control/QA for bugday team members I would propose two different |
| 8 |
> keywords: one for bugday candidates and one for confirmed bugday bugs. |
| 9 |
> |
| 10 |
> Any dev could mark bugs as candidates easily and without delays while |
| 11 |
> you could still reserve acknoledgement to you. |
| 12 |
|
| 13 |
... And here I'm proposing three: |
| 14 |
|
| 15 |
BUGDAY (nomination) |
| 16 |
BUGDAY-ACCEPTED (or whatever is thought appropriate) |
| 17 |
NOBUGDAY (or BUGDAY-DECLINED, or BUGDAY-REFUSED, or...) |
| 18 |
|
| 19 |
The latter would be for nominated bugs that were declined as inappropriate |
| 20 |
for whatever reason, to help prevent them being nominated again. |
| 21 |
Presumably there'd be a comment added explaining why as well, but the |
| 22 |
keyword would be what shows up in someone's face if they're thinking about |
| 23 |
keywording it BUGDAY. |
| 24 |
|
| 25 |
-- |
| 26 |
Duncan - List replies preferred. No HTML msgs. |
| 27 |
"Every nonfree program has a lord, a master -- |
| 28 |
and if you use the program, he is your master." Richard Stallman |
Archives