From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-dev+bounces-39640-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1NmGyp-0005zw-My
for garchives@archives.gentoo.org; Tue, 02 Mar 2010 01:33:00 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 9511DE0C38;
Tue, 2 Mar 2010 01:32:56 +0000 (UTC)
Received: from mail-pw0-f53.google.com (mail-pw0-f53.google.com [209.85.160.53])
by pigeon.gentoo.org (Postfix) with ESMTP id A3E40E0B82
for <gentoo-dev@lists.gentoo.org>; Tue, 2 Mar 2010 01:32:46 +0000 (UTC)
Received: by pwi2 with SMTP id 2so1885013pwi.40
for <gentoo-dev@lists.gentoo.org>; Mon, 01 Mar 2010 17:32:46 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Sender: antarus@scriptkitty.com
Received: by 10.141.23.19 with SMTP id a19mr2939995rvj.22.1267493565675; Mon,
01 Mar 2010 17:32:45 -0800 (PST)
In-Reply-To: <pan.2010.03.02.01.09.14@cox.net>
References: <4B889D1F.3040304@gentoo.org>
<201002282154.35130.hwoarang@gentoo.org> <4B8ACC34.7000600@gentoo.org>
<20100228173504.78eea0b1@angelstorm>
<ea440b1d1003011317j24a550b2id2653d8061757c94@mail.gmail.com>
<e117dbb91003011419if3b25fnef03dc6c0e86e69d@mail.gmail.com>
<ea440b1d1003011426hdc97dc4p55666fa51f34bcee@mail.gmail.com>
<20100302010205.18765d7s0e4x781s@webmail.df.eu>
<pan.2010.03.02.01.09.14@cox.net>
Date: Mon, 1 Mar 2010 17:32:45 -0800
X-Google-Sender-Auth: 54573e9f222f00fc
Message-ID: <b41005391003011732p14a3a6d2q3290f573eef39e55@mail.gmail.com>
Subject: Re: [gentoo-dev] Re: Marking bugs for bugday?
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 68a98655-1e0b-45c4-8ab7-f39c8dbc5e58
X-Archives-Hash: 4a97a9e131233b31ee21967aca5fa619
On Mon, Mar 1, 2010 at 5:09 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> Sebastian Pipping posted on Tue, 02 Mar 2010 01:02:05 +0100 as excerpted:
>
>> Quoting Ioannis Aslanidis <aslanidis@gmail.com>:
>>> I would prefer to keep the keyword for Bugday Members to administer.
>>
>> I don't think that sending mails would work well. If you want extra
>> control/QA for bugday team members I would propose two different
>> keywords: one for bugday candidates and one for confirmed bugday bugs.
>>
>> Any dev could mark bugs as candidates easily and without delays while
>> you could still reserve acknoledgement to you.
>
> ... And here I'm proposing three:
>
> BUGDAY =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(nomination)
> BUGDAY-ACCEPTED (or whatever is thought appropriate)
> NOBUGDAY =C2=A0 =C2=A0 =C2=A0 =C2=A0(or BUGDAY-DECLINED, or BUGDAY-REFUSE=
D, or...)
I think the last one is over-engineering a bit; bugzilla keywords are
not permanent so this will likely not help as much as one may think in
practice. Old bugday keywords are visible in the activity trail.
-A
>
> The latter would be for nominated bugs that were declined as inappropriat=
e
> for whatever reason, to help prevent them being nominated again.
> Presumably there'd be a comment added explaining why as well, but the
> keyword would be what shows up in someone's face if they're thinking abou=
t
> keywording it BUGDAY.
>
> --
> Duncan - List replies preferred. =C2=A0 No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master." =C2=A0Richard Stallman
>
>
>