Rob Mahlert skreiv:
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.A few have permission to do this.. if they don't, let me know and I'll make sure they do. You know who you are when you log onto it, just e-mail me and I can update the accounts.
Well, they don't ;-) And I don't think the people that are actually fixing bugs are using the bugtracker that much either. I found several cases today that I know have been fixed, but the people who has done the fixes has not resolved the cases. Integration between cvs and the bugtracker would help here.
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.SPAMMERS and hackers! To protect the system, I have to keep the registrations and even that is not enough! The server was hacked in the
Then Mantis must be very vulnerable if it can be hacked by receiving an email with attachments.
At work we're using FogBugz both internally and also as a support system to out customers. Everybody can send a mail to FogBugz, yet spam is not a problem at all. The spamfilter takes care of this.
If ordinary users has to either subscribe to the mailing list or ask for a bugtracker-account just to report a bug, then it won't be done. Without simple, anonymous bug-reporting the value of the bugtracker is limited.
3. The roadmap-feature must be used.This is for Frank to decide or if enough agree.. but who will maintain it??
There must of course be a project manager. Either a single person or a team.
4. The CVS integration must be used.Same as above.. for Frank.
So what do you say Frank? Integration with CVS makes it much easier to track bugs, especially when some newcomer needs to figure out what the hell happened three years ago.
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.Maybe for registered.. but NEVER anonymous! They are already trying to hack into the system.
Then there must be a more robust tool than Mantis. Teams all over the world are doing these kinds of things, so it must be possible?
6. The routines regarding development, patching, bugtracking etc must be documented and the documents must be easily obtained.If someone wants to write it.. it can be easily placed on the sparemint.org website. Which if you have CVS write access.. you can update the site.
Not many have CVS write access. Anyway, the sparemint website would benefit from an update. Using a wiki and having a team of editors would make the web-site much more dynamic and easily maintained.
Jo Even