Adding More Projects to Mantis

[SinbadEV]

I was inspired by this post.

Anyway, it actually makes sense if we are going to let content developers have their own sub-forums that we also let them into the Bug tracking too.

This functionality relies on someone being able to change the project a bug is associated with if it was reported wrong (which I'm not sure mantis can do).

Namely I'm suggesting we add projects( or categories) for Widgets, Maps and any Mods, Lobbies or other side apps (like map builders, Spring Downloader) that want to participate (using the same rules for inclusion as we do for sub-forums). Then, ALL bugs could be submitted to the same place, and if it was determined that they had been submitted to the wrong place after review or testing, instead of rejecting them they could be re-assigned to somewhere they could be useful.

The easier it is for people to report useful bugs the better.

It would be really cool if when a bug was submitted that needed further testing or more information, instead of it being ignored there was a way to let the community know about that need, with the number of users we have, someone must have run across a similar problem before... and getting more people into the bug tracking system more often would be a good way to have this happen.

[imbaczek]

this should probably live in the same place as the widget database to keep everything in one place. not a bad idea, but i can see problems with getting maintainers.

[zwzsg]

We need middle men, that scours the Help & Bugs subforums, and then transmit the information to whoever is in charge of the part causing the bug through the mean the one in charge of that part prefers: IM/Post in project's subsite/Mail/Nagging in lobby/PM in Spring's forum/Spring's Mantis/CA's bugtracker/...

[hoijui]

sounds like a perfect job for one of these 10 yer old chinese street kids with no future and no idea of what life means as they never saw it...
they should reassemble a workign pc fom the dead parts they get every day, and then work as slave for us, as this middle man. though if thye got that scrap PC together, thye may already have to much of an idea of life to be willing to do this.

[FLOZi]

wrt mods and games, sounds like the kind of thing they should handle themselves.

*insert links to numerous S44 bugtrackers/bug reporting forums*

[AF]

Perhaps a switch from mantis to something that doesn't make me want to tear my eyes out? Redmine seems to work well for me and the springinfo people

[imbaczek]

i heard horror stories about upgrading redmine.

[det]

SpringLobby switched from Trac to RedMine and I think it was much nicer as Trac. At one point I offered to host a Trac for Spring and even set it up and imported all bugs from Mantis. Noone seemed really interested though.

[koshi]

i've had no problem updating redmine so far
if you guys seriously consider this the offer of trying to import mantis db still stands

[Forboding Angel]

Redmine is really nice. I do like trac quite a lot, but after using redmine I don't think I would want to go back to trac. Redmine has a lot more features that are useful for random idiots such as myself.

[el_matarife]

Here's an idea: Why not split the forum into "Help me" and "Bug Discussion", with bug discussion threads required to have Mantis links?

Help forum:
Imagine this as almost a helpdesk style tracking system. You open a thread with a complaint. People post in the thread until your issue is resolved, then it is locked and the title is edited to "Resolved X.XX.X: Foo Bar" where X.XX.X is the Spring version you had your problem on and Foo Bar was your problem. This would make it easy to see who's having problems so you can help them out, and over time the resolved problems will almost turn into a FAQ. The resolved threads could be moved into locked subforums based on major Spring versions as an archive.

Bugs forums:
Each thread would need a Mantis entry to go along with it. After a bug is found and resolved, the thread would be locked. Threads would be tracked on a per version basis so the information in the bugs forum would only be for the current version of Spring. Old threads would be moved to an archive, unless the bug is still being tracked.

Combine both of these with AF's automatic crash uploading system, and it would be war on Spring bugs.