----- Original Message -----
From: "Geir Magnusson Jr." <[EMAIL PROTECTED]>
To: "jakarta-commons" <[EMAIL PROTECTED]>
Sent: Monday, April 16, 2001 7:50 PM
Subject: [DISCUSSION] new committer rules
> This morning Jason Van Zyl was added as a committer to jakarta-commons.
> You all should know Jason - he founded the Velocity project, is an
> over-active participant in the Turbine project, a member of the Jakarta
> PMC, and knows now to wear eye protection when playing squash.
>
> He was a sandbox committer for the Configuration component - when it was
> merged with the approved Collections component, it seemed natural that
> he would follow it into jakarta-commons to continue participation.
>
> While I believe that this was a perfectly appropriate way to do it
> because of the unique circumstances of a sandbox merge at the same time
> as the move to the main CVS, it brings up some questions, and I think we
> should discuss this.
>
> In no order :
>
> 1) Can a set of component committers add a committer for their
> component? For example, supposing Jason was new, could Craig, Vincent
> and myself simply voted him in? I believe that is generally appropriate
> - currently, the components are a bit small, w/ the exception of cactus,
> but this will change over time.
>
good question.
As there is no component-specific resources allocated for a given component
I would say the decision belongs to jakarta-commons in general. It may
change over time when some of the components get bigger and get some
resources of their own. I think we should follow the general apache rules
and vote for addition of a new committer, explaining what this new person
has done and why he is being added.
Also, I already know 2 or 3 persons who are developing extension for Cactus
(one person is developing the support of EJBs for unit testing them). These
persons would like to participate to Cactus but may not want to participate
to jakarta-commons in general. I guess, in due time, I'll propose them to
the commons mailing list for working on Cactus.
> 2) If so, then because of the common main CVS, that person is now able
> to participate in all components with the 'edit the STATUS file' bit.
>
> Is this what people expect?
>
Is it possible to restrict user access by submodule/directory in CVS ?
> geir
Vincent
