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: Mon, 14 Jun 2004 23:36:56 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040614232525.A694.LEKTU@mi.madritel.es> References: <20040614091950.7D88.JMBARRANQUERO@wke.es> 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 1087249077 22735 80.91.224.253 (14 Jun 2004 21:37:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 14 Jun 2004 21:37:57 +0000 (UTC) Cc: Thien-Thi Nguyen Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Jun 14 23:37:48 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 1BZz9H-0005e8-00 for ; Mon, 14 Jun 2004 23:37:47 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZz9H-0003m8-00 for ; Mon, 14 Jun 2004 23:37:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZzAB-0006aR-Um for emacs-devel@quimby.gnus.org; Mon, 14 Jun 2004 17:38:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BZzA8-0006ZF-Vk for emacs-devel@gnu.org; Mon, 14 Jun 2004 17:38:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BZzA7-0006XZ-4S for emacs-devel@gnu.org; Mon, 14 Jun 2004 17:38:40 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZzA7-0006XT-24 for emacs-devel@gnu.org; Mon, 14 Jun 2004 17:38:39 -0400 Original-Received: from [62.81.186.17] (helo=smtp07.retemail.es) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BZz8W-0007Ty-Fx for emacs-devel@gnu.org; Mon, 14 Jun 2004 17:37:00 -0400 Original-Received: from [127.0.0.1] ([213.37.34.54]) by smtp07.retemail.es (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20040614213658.FYVO18116.smtp07.retemail.es@[127.0.0.1]>; Mon, 14 Jun 2004 23:36:58 +0200 Original-To: emacs-devel@gnu.org In-Reply-To: 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:24970 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24970 On 14 Jun 2004 12:40:43 -0400, Thien-Thi Nguyen wrote: > i think if you separate the user interface question from the data > representation question, you will receive less static. You lost me there. My primary interest is user interface, which is what makes or breaks the success of a bug tracker. Users must be able to enter bug reports easily, and developers must be able to see what's done and what's waiting, who's doing what, etc. also easily Whether the data is in cuneiform tablets or tachyonic particles oscillating between alternate universes is an implementation detail. (Which doesn't mean all representations are equivalent, obviously). But in fact, and contrarily to many things heard in this thead, I'm specifically proposing to develop *nothing* (or at least, almost nothing), so data representation is an issue for the software already existing out there, not for me. I'm hearing about using text files and developing modes to manage and display that information, and I wonder, who's going to implement it? Because I know I'm not (although I will use whatever we have, if someone invests the effort in developing it). First, though, we'd have to answer whether we want a bug tracker (as I proposed), a pending-and-future-issues planner (as I think Richard wants), both or none. Personally I find little use in the planner, a text file (with no custom elisp development) is fine. But a bug tracker, oh yes, I strongly think this would be good for the project. /L/e/k/t/u