From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.90.117.16 with SMTP id p16cs466662agc;
        Mon, 2 Nov 2009 07:09:44 -0800 (PST)
Received: by 10.224.102.84 with SMTP id f20mr2838308qao.224.1257174584394;
        Mon, 02 Nov 2009 07:09:44 -0800 (PST)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 13si7770856qyk.131.2009.11.02.07.09.44;
        Mon, 02 Nov 2009 07:09:44 -0800 (PST)
Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 05FF61598078;
	Mon,  2 Nov 2009 10:09:43 -0500 (EST)
Received: from entry.masanjin.net (masanjin.net [209.20.72.13])
	by rubyforge.org (Postfix) with ESMTP id 4EB0E1858292
	for <sup-talk@rubyforge.org>; Mon,  2 Nov 2009 10:08:48 -0500 (EST)
Received: from w by entry.masanjin.net with local (Exim 4.69)
	(envelope-from <w@masanjin.net>) id 1N4yWW-0001JK-1g
	for sup-talk@rubyforge.org; Mon, 02 Nov 2009 07:08:48 -0800
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
In-reply-to: <1257146404-sup-9768@tilus.net>
References: <1256749942-sup-4831@arrakis.es.net> <1256760295-sup-9873@peray>
	<1256760970-sup-8118@arrakis.es.net>
	<1256939476-sup-2864@masanjin.net> <1256987483-sup-338@tilus.net>
	<1257086191-sup-1136@masanjin.net> <1257146404-sup-9768@tilus.net>
Date: Mon, 02 Nov 2009 07:08:48 -0800
Message-Id: <1257174456-sup-5631@masanjin.net>
User-Agent: Sup/git
Subject: Re: [sup-talk] Sup Issues Task Force (SITF)
X-BeenThere: sup-talk@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-talk-bounces@rubyforge.org
Errors-To: sup-talk-bounces@rubyforge.org

Reformatted excerpts from Tero Tilus's message of 2009-11-01:
> How about SITF responsible of the boring suff
>  - First line processing of inbound issues (relevance, duplication, ...)
>  - Issue overview
>    - Supervise that fixed/handled issues get closed appropriately
>    - Draw attention to triaged "bad" bugs
> 
> I'm in.  Who else?

That sounds great. I think it needs to be combined with some kind of
formal issue tracker though.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk