From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Bug tracking Date: Sun, 13 Jun 2004 00:09:04 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040613000234.B07C.LEKTU@mi.madritel.es> References: <20040612143605.151D.LEKTU@mi.madritel.es> <87zn78wzv6.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1087078212 16728 80.91.224.253 (12 Jun 2004 22:10:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 12 Jun 2004 22:10:12 +0000 (UTC) Cc: Juri Linkov , rms@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Jun 13 00:10:02 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 1BZGhM-00042i-00 for ; Sun, 13 Jun 2004 00:10:00 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZGhM-0006H1-00 for ; Sun, 13 Jun 2004 00:10:00 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZGiA-0002Qn-7Q for emacs-devel@quimby.gnus.org; Sat, 12 Jun 2004 18:10:50 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BZGhc-0002B5-Pd for emacs-devel@gnu.org; Sat, 12 Jun 2004 18:10:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BZGhZ-00029f-Ff for emacs-devel@gnu.org; Sat, 12 Jun 2004 18:10:15 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZGhY-00028M-Th for emacs-devel@gnu.org; Sat, 12 Jun 2004 18:10:12 -0400 Original-Received: from [62.81.186.19] (helo=smtp09.retemail.es) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BZGgV-0002ZY-0l; Sat, 12 Jun 2004 18:09:07 -0400 Original-Received: from [127.0.0.1] ([213.37.34.195]) by smtp09.retemail.es (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20040612220902.WQWI29475.smtp09.retemail.es@[127.0.0.1]>; Sun, 13 Jun 2004 00:09:02 +0200 Original-To: emacs-devel@gnu.org In-Reply-To: <87zn78wzv6.fsf@mail.jurta.org> X-Mailer: Becky! ver. 2.09.01 [en] 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:24885 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24885 On Sat, 12 Jun 2004 18:38:29 +0300, Juri Linkov wrote: > Even without special mode a plain text file is the most convenient > way to edit data and to perform arbitrary Emacs operations on them. No, a plain text file is not necessarily "the most convenient way to edit data", not by a long shot. Certain kinds of data, yes. And yes, it is easi to perform arbitrary Emacs operations on it, but we don't want to perform arbitrary operations, but a few, very specific, widely used kinds of operations: the ones usually associated with bug/issue management. Your claim is so broad that it seems like you were saying that Emacs is "the most convenient way" to do anything. > I think there is nothing wrong with the fact that only Emacs > developers will be able to fill bug reports. So no web interface > is really needed. Obviously, we *strongly* disagree here. I see much wrong with only Emacs developers being able to fill bug reports (for one, that means someone *has* to do the work which could have made the user). So the web interface is, to me, really needed. > That's exactly how it might work: developers read gnu-emacs-bugs, > create new bug entries in the text file and commit them to CVS. > And you can track changes in the text file with all the usual > features of CVS. Yes, I understand how could it work, I just happen to think that is a extraordinarily un-optimized way to do things. See etc/TODO: would you dare say that it is really used for the intended purpose? Many things in TODO have been there for years, and almost *all* things implemented or fixed never ever touched TODO. > Apart from the Ee categorizing manager, I think that some other > Emacs packages can perform these operations on text files. > AFAIK, at least Gnus should be able to read a text file in the > mail-like format and to treat it as a mail group with bug and TODO > entries as messages. There are even many possibilities of tighter > integration with its email functionality. Aren't you saying that we can shoehorn something into simulating being an issue tracker, just to *not* use an issue tracker which already does all that? /L/e/k/t/u