[gentoo-dev] IssueTracker Requirements

[Joshua Pollak]

Ok,

Here is a list of issuetracker requirements, as I remember them. They are not 
sorted in any particular order of importance, although things I think 
everyone can agree are 'nice things to have but not show stoppers' are lower 
down the list:

email interface
easy to use web interface
clean, modifiable code base
multiple package support
easy for newbies
	- quick to add bugs (most important)
	- search, find duplicates (almost as important)
	- update status and communicate with developers
powerful for developers
irc interface bot
implemented in a real language (not PHP, etc)
desktop user interface (GUI?, command-line?)

Current candidates, with implementation language, and URL:
Because I can't resist, I've included one line for both upside and downside 
to each package, as I see it.

* Roundup
	- Python
	- http://roundup.sf.net
	- Plus: Email interface, passable web interface, command-line interface
	- Unfamiliar to many of us.

* Bugzilla
	- ???
	- http://www.mozilla.org/projects/bugzilla/
	- Plus side: Monster program with basically every feature imaginable
	- Downs: large, large learning curve.

* PEST
	- PHP
	- http://unrecoverable.org
	- Plus side: cute Web interface, DB storage (good for other interfaces)
	- Downside: PHP, no mail interface

* Debian BTS
	- "most of the code is written in Perl5"
	- http://www.benham.net/debbugs/
	- Plus: "now has a fairly rich feature set", everything via email
	- Down: "system has grown fairly organically", kludgy web interface
(quotes are from Debian BTS website)

* GNATS
	- everything
	- http://www.gnu.org/software/gnats/
	- Plus: Official GNU software
	- Downs: Web, TK, etc interfaces are seperate, install looks like a pain 

* Improve current dev-wiki
	- ???
	- I must be blind, because I can no longer see the link to the wiki.
	- Gentoo specific project, we decide how it should be done
	- Gentoo specific project, lots of work, risk wasting time repeating other 
peoples work.