On Feb 13, 2008, at 1:38 PM, Bertrand Delacretaz wrote:
> On Feb 13, 2008 1:09 PM, William A. Rowe, Jr. <wrowe@rowe-clan.net>
> wrote:
>
>> ... In projects where commit is handed out with ease, and that
>> commit is
>> never used, at some point it should be reviewed (and this should
>> happen
>> BEFORE graduation, as a precondition of graduation, not as a trigger
>> upon graduation)....
>
> Agree with this, and this is similar to what I was initially
> suggesting.
>
> Several of us in this thread think that this review of commit rights
> should not be a re-election as initially suggested, but rather a
> process that the podling mentors can run as they see fit: maybe not at
> all if all committers are obviously active, by election if desired, or
> in any suitable way.
>
> Do people agree on leaving this up to podling mentors, and requiring
> that they report on this commit rights review in the podling's
> graduation request?
I definitely think it's a mentor-driven process that deserves a
sentence in the graduation request, right along side "meritocracy" and
"independent committers".
Craig
>
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
|