Folks, Would like to establish and follow very early on the bylaws under which we will operate. Projects such as Accumulo, CloudStack, Pig, and Kafka have very similar bylaws with minor differences:
[References] https://accumulo.apache.org/bylaws.html http://hadoop.apache.org/bylaws.html https://cwiki.apache.org/confluence/display/KAFKA/Bylaws http://cloudstack.apache.org/bylaws.html http://pig.apache.org/bylaws.html [My opinion] I think we should adopt Accumulo's bylaws almost directly. What I would suggest we remove is the custom to have committers invited to the PMC. I think the staged progression to the PMC is important. Recommend we also do the same for a release guide. Again Accumulo offers a very good example: https://accumulo.apache.org/governance/releasing.html And finally we should clearly define a few terms: API: We should clearly call out what is the public API and the internal API. Changes to the public API are very sensitive in nature as they can disturb the user base. Changes to the private/internal API however are important to allow internal implementation to evolve. Versioning Scheme: x.y.z Where X = Massive? Y = Major Z = Minor Look forward to any thoughts. None of this needs to be solidified at this very early stage for our project. But it is important to establish something as a basis of further discussion and iteration. Happy Thanksgiving. Joe
