I see little need for an additional "Bylaws". I think following the foundation guidelines are all that 90% of projects need for their day to day lives: <http://www.apache.org/foundation/voting.html>
I think adding an additional bylaws about exceptional things are not needed. Don't build policies and processes around things that shouldn't be happening -- and so far haven't needed to happen. If the project is healthy, it shouldn't need to ever refere to the bylaws for the definition of consensus. If the project is in trouble, then sure, add process, add rules, add bylaws, but by default, leave it open, let people do things without constraints. Consensus is the community working together on a shared vision, it is not about voting and waiting 7 days to see if no one sends a -1. Its about convincing your peers that a technical decision is the right one. Thanks, Paul On Sun, Nov 7, 2010 at 7:40 PM, Leif Hedstrom <zw...@apache.org> wrote: > Hi all, > > I've not received any further comments or suggestions on the proposed Bylaws > document, so I would like to start the vote for this. This is an important > issue, so I urge all PMC members, and the entire community to read the > proposal, and vote. Please cast your vote (please vote!), +1, -1 or 0 within > the next 72 hours. > > In particular, make sure you are OK with the vote requirements in this > proposal. For example, a release artifact is only releasable if there's lazy > majority (at least 3 +1 binding votes, and more +1's than -1's). So vote! > :). > > Thanks, > > -- leif > > https://cwiki.apache.org/confluence/display/TS/BylawsDraft >
