Re: The Linux Kernel Project Management System (INITIAL PROPOSAL)

Anthony Towns (aj@azure.humbug.org.au)
Tue, 28 Sep 1999 13:35:35 +1000


On Mon, Sep 27, 1999 at 04:32:13PM -0400, Jordan Mendelson wrote:
> The bug reporting and tracking system can be a modified version of Bugzilla.
> Bugzilla has proven itself to be a very adaptable and usable system. The bug
> reporting system should allow bug reporting directly from the console without
> a web browser via an automated program that would gather system information,
> however the bulk of bug reports should be done with a web browser. The bug
> reports should contain all critical information including system components,
> crash information, etc.

The Debian BTS [0] might be worth considering here too. It's used by at
least Debian, Gnome and KDE [1], and has both web (for viewing) and mail
(for manipulating and viewing) interfaces. Every bug gets forwarded via
email to the appropriate maintainer and a couple of mailing lists as
soon as its received, and added to the archives. It's GPLed for what
that's worth. There are a number of tools to make bug reporting and
viewing easier (reportbug.deb and bug.deb come to mind) and it's also
a fairly well tested and reliable system.

It's designed to handle lots of small programs though, rather than one
big project with lots of inter-related modules though.

> The peer review system should be web based. The web provides an efficient
> means of managing something as complex as the Linux kernel. Patches should be
> sorted into individual sets, new patches, accepted patches, and denied
> patches. You should be able to comment on the patches. Patch comments should
> be delivered via email by the author if requested. It should be as tightly
> integrated with Bugzilla as possible as Bugzilla already implements most of
> the features required for the peer review system.

Debian uses "wishlist" bug reports for this, more or less (bug fixes get
normal priority, security fixes get critical priority). For most bugs,
it works pretty well --- you can send a feature request, and add patches
/ comments or whatever. When the maintainer uploads a fixed version,
they close the report. Having the bug reports go to various mailing lists
also helps this.

Too much discussion really doesn't work that well though --- the important
points get lost in the discussion so if you just want to find out the key
points from some month old bug report, it becomes pretty painful. The
archived discussion also isn't threaded, which can be a pain in these
cases.

Cheers,
aj

[0] http://benham.net/debbugs/

[1] http://bugs.debian.org/, http://bugs.gnome.org/, http://bugs.kde.org/

-- 
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. PGP encrypted mail preferred.

``Like the ski resort of girls looking for husbands and husbands looking for girls, the situation is not as symmetrical as it might seem.''

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/