From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: Bug Database? Date: Sat, 21 Oct 2006 10:31:59 +0900 Message-ID: <87pscm314g.fsf@catnip.gol.com> References: <17717.20433.183356.106695@kahikatea.snap.net.nz> <87odsameu4.fsf@furball.mit.edu> <17717.45053.900033.152204@kahikatea.snap.net.nz> Reply-To: Miles Bader NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1161394345 10820 80.91.229.2 (21 Oct 2006 01:32:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 21 Oct 2006 01:32:25 +0000 (UTC) Cc: lekktu@gmail.com, rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 21 03:32:24 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Gb5io-0007eY-CA for ged-emacs-devel@m.gmane.org; Sat, 21 Oct 2006 03:32:22 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gb5in-0007do-S2 for ged-emacs-devel@m.gmane.org; Fri, 20 Oct 2006 21:32:21 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gb5ib-0007dN-9J for emacs-devel@gnu.org; Fri, 20 Oct 2006 21:32:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gb5iX-0007cz-Q7 for emacs-devel@gnu.org; Fri, 20 Oct 2006 21:32:08 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gb5iX-0007cw-Mv for emacs-devel@gnu.org; Fri, 20 Oct 2006 21:32:05 -0400 Original-Received: from [203.216.5.72] (helo=smtp02.dentaku.gol.com) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Gb5iU-0001GI-Ng; Fri, 20 Oct 2006 21:32:03 -0400 Original-Received: from 203-216-96-133.dsl.gol.ne.jp ([203.216.96.133] helo=catnip.gol.com) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1Gb5iS-0002ZW-4L; Sat, 21 Oct 2006 10:32:00 +0900 Original-Received: by catnip.gol.com (Postfix, from userid 1000) id B54892F45; Sat, 21 Oct 2006 10:31:59 +0900 (JST) Original-To: Eli Zaretskii System-Type: i686-pc-linux-gnu In-Reply-To: (Eli Zaretskii's message of "Fri\, 20 Oct 2006 07\:55\:34 +0200") Original-Lines: 40 X-Abuse-Complaints: abuse@gol.com X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:60976 Archived-At: Eli Zaretskii writes: > Usually, it's the other way around: the bugs are reported to the > bug-tracker, which then emails them to the list. > > We could modify report-emacs-bug to use a Web browser (via url, for > example) to do that. While it's nice to have the _ability_ to submit bugs via the web (casual users might find it easier to deal with such an interface), I think email reporting is mandatory. It's also nice to have something like debian's "reportbug" program, which uses a simple UI on the user's machine to prompt for details, but sends email to actually report the bug. Basically, choice is good. Several reasons for this: (1) Email is available in situations where web access is not (the reverse is true too of course: again, choice is good). (2) Typical web bug-tracker interfaces are completely awful (bugzilla, I'm looking at you...) and the lack of integretation with one's familiar environment annoying. Clumsy web interfaces are especially frustrating when reporting many bugs, because one must painfully labor through the same bad interface repeatedly -- when email is supported, one can streamline the process greatly (elisp is great for this). (3) Many bugs involve "conversations", with back-and-forth between developers (often more than one) and bug reports. Web-only interfaces like bugzilla make this very awkward -- while it wil _send_ email to indicate a new response in "the conversation" about a bug, one must then go to the web page and fill in a form to reply! The natural thing, simply replying (to the email'd report) via one's mail client, isn't supported! -Miles -- "Suppose we've chosen the wrong god. Every time we go to church we're just making him madder and madder." -- Homer Simpson