With respect to JIRA, I have asked for and received a license grant for
the jdbm project. I can host a jdbm project within an existing JIRA
instance  at any time. If you want to wait until/if jdbm is transferred
to codehaus, then fine. I am probably not inclined to establish a new jira
instance specifically for jdbm, but only to happy to host jdbm with the cweb
From: Alex Boisvert [mailto:boisvert@...]
Sent: Monday, January 16, 2006 7:18 PM
Cc: Thompson, Bryan B.; Kevin Day; JDBM Developer listserv
Subject: Re: [Jdbm-developer] jdbm issue tracking.
As they say, better the devil you know than the devil you don't know!
I would need to take a look at Mantis... Right now, I'm in the camp of
those familiar with Jira (both user and administration) and I find it
usable -- especially compared to Bugzilla!
There's also the issue of hosting. Both SourceForge and Codehaus
already have their bug tracking setup. With Mantis we would have to
setup and maintain it ourselves. Time spent on installing, configuring
and maintaining Mantis is time not spent on JDBM ;)
> On Fri, Jan 13, 2006 at 09:53:37AM -0500, Thompson, Bryan B. wrote:
>> I'm not sure that I can provide you with a feature breakdown. JIRA
>> is much nicer in my experience. Enough so that it has become the
>> de-facto standard for open source projects. While JIRA is not open
>> source itself a no-cost license is available for use with open source
>> projects. My employer also uses JIRA internally, but I was not part
>> of the process for selecting the internal issue management system.
> I beg to disagree here. I find JIRA a pain to use and would like to
> suggest to try mantis (http://www.mantisbt.org) for bugtracking
> Here is a demo: http://bugs.mantisbt.org/main_page.php
> Mantis is opensource, very easy to install (just a set of PHP scripts,
> needs a MySQL database) and in contrast to most other tools that I
> have tried (including JIRA) it is *very* userfriendly.
> It doesn't offer any kind of integration with your VCS (be it CVS, SVN
> whatever) that I know of but I don't think that's really needed either
> (in fact there may be some plugin that I just don't know about)
> Its main feature is the usability, just give it a shot and you know
> what I'm talking about.
> For the VCS I'd suggest to just stick with CVS unless you have a good
> reason to switch. Imho SVN doesn't offer many worthwhile advantages
> over CVS but only introduces additional hassles (it depends on Apache2
> for remote service for example). Never change a running system...
> So, in summary, I'd strongly suggest to satisfy your needs with
> individual tools (e.g. mantis for bugtracking, twiki for wiki,
> qmail+ezmlm for mailing list etc.) instead of trying to find one
> integrated "swiss army knife" that does it all - but poorly.
> JIRA is a particularly bad example, too.
> If you really want one integrated package then
> TRAC (http://projects.edgewall.com/trac/) may be worth a look.
> Rule of thumb: Usability is generally more important than features.
> best regards,