commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <robertburrelldon...@blueyonder.co.uk>
Subject Re: [PATCH] AdaptorRegistry
Date Sat, 08 Mar 2003 16:46:45 GMT
On Friday, March 7, 2003, at 03:55 PM, Howard M. Lewis Ship wrote:

> Since I'm a Jakarta committer, I can be a Commons committer by default 
> (from
> what I've read).  Still I'd prefer to be "invited" to move code from
> Tapestry to commons.

hi howard

i'm sure what you've read where but IMHO it's easy to get confused between 
what-jakarta-might-become and what-it-is-now. this also applies to the 
commons. here's my understanding of the current position.

any jakarta committer can request karma for the sandbox and have it given 
without question. (since the commons has responsibility for the oversight 
of the sandbox, this karma could probably be withdrawn if abused - but it'
s never come anywhere near to that.) the sandbox gives jakarta committers 
freedom to experiment.

the rules for commons committership are the same as other jakarta 
sub-projects. (at the moment) this means by popular election by their 
peers. the convention is that committers are elected for their work on a 
particular component or components.

what can throw people a little is that here in the commons we're pretty 
strong on keeping components within their stated aims. we also have had 
(historically) a high barrier to entry for new components. (one reason for 
this is that we have limited resources but a collective responsibility for 
all commons components.)

(i'm not trying to discourage you, it's just IMHO it's easier to get 
things straight in advance.)

- robert


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


Mime
View raw message