What about jakarta-commons-sandbox projects? Note that there is potential for a name overlap problem, e.g. jakarta-commons [myproject] and a jakarta-commons-sandbox [myproject], although I do not believe this is currently the case.
michael On Mon, 12 Jan 2004, 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]
