james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danny Angus" <da...@apache.org>
Subject RE: Straw poll : FW: Projects to nudge into top-level ( was Re:Concern about the futureof Apache. )
Date Thu, 24 Oct 2002 17:42:56 GMT
As I understand it there is the potential for Jakarta projects to apply to "jump-ship" now,
irrespective of the outcome of the reorg.

> -----Original Message-----
> From: Serge Knystautas [mailto:sergek@lokitech.com]
> Sent: 24 October 2002 18:07
> To: James Developers List
> Subject: Re: Straw poll : FW: Projects to nudge into top-level ( was
> Re:Concern about the futureof Apache. )
> 
> 
> I think it could help James to have it promoted, but am not sure about 
> the impact of making that many projects higher level.  The value of that 
> top status is diminished if you allow too many.  As an alternative, you 
> could split jakarta into the three categories specified on the home page 
> (libraries/tools/API, frameworks/engines, and server applications).  To 
> me it depends on the priorities driving the reorg... whether it's to 
> keep jakarta for more fledging code, to improve communication between 
> projects, to improve visibility for more mature code, or what have you.
> 
> Anyway, I'm on the mailing list (well, the new community@ list), and if 
> there is a move to push some jakarta projects to top level, I'd like to 
> see James moved as well.  I'm just not sure yet if that exact reorg is 
> the best.
> 
> -- 
> Serge Knystautas
> Loki Technologies - Unstoppable Websites
> http://www.lokitech.com
> 
> Danny Angus wrote:
> > 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.
> > 
> > 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.
> 
> 
> --
> 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>


Mime
View raw message