James Bursa wrote:
If we're going to change bug tracker, what features are most
I think we need:
- really easy adding bugs without setting up an account
- some way to transfer the bugs from SourceForge
- a way for users to ask "website x renders wrong / doesn't work, is this
known / is there a workaround?"; maybe this needs to be a separate database
I've been toying about with SVNTrac, a version of Richard D. Hipp's
CVSTrac. It's very basic and non-bloaty, but still flexible and works
OK in NetSurf itself. It's been well tested, as Richard's other
software (SQLite, Lemon, etc) uses it. The only drawback is that it
needs to have access to the file system on which the subversion
I have one set up that you're welcome to play with: http://svn.rjek.com/
Guest account is guest/guest. Feel free to mess around, I need to
delete and recreate the database anyway.
Constraints I would place on a BTS would be:
* Not written in PHP or Java,
* Integrates well with our versioning system (perhaps so we can
say 'fixes #1234' in the commit message and BTS gets updated,
but that's really fancy)
* Not Edgewall's Trac, as while it's very nice, it has a
plethora of security problems.
* Obviously being usable in NetSurf would be good.
* Anonymous bug reporting, but at least say to the anonymous
user that it would be better if they really did make an
I'm sure there are most likely loads of other criteria too.