From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs449386agc; Mon, 2 Nov 2009 01:50:41 -0800 (PST) Received: by 10.224.20.144 with SMTP id f16mr2735895qab.220.1257155441172; Mon, 02 Nov 2009 01:50:41 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 26si6937017qyk.4.2009.11.02.01.50.41; Mon, 02 Nov 2009 01:50:41 -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 C44E716782B6; Mon, 2 Nov 2009 04:50:40 -0500 (EST) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 305E118582C7 for ; Mon, 2 Nov 2009 04:50:07 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id 1E2BE6011; Mon, 2 Nov 2009 09:50:07 +0000 (GMT) From: Tero Tilus To: sup-talk In-reply-to: <1257150627-sup-1843@peray> References: <1257111816-sup-4397@peray> <1257143690-sup-7839@tilus.net> <1257150627-sup-1843@peray> Date: Mon, 02 Nov 2009 11:50:07 +0200 Message-Id: <1257154664-sup-90@tilus.net> User-Agent: Sup/git Subject: Re: [sup-talk] Choosing a bug tracker for Sup X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Nicolas Pouillard, 2009-11-02 10:46: > Excerpts from Tero Tilus's message of Mon Nov 02 08:01:31 +0100 2009: >>> "Do we really need to invent this (big) tool?" >> >> Well... if somebody invented it for us already. :) > > Yes but a big tool imply development, extensions, upgrades... Unless you take service, not the bare tool. We are already using gitorius and rubyforge (at least to some extent). I'd go for a issue tracking service that suits our needs. >> Requirement: Email notifications to ticket "subscribers"? >> That's reasonable. > > I would say that the mailing-list is the only subscriber, people > choose to follow the discussion or not with their email-client. Thats exactly why there were quotes around the word subscribers. ;) What I was thinking was that you could be a first class citized no matter the client. You could choose to comment and follow the discussion on issues using your mua or web interface. Kinda like what Alue[1] does for discussions in general. [1] http://antti-juhani.kaijanaho.fi/newblog/archives/572 -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk