[mantisbt-dev] Bugtracking for Plugins

[Roland B. <ro...@at...>]

Hi all,

I would like to get a short discussion and a decision for bugtracking of the 
various MantisBT plugins.

At the moment there are at least three models for this.

1. No bugtracking system (or mailing the developer)
2. Own bugtracking system (some based on MantisBT)
3. Bugtracking using www.mantisbt.org/bugs in a horrible way, for examples see [1] and [2]

There are some options to get this consolidated.

1. Use the existing www.mantisbt.org/bugs and add one project per plugin
2. Setup an own instance, something like www.mantisbt.org/pluginbugs
3. Setup an own instance at another server

I think the advantages and disadvantages are quite obvious around themes 
user management, project management, relations between issues of plugins and core system, redundancy,
scattered information, ....

I prefer option 1 where every plugin developer who is interested should get his own project with
access level MANAGER for it (or DEVELOPER and some changed thresholds)

If there will be no decision/actions the next days I will setup a system on another server.
If this would be adopted by plugin developers there can be a later decision
to move the instance or data to www.mantisbt.org

I don't think it's a good idea at the moment to discuss the whole plugin story.
(Questions like: should plugins have a common code repository, a common forum, 
a common website, should there be a certification, when should a plugin become 
part of standard delivery of MantisBT ....)

I would like to concentrate on bugtracking of plugins as a first step.

Roland

[1] http://www.mantisbt.org/bugs/view.php?id=4286
[2] http://www.mantisbt.org/bugs/view.php?id=4220