--- Simon Kitching <[EMAIL PROTECTED]> wrote:
> 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).

-0
I don't have any problems with using bugzilla and other installations
(like Red Hat's site) show that bugzilla's interface can be customized and
cleaned up quite a bit.  I don't understand why free Apache projects
should use non-free bug tracking software.  If it ain't broke, don't fix
it.

David

> 
> 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: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to