Re: BugCommunicator as a GRUB BTS

[Yoshinori K. Okuji]

At Mon, 28 Oct 2002 14:51:42 +0100 (CET),
Dr. Tilmann Bubeck <address@hidden> wrote:
> Well, nothing in particular is bad with bugcomm. The only thing is, that
> there are already a large number of bug reporting tools. If there is a
> special thing, which you don't like about the existing tools, then think
> about contributing a patch. This is what many users of GRUB do, instead of
> writing a new boot loader.. ;-)

I agree with you. There are many BTS implementations. Too many. But I
want to point out two things.

First of all, your indication is too late. BugCommunicator is not
vaporware, but it is already working. So, it wouldn't save my time to
switch to another BTS. Rather, it would be wasteful, because I created
it for my own taste and I'm quite familiar with it.

Well, about the other. I generally tend to contribute to existing
software projects rather than reinventing the wheel. In fact, I have
done to several tens of projects. I don't make new software
unnecessarily.

When I was a young programmer, I thought code was the most
important. But I considered what made GRUB so nice, and I realized
there was a much more important thing, that is to say, a design. How
to design a software package is a much bigger problem than how to
implement it.

IMHO, if the design of a software package sucks, it isn't worth
improving, even if the implementation is elegant, beautiful, simple,
and smart. Especially when the goal is different from yours, there is
no point where you can contribute.

That's why I started BugCommunicator. I surveyed some famous projects
before starting and concluded that no project would satisfy my
needs. Sicne it is critical for us to have a good BTS, I believe that
I didn't waste my time.

Okuji