> From: Sam Ruby [mailto:[EMAIL PROTECTED]] 
> 
> Leo Sutic wrote:
> 
> > Avalon does not need the consensus of Jakarta-Commons, we can vote 
> > ourselves. At the same time, I don't want one person creating a 
> > subproject of Avalon, declaring that he owns that code and that his 
> > own opinion is equal to concensus.
> > 
> > In short, is there any way to decouple Phoenix from Avalon
> > in such a way so that *all* PMC members need not vote on
> > *every* change to Phoenix, yet keep Phoenix from sliding
> > away to a little isolated group of its own?
> 
> A point of order.  No PMC member is *ever* required to vote on *any* 
> specific change.  If what you desire is a mechanism by which 
> a specific 
> PMC member is *excluded* from voting on a specific change, 

No. I meant *required to vote* as in: "Being responsible for the code".
If no such requirement exists, then I'm fine.

Thanks for clearing that up.

/LS


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to