Re: [sup-talk] Choosing a bug tracker for Sup

From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Mon, 02 Nov 2009 11:50:07 +0200	[thread overview]
Message-ID: <1257154664-sup-90@tilus.net> (raw)
In-Reply-To: <1257150627-sup-1843@peray>

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