From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs443479agc; Sun, 1 Nov 2009 23:16:51 -0800 (PST) Received: by 10.224.123.103 with SMTP id o39mr2701640qar.93.1257146211181; Sun, 01 Nov 2009 23:16:51 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 16si6832004qyk.83.2009.11.01.23.16.50; Sun, 01 Nov 2009 23:16:51 -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 BAD9618582CA; Mon, 2 Nov 2009 02:16:50 -0500 (EST) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 7D84E18582AC for ; Mon, 2 Nov 2009 02:01:32 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id B10426011; Mon, 2 Nov 2009 07:01:31 +0000 (GMT) From: Tero Tilus To: sup-talk In-reply-to: <1257111816-sup-4397@peray> References: <1257111816-sup-4397@peray> Date: Mon, 02 Nov 2009 09:01:31 +0200 Message-Id: <1257143690-sup-7839@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 Requirements collected: - Store/track - Formal attributes: Issue type, severity, priority, category, person assigned, progress status, incriminated version and platform, planned milestone/released - Informal meta: Issue details, discussion, answers, attachments - Web-interface (at least for issue submission, searching and displaying) - Issue submission, commenting, attachments and editing attributes by email - Notifications by email Nicolas Pouillard, 2009-11-01 23:52: > OK lets forget Ditz[2] as an option. Why? (not that i have any reason why not, i've never used diz) > Note also that I would make no objection to using a traditional bug > tracker. > > It seems that we do not find a tool we really like. Looks like this is a issue you have discussed in depth before. Any pointers to list archives? > A simple question I asked me was: > "Do we really need to invent this (big) tool?" Well... if somebody invented it for us already. :) > Especially for a bug tracker we need recipes, protocols more than a > nice interface. Now we are talking! ...and when trying to choose a tool, we need to think about what we need it to do for us. I tried to pick the requirements you used. > So we need a web interface for non technical users, great. OK, this seems reasonable requirement. > What about a pre-formatted email explained on a single web-page for > reporting bugs. ... > A bot will receive emails on the mailing-list and process those > which are in the right format. Requirement: Bug submission by email? I'd say we need that. > I think that the bot will not have a lot of information to store: > > (correct me if you find something else) > > * Issue type, severity, priority, category, person assigned, > progress status, incriminated version and platform, planned > milestone/released. > > * Issue details, discussion, answers, attachments. This is pretty traditional. I'd still want to challenge a bit. Why do we need severity and priority? What would they be used for? > I would store and manage the first category using a simple YAML > file. The bot acknowledges its updates by simply answering to the > discussion. Requirement: Email notifications to ticket "subscribers"? That's reasonable. > Those of the second category can be managed using a single email > discussion. Requirement: Issue comments/attachments and status changes by email? > I don't know yet how many issues I've forgotten I can't figure out anything really necessary you would have missed. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk