Noah, thanks for putting this together and the approach. I really like the Cloudstack by-laws. I think we could just copy them with some minor changes. Here are some questions or comments (on https://cloudstack.apache.org/bylaws.html):
2.4.1.2. I am not sure if the PMC has to approve the releases. In our case it is a vote on dev@. 2.4.6. As for today, we do not have a chair rotation but iirc, we have already spoken about this as a possibility 3.1.2.4 I was not aware that a -1 needs an explanation 3.2. Approvals - maybe we have to adjust the numbers. 3 is kinda low I think compared to how many PMC members and committers we have 3.3. Vetoes - this point is fairly new to me and I would love to see areal example 3.4.1. Technical Decisions - it first states that technical decisions should made by voting but later it is described how it should be done when a vote was started. It's a bit contrary. In 3.4.2 there is a reason described for the need of a vote if there is a dispute of finding consensus. Then I am not sure if we "live" this already but I like it "Any user, contributor, committer, or PMC member can initiate a technical decision making process.". 3.4.4. Product Release - if we follow our now active process, this has to be changed imo. 3.4.5. Adoption of New Codebase this would be new for CouchDB but is maybe a good idea I am not sure if the CoC acceptance has to mentioned in this paper also. Cheers Andy On 28 April 2014 21:53, Noah Slater <[email protected]> wrote: > I'd like to propose that we vote in a set of project by-laws. > > This document will define the specific roles in this community, as > well as the decision making procedures we use. > > Right now, most of the rules are in my head. The reasons for this are > historical. Our mentors were absent, and we sort of figure out a > rudimentary set for ourselves. Later, when I joined the incubator, I > started to pick up lots of things we were missing. > > Instead of me repeating things and being a single point of failure > here, I'd like to get everything down "on paper" and make it official. > > I propose something very similar to, if not identical to, CloudStack's > by-laws: > > https://cloudstack.apache.org/bylaws.html > > (Which I helped draft.) > > -- > Noah Slater > https://twitter.com/nslater > -- Andy Wenk Hamburg - Germany RockIt! http://www.couchdb-buch.de http://www.pg-praxisbuch.de GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc
