Danny Angus wrote:
Good idea. I signed up for reorg when first announced and signed off the next day under the weight of emails.I don't know how many, if any, commiters are also on the reorg@ list, but I thought I'd FW this mail in case you're not.
Charles
To sumarise theres a feeling abroad that Apache should be less vertical and more horizontal in its organisation, that Jakarta is unbalancing things by being so big, and that "The Apache Way" is being diluted as a result (don't flame me I'm just passing it on ;).
To address this there has been a proposal that sub-projects can be elevated to full "xxxx.apache.org" project status, and as you can see from the appended message James has been suggested as a candidate.
This would involve James having its own PMC, and reporting to the board, and would benefit from higher percieved "status".
Alternatively there is also a move afoot to allow self-categorisation of projects, removing the benefit of "status" from the action of elevation to full project.
Now.. I don't know how long the internal machinations of reorg, or the Board will take, and I would be a fool if I second guessed the outcome, but out of curiosity are we generally in favour or opposed to being a top level project with our own elected PMC?
(I'll save my own opinion 'till I hear some others)
d.
-----Original Message-----
From: Nicola Ken Barozzi [mailto:nicolaken@;apache.org]
Sent: 24 October 2002 10:17
To: [EMAIL PROTECTED]
Cc: Peter Donald; Stefano Mazzocchi; Jason van Zyl; acoliver;
[EMAIL PROTECTED]; [EMAIL PROTECTED]; Steven Noels
Subject: Projects to nudge into top-level ( was Re: Concern about the
futureof Apache. )
Peter Donald wrote:
On Thu, 24 Oct 2002 08:06, Sam Ruby wrote:[...]
Peter Donald wrote:
I doubt you will see any projects leave willingly while others areI want to create an environment where those that chose to "leave the
allowed to stay behind.
nest" have every opportunity to do so, and get all the assistance that
they need in making this transition.
Have you got a list prepared of those that will be "gentlynudged out of the
nest" ?I'll start with the projects I know of that IMO would immediately be ready to be top-level and have their internal managing to do.
These are strong communities that already manage themselves and will now be able to report directly to the board IIUC.
Cocoon: XML processing system
composed of core+apps+docs
possible coordinator of the proposal: Stefano Mazzocchi
Avalon: Service Framework and Server
composed framework+containers (Phoenix, fortress, merlin, etc)
possible coordinator of the proposal: Peter Donald
Turbine: Server
composed of 2,3,Plexus, (or somewhere else later), TDK, etc
possible coordinator of the proposal: Jason Van Zyl
Maven: project management, comprehension and build system
composed of core+plugins
possible coordinator of the proposal: Jason Van Zyl
POI: M$ format libraries
composed of HDF+HSSF+...etc
possible coordinator of the proposal: Andrew C. Oliver
James: Mail Server
composed of Mailet spec, Server
possible coordinator of the proposal: Danny Angus
Slide: CMS
other non-Apache projects have asked to be part of the CMS effort
possible coordinator of the proposal: ?
Forrest: Community Tools
composed of bot, editor, site
possible coordinator of the proposal: Steven Noels
Ant:
composed of Java Ant, Nant(maybe), Centipede(maybe)
possible coordinator of the proposal: Stefan Boedwig
As for Turbine and Avalon Components I'll make a small proposal myself on the lists to make an Avalon Component space at commons.apache, as hinted on the commons.apache.list.
-0-
If anyone here on this list wants to help, please involve these communities and make a proposal ready, as previously hinted, a bit before the Apache Conference.
I hope I'll be left with no project to lobby ;-) , but if nobody else takes up this task I'll try myself.
If there are any other projects you know of that might be interested, please contact them similarly ASAP.
Let's start this flattening from the bottom! :-D
[...]
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
-- To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
