Re: [MiNT] Bugtracker

[Rob Mahlert <rmahlert@charter.net>]

Jo..  the problem is I have several SPAM accounts created a week.
To keep it secure.. I turned off attachments and required user accounts.
More below..

Jo Even Skarstein wrote:
> 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 Smilefjes 
> Uttrykksikon
>  
> 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.
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.

> 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 
past from an old mantis install, my fault for not updating the scripts 
regularly.

> 3. The roadmap-feature must be used.
This is for Frank to decide or if enough agree.. but who will maintain it??
> 4. The CVS integration must be used.
Same as above.. for Frank.
> 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.

> 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.

> 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.
>  
I agree.

Rob Mahlert