. Some random comments:
1) don't pad the bug id with zeroes (if that's possible)
The bug ID displayed in the view is the default. Options are to either try to change it or to just list the bug by the significant digits and let people learn to discount the zeros themselves
2) platform information is actually quite hard to specify since there are actually three states for each platform: affected; not affected; not yet checked. I can't tell if the Platform field in the Advanced view is a drop-down menu or free text. Either way, it's not shown in the Simple view and it's actually quite useful so I suggest the Additional Information field in the Simple view stores this. e.g.: "Linux: yes | Mac: no | Windows: unknown".
Hmmm... my concept was to list the bugs sorted by platform, and you can tell that I started down that path by the category bug 1 is in... but that is in direct conflict with the way we've been doing it in the forums. So note this well, lmop!... ... ... you're not the only one to lose track of what they were doing with one aspect or another of this project
The good news is that Mantis has a "Custom Fields" function and I'll put researching that at the top of my to-do list... right after pawprints, of course.
3) categories (I've deliberately made these fairly vague; we can subdivide more intelligently later on when we actually have some bugs to group):
Development Environment - issues with IDEs, Makefiles, build scripts and the source code itself
Equivalent to, and including the stuff covered by, the current "HW-SDL compile status" category?
Game - problems when playing the game
Tools - editing/modding tools
Straightforward, though subdivision seems inevitable.
To Do - possibly contentious but we need somewhere to log the stuff we know we should do, no-one has any time to do but which a new recruit might want to throw themselves at.
like the "HW-SDL fixme rollcalll", for example?...
4) the following users should all be given "developer" logins: alankila, aunxx, azurief, lmop, nova
since they are actually in a position to fix the bugs that get entered
Hmmm.... some elements of that list seem familiar...
As I said, I'll be giving logins to coders
, which forum rank, however erratically applied by me (whenever I remember to apply it), does seem to cover "developer" status.
I hadn't considered other ranks when I said that, but it seems logical to give "reporter" status to those who are interested in risking... -er- testing
the code, but haven't taken the plunge of serious HW source coding (... yet
As you have listed yourself in there I've signed you up, so check your mail.
So everyone else check in here (or the other Mantis thread) and ask and I'll set it up. (that should also help assure that you're up to date with what we're doing with Mantis etc.)