From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: Bug tracking (was: new *Help* argument highlighting) Date: 12 Jun 2004 16:01:15 -0500 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87wu2ca3tw.fsf@floss.red-bean.com> References: <20040512103042.FB57.JMBARRANQUERO@wke.es> <20040611122633.5F88.JMBARRANQUERO@wke.es> <87659wd44u.fsf@floss.red-bean.com> <87659wbl2q.fsf@floss.red-bean.com> <20040613023944.GA13072@fencepost> Reply-To: kfogel@red-bean.com NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1087096719 14533 80.91.224.253 (13 Jun 2004 03:18:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 13 Jun 2004 03:18:39 +0000 (UTC) Cc: Juanma Barranquero , rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Jun 13 05:18:31 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZLVv-00061b-00 for ; Sun, 13 Jun 2004 05:18:31 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZLVv-00023X-00 for ; Sun, 13 Jun 2004 05:18:31 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZLWk-0006aG-B9 for emacs-devel@quimby.gnus.org; Sat, 12 Jun 2004 23:19:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BZLWh-0006a6-9g for emacs-devel@gnu.org; Sat, 12 Jun 2004 23:19:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BZLWg-0006Zl-Cn for emacs-devel@gnu.org; Sat, 12 Jun 2004 23:19:18 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZLWg-0006Zb-8M for emacs-devel@gnu.org; Sat, 12 Jun 2004 23:19:18 -0400 Original-Received: from [207.115.63.78] (helo=pimout6-ext.prodigy.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BZLVl-0003xo-CH; Sat, 12 Jun 2004 23:18:21 -0400 Original-Received: from floss.red-bean.com (adsl-65-42-95-31.dsl.chcgil.ameritech.net [65.42.95.31]) by pimout6-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id i5D3IKRB453802; Sat, 12 Jun 2004 23:18:20 -0400 Original-Received: from kfogel by floss.red-bean.com with local (Exim 3.34 #1 (Debian)) id 1BZFcp-0003zv-00; Sat, 12 Jun 2004 16:01:15 -0500 Original-To: Miles Bader X-Windows: sometimes you fill a vacuum and it still sucks. In-Reply-To: <20040613023944.GA13072@fencepost> Original-Lines: 33 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:24907 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24907 Miles Bader writes: > It's critical, IMO -- my experience of using mozilla and savannah's bug > tracker is that the annoyance of having to go to the web site and muddle > through the forms significantly decreased the likelihood that I would bother > (it was fine the first N times, but after a while I started to dread it). Note that filing bugs by email significantly increases the likelihood of duplicate issues. One of the advantages of going to the web site is that you can first search to see if the bug already exists in the database. Whereas if you fire off an email, there's no query step. Sure, the editing environment for an email is better -- Emacs buffer, rather than web form -- but the web forms *are* also a realtime database front end, and that makes a difference too. I'm not sure what interface made you "muddle through forms". In my experience, if you're filing a new bug, there's one form to fill out, and if you're modifying an existing bug, then you just go to a URL and make the appropriate change. It's not that hard; I certainly don't dread it. Administering existing bugs by email would be nice, of course. For example, I'd like to be able to respond to an email sent by the issue tracker, and have my response cause some new change to the bug. But lack of this feature is hardly a showstopper. Please, let's not aim for perfection, that way lies madness. Some issue tracker is better than no issue tracker, and if one sets up the appropriate bookmarks and URLs, one should never have to muddle through multiple forms to get things done. -Karl