Re: Bug tracking

[Juanma Barranquero]

On 14 Jun 2004 12:40:43 -0400, Thien-Thi Nguyen <address@hidden> 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