Technically, I think you're right. I read this half a dozen times before sending my previous email, and with another half a dozen reads, I'm still confused but now leaning towards your interpretation. I was deriving significance from the term "lazy", although it's never defined in the document.
As for a clarification, you'll have to request one from the Jakarta PMC. From my memory, I thought voting used to be typically majority-style. But from this doc, a release plan and a release testing are the only actions that are to use this vote-style. All others should ultimately be consensus. I have to think this is backwards... changing CVS requires consensus but making a release doesn't?
Anyway, kudos on being a committer. I firmly believe the ASF has produced so much great stuff, and it's because it has the right style... from licensing model to decision making approach to project proposal credentials to culture. I think the interpretations and the future re-org are relatively minor and just clarifying what's largely already in place. (saying the rules and regs aren't heavy and not a big part of the culture, imho.)
--
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
Noel J. Bergman wrote:
a code change [only needs] a majority vote (even a -1 isn't blocking).Please explain this. Because I really want to understand, and I had understood it differently. From http://jakarta.apache.org/site/decisions.html: "Changes to the products of the Project, including code and documentation, will appear as action items in the status file. All product changes to the currently active repository are subject to lazy consensus." I'd interpreted this to say that CVS changes are subject to lazy consensus. And the document says that "[an] action requiring consensus approval must receive at least 3 binding +1 votes and no binding vetos." Please explain where I missed the point, and where I can find more illuminating information. I figure that between my being a new Committer, the talk about a PMC, and having to stand in front of 600 people in 10 days talking about all of the wonderful Java technologies from Apache, it is probably a good idea to get more clarity on Apache's rules and regs. :-) Thanks! :-) --- Noel
-- To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
