On Sep 30, 2013 4:19 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > Hi, > > Looks like as part of the graduation process that we didn't get together and come up with a list of bylaws for Apache Flex. > > Some example Apache project bylaws: > http://hadoop.apache.org/bylaws.html > http://cloudstack.apache.org/bylaws.html > https://cwiki.apache.org/confluence/display/Hive/Bylaws > https://cwiki.apache.org/confluence/display/KAFKA/Bylaws > http://ant.apache.org/bylaws.html > > As well as listing out the roles and responsibilities on the project it needs to spell out the voting rules. > > Here's some of the things we would need to reach consensus on. If PMC members (and others) could indicate > their preferences to there questions below we'll start getting a document together based on this what other > Apache projects have done. >
Here are my preferences: > If you have no strong preference indicate that and this is not a vote, just more of what you think bests fits in our > community. > > 1. Voting procedure for committers > a) lazy-majority (more +1s than -1s) > b) lazy-consensus (no -1's) > c) consensus (3 +1's no -1's) > c. > 2. Voting procedure for PMC members > a) lazy-majority (more +1s than -1s) > b) lazy-consensus (no -1's) > c) consensus (3 +1's no -1's) > d) 2/3 majority (3 +1's and twice an many +1 as -1) c. > > 3. Voting procedure for Chair > a) lazy-majority (more +1s than -1s) > b) lazy-consensus (no -1's) > c) consensus (3 +1's no -1's) > d) 2/3 majority (3 +1's and twice an many +1 as -1) > c. > 4. Length of term of Chair > a) until they resign > b) 1 year > d) reviewed every year with option to continue > c) other a or d > > 5. Voting procedure on changing bylaws > a) lazy-majority (more +1s than -1s) > b) lazy-consensus (no -1's) > c) consensus (3 +1's no -1's) > d) 2/3 majority (3 +1's and twice an many +1 as -1) c. > > I notice other Bylaws use the word active a lot eg "active PMC", "active committers", but don't seem to define it. > Should we try and define or at least give some guidelines what an active person on the project is? I think we should. Although I am not sure what the distinction means. Are you thinking of restricting voting privileges to non active PMC? > There seems to be a vague "not contributing to the project for 6 months" in one or two of the existing bylaws. > > There are several other thing in the bylaws eg removal of PMC or committer but as they are hopefully unlikely to > happen so I can't see consensus being hard to reach there. IMHO, there are way too many committers/PMC members who have not contributed anything since the project started. Maybe, we should check once in a while to see if they are still around. Thanks, Om > > I assume once we have a complete document put together we would need to take a vote and inform the board. > > Thanks, > Justin
