Received: from spf5.us4.outblaze.com (spf5.us4.outblaze.com [205.158.62.27])
	by sdf.lonestar.org (8.13.1/8.12.10) with ESMTP id j17Ip91Z026347
	for <migo@freeshell.org>; Mon, 7 Feb 2005 18:51:09 GMT
Received: from hera.museatech.net (unknown [207.166.200.220])
	by spf5.us4.outblaze.com (Postfix) with SMTP id 99A5777061
	for <migo@homemail.com>; Mon,  7 Feb 2005 18:51:57 +0000 (GMT)
Received: (qmail 6077 invoked by uid 110); 7 Feb 2005 18:51:52 -0000
Received: from gnu-arch-dev-bounces@lists.seyza.com by hera by uid 102 with qmail-scanner-1.20 
 (clamscan: 0.60. spamassassin: 2.60.  Clear:RC:1(127.0.0.1):. 
 Processed in 1.917785 secs); 07 Feb 2005 18:51:52 -0000
Received: from unknown (HELO hera.museatech.net) (127.0.0.1)
  by hera.museatech.net with SMTP; 7 Feb 2005 18:51:50 -0000
Delivered-To: list-gnu-arch-dev@lists.seyza.com
Received: (qmail 5992 invoked by uid 110); 7 Feb 2005 18:51:42 -0000
Received: from lord@emf.net by hera by uid 102 with qmail-scanner-1.20 
	(clamscan: 0.60. spamassassin: 2.60.  Clear:RC:1(207.166.200.201):. 
	Processed in 2.07182 secs); 07 Feb 2005 18:51:42 -0000
Received: from unknown (HELO a1.mx.alal.us) (207.166.200.201)
	by hera.museatech.net with SMTP; 7 Feb 2005 18:51:39 -0000
Received: (qmail 21435 invoked from network); 7 Feb 2005 20:04:58 -0000
Received: from emf.emf.net (HELO emf.net) (205.149.0.20)
	by a1.mx.alal.us with SMTP; 7 Feb 2005 20:04:55 -0000
Received: (from lord@localhost) by emf.net (K/K) id KAA08819;
	Mon, 7 Feb 2005 10:51:37 -0800 (PST)
Date: Mon, 7 Feb 2005 10:51:37 -0800 (PST)
From: Tom Lord <lord@emf.net>
Message-Id: <200502071851.KAA08819@emf.net>
To: gnu-arch-users@gnu.org, gnu-arch-dev@lists.seyza.com
In-reply-to: <200502071824.KAA07782@emf.net> (lord)
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dev.alal.com
X-Spam-Level: 
X-Spam-Status: No, score=-1.6 required=9.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Cc: 
Subject: [GNU-arch-dev] Re: a note about bug czar bandwidth
X-BeenThere: gnu-arch-dev@lists.seyza.com
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: a mailing list for GNU Arch developers <gnu-arch-dev.lists.seyza.com>
List-Unsubscribe: <http://lists.seyza.com/cgi-bin/mailman/listinfo/gnu-arch-dev>, 
	<mailto:gnu-arch-dev-request@lists.seyza.com?subject=unsubscribe>
List-Archive: <http://hera.museatech.net/pipermail/gnu-arch-dev>
List-Post: <mailto:gnu-arch-dev@lists.seyza.com>
List-Help: <mailto:gnu-arch-dev-request@lists.seyza.com?subject=help>
List-Subscribe: <http://lists.seyza.com/cgi-bin/mailman/listinfo/gnu-arch-dev>, 
	<mailto:gnu-arch-dev-request@lists.seyza.com?subject=subscribe>
Sender: gnu-arch-dev-bounces@lists.seyza.com
Errors-To: gnu-arch-dev-bounces@lists.seyza.com
Status: RO
Content-Length: 883
Lines: 29


Oh, and, btw:

   Date: Mon, 7 Feb 2005 10:24:02 -0800 (PST)
   From: Tom Lord <lord>

   Regardless, the bug czar is not intended to be online 24 hours a day -- 
   not even close.

   One to three hours, 5 business days per week, strikes me as about right.


I don't mean that I expect a volume of incoming reports that would fill
that time just entering them, either.   A secondary role for bug czar
hours is a kind of "ombudsman" role, following up on open bugs,
keeping progress going forward, etc.

Another component that "would be nice" to add to the mix here
is "office hours" --- support hours when a core GNU Arch hacker
is certain to be around on IRC or some such.   But that's a whole
separate RFCV.

-t

_______________________________________________
Gnu-arch-dev mailing list
Gnu-arch-dev@lists.seyza.com
http://lists.seyza.com/cgi-bin/mailman/listinfo/gnu-arch-dev