In addition, once I relaunch (something that damien and others have been asking about getting accessible again), I'll be working on doing this in a way to allow plugins hosted their to have access to a freely available mantis instance.

I'd expect that if done right, would become a community location for people to find services and plugins around mantis.


On Tue, Mar 4, 2014 at 8:23 PM, Roland Becker <> wrote:
In response to

> Roland Becker <> hat am 4. März 2014 um 21:22 geschrieben:
> > 1. Create a project per plugin independent of size.
> This is what we have for 12 plugins and the Mylyn Connector at the moment.
> > 2. Create a project for all plugins and use category to represent the
> > specific
> > plugin.
> There are some plugins in project mantisbt with category plug-ins
> > 3. Create a separate bug tracker for all plugins -- separating it from this
> > one that focuses on MantisBT core. The plugins bugtracker could be hosted on
> > MantisHub.
> Not that good if there are relationships between MantisBT and plugin issues
> > 4. Make all plugins use github going forward for tracking their issues.
> There are some existing plugins using github
> > I'm thinking that 4 may be good enough. If not, then I would choose a
> > consistent model from the others.
> Don't eat our own food?
> Furthermore there are plugins/addons that host their own MantisBT instance.
> Quite hard to choose _one_ consistent model after there are at least four
> models
> alive. 

Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
mantisbt-dev mailing list