Inspired by Miro's talk about a project management tool,
I had a look at the Mantis bugtracker on sparemint.org. I think it would serve
us well if used correctly. After all, this is a hobby project and we should be
very careful about making it too bureaucratic 
However, the tool is not worth anything if we don't use
it properly. So far the bugtracker has not been used that much, and it's not
very widely known. In order for it to be used and to be of real value some
issues would have to be adressed:
1. There must be atleast one person that keeps track of
what's happening, someone to make sure that cases are closed when they should be
etc. Right now there are lots of cases that should have been closed, which makes
the situation look worse than it is. There are also some very old cases which
are worthless by now.
2. It must be very easy for the average user to report
bugs. Either through email or a simple form that does not require registration.
The reporter must get feedback about the status of the bugreport.
3. The roadmap-feature must be used.
4. The CVS integration must be used.
5. Attachments must be allowed in both anonymous
(screenshots, logs etc) and registered bug-reports. Then patches can be
submitted to the relevant case if the developer does not have CVS write
access.
6. The routines regarding development, patching,
bugtracking etc must be documented and the documents must be easily
obtained.
An up-to-date and well maintained bug- and
featurelist would be very beneficial to this project, especially for a newcomer
that doesn't have everything in his head.
Jo Even
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4694 (20091216) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com