Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [PROPOSAL] Jakarta Commons moving to JIRA
From: Simon Kitching <simon@ecnetwork.co.nz>
Reply-To: simon@ecnetwork.co.nz
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
In-Reply-To: <40032595.7060407@latte.harvard.edu>
References: <NBBBJGEAGJAKLIDBKJOPOEMNGIAB.noel@devtech.com>
	 <40032595.7060407@latte.harvard.edu>
Content-Type: text/plain
Organization: The Electronic Commerce Network Ltd.
Message-Id: <1073949557.6291.200.camel@pcsimon.ecnnz.ecnetwork.co.nz>
Mime-Version: 1.0
Date: Tue, 13 Jan 2004 12:19:17 +1300
Content-Transfer-Encoding: 7bit

I'm -0 on moving Digester (the project I mostly contribute to).

It's purely on philosophical grounds. While it's kind of the JIRA team
to grant free use of their product I would prefer to stay with something
free. I'm not opposed to commercial products but bug/issue tracking is a
core development tool and as such there really should be a good free
solution. By moving to JIRA we take away motivation to work on better
free alternatives to Bugzilla, like Scarab (http://scarab.tigris.org).

On Tue, 2004-01-13 at 11:54, Mark R. Diggory wrote:
> Hmm, I suspect that MATH would be at home there. Lets move it there (if 
> there is no objection).
> 
> -Mark
> 
> Noel J. Bergman wrote:
> > Guys,
> > 
> > There are separate requests on the table to move BETWIXT, CLI, CODEC, JEXL
> > and CONFIGURATION from Bugzilla to JIRA.  JELLY is already there.
> > 
> > Are there any other Jakarta Commons projects that want to migrate?  Are
> > there any that do NOT want to leave bugzilla?
> > 
> > Right now, each "project" is a component of Commons.  If we move to JIRA, I
> > would propose that we create a Project Category for Jakarta Commons, and
> > make each component a project, so that each one can be released separately
> > with its own versioning, etc.  We could use a common scheme for permissions,
> > notifications, etc..  Jelly has a dedicate scheme, but I think we could use
> > a single scheme for all of Jakarta Commons.
> > 
> > A bugzilla import will create a single Commons project, but we can then move
> > the issues from the imported project into a new project for each of our real
> > projects.
> > 
> > For each TLP, we should probably have a single permission scheme, but I'm
> > not going to get into that argument today.  We can create
> > jakarta-administrator and jakarta-commons-developer groups.
> > 
> > 	--- Noel
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > 


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org