From: Thompson, B. B. <BRY...@sa...> - 2006-01-13 14:53:05
|
Kevin, 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. -bryan -----Original Message----- From: jdb...@li... [mailto:jdb...@li...] On Behalf Of Kevin Day Sent: Friday, January 13, 2006 9:47 AM To: Thompson, Bryan B.; JDBM Developer listserv Subject: re: [Jdbm-developer] jdbm issue tracking. Bryan- Just for my own edification - what are the advantages of using JIRA instead of the issue tracking system provided by SourceForge? Thanks, - K > Alex, I would like to suggest that we use JIRA to track issues as we begin a 2.x jdbm. I have an open-source license grant [1] for the cweb project and I can add a project entry for jdbm. -bryan [1] <http://jira.cognitiveweb.org/> http://jira.cognitiveweb.org/ < ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Jdbm-developer mailing list Jdb...@li... https://lists.sourceforge.net/lists/listinfo/jdbm-developer |
From: Thompson, B. B. <BRY...@sa...> - 2006-01-13 17:49:53
|
Alex, I have not been able to get subversion working with eclipse, but I am otherwise fine with this. The codehaus people do some great work. -bryan -----Original Message----- From: Alex Boisvert [mailto:boi...@in...] Sent: Friday, January 13, 2006 12:18 PM To: Thompson, Bryan B. Cc: JDBM Developer listserv Subject: Re: [Jdbm-developer] jdbm issue tracking. Speaking of which, I have an offer on the table to move the project to CodeHaus. http://www.codehaus.org/ This would improve our infrastructure in many ways, including the following services: Wiki: Confluence Bug tracking: Jira Version control: Subversion Blog: [not sure what they use, but they have something] IRC: irc channels Build: Continuum Interested? alex Thompson, Bryan B. wrote: > Alex, > > I would like to suggest that we use JIRA to track issues as we begin a > 2.x jdbm. I have an > open-source license grant [1] for the cweb project and I can add a > project entry for jdbm. > > -bryan > > [1] http://jira.cognitiveweb.org/ |
From: Alex B. <boi...@in...> - 2006-01-13 18:30:19
|
Are you talking about Subclipse? http://subclipse.tigris.org/ I've used it for a while without problems. alex Thompson, Bryan B. wrote: > Alex, > > I have not been able to get subversion working with eclipse, but I > am otherwise fine with this. The codehaus people do some great work. > > -bryan > > -----Original Message----- > From: Alex Boisvert [mailto:boi...@in...] > Sent: Friday, January 13, 2006 12:18 PM > To: Thompson, Bryan B. > Cc: JDBM Developer listserv > Subject: Re: [Jdbm-developer] jdbm issue tracking. > > > > Speaking of which, I have an offer on the table to move the project to > CodeHaus. http://www.codehaus.org/ > > This would improve our infrastructure in many ways, including the > following services: > > Wiki: Confluence > Bug tracking: Jira > Version control: Subversion > Blog: [not sure what they use, but they have something] > IRC: irc channels > Build: Continuum > > Interested? > > alex > > > > Thompson, Bryan B. wrote: >> Alex, >> >> I would like to suggest that we use JIRA to track issues as we begin a >> 2.x jdbm. I have an >> open-source license grant [1] for the cweb project and I can add a >> project entry for jdbm. >> >> -bryan >> >> [1] http://jira.cognitiveweb.org/ -- Alex Boisvert, Product Development Director Intalio, Inc. | www.intalio.com boi...@in... |
From: Thompson, B. B. <BRY...@sa...> - 2006-01-17 11:16:07
|
Alex, 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 [1] 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 jira instance. -bryan [1] http://jira.cognitiveweb.org -----Original Message----- From: Alex Boisvert [mailto:boi...@in...] Sent: Monday, January 16, 2006 7:18 PM To: moe Cc: Thompson, Bryan B.; Kevin Day; JDBM Developer listserv Subject: Re: [Jdbm-developer] jdbm issue tracking. Moe, 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 ;) alex moe wrote: > On Fri, Jan 13, 2006 at 09:53:37AM -0500, Thompson, Bryan B. wrote: >> Kevin, >> >> 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 > instead. > > 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 > or > whatever) that I know of but I don't think that's really needed either way. > (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, > > moe |
From: moe <fil...@mb...> - 2006-01-13 22:11:34
|
On Fri, Jan 13, 2006 at 09:53:37AM -0500, Thompson, Bryan B. wrote: > Kevin, > > 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 instead. 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 or whatever) that I know of but I don't think that's really needed either way. (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, moe |
From: moe <fil...@mb...> - 2006-01-13 22:15:59
|
PS: I'm not involved with jdbm developement (only on the list because I used jdbm on some projects), so please take my words as friendly advice, I'm not trying to bash anyone or anything. :-) |
From: Alex B. <boi...@in...> - 2006-01-17 00:17:56
|
Moe, 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 ;) alex moe wrote: > On Fri, Jan 13, 2006 at 09:53:37AM -0500, Thompson, Bryan B. wrote: >> Kevin, >> >> 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 instead. > > 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 or > whatever) that I know of but I don't think that's really needed either way. > (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, > > moe |