I would say that the (hints of) examples presented, especially meaning deviation of the general 'guideline' of a simple majority vote for (procedural) aspects would be enough reason for any aspiring ASF project to do just to all to have a set of bylaws.
Despite all the ASF pages to make its philosophies interpretable in only one way, I hear/see a lot of variants of what is the Apache Way or the Apache Code of Conduct from various - fellow - ASF politicians (pun intended :-)). It is bylaws that decrease the ambiguity instilled in the ASF pages, ensuring that due process is or can be established, that every contributor can expect rules to be applied equally to all. Guidelines, as some of the esteemed Members of the ASF or participants in this discussion seem to regard the policies of the ASF, don't deliver that. Remember, like Sarbanes-Oxley intended with respect to how enterprises conduct their business , per project bylaws feed into the aspect of compliance to the ASF doctrine or explain when deviating on points. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Jul 6, 2015 at 10:18 AM, Bertrand Delacretaz <bdelacre...@apache.org > wrote: > Hi, > > On Sun, Jul 5, 2015 at 6:30 AM, Pierre Smits <pierre.sm...@gmail.com> > wrote: > > ....if a project wants to deviate from the general rule of a simple > > majority voting for specific aspects - think off changing the direction > or > > goal of the project, or e.g. every registered contributor (iCLA filed) > has > > a vote with respect of onboarding new PMC Members - this must be > > incorporated in the bylaws of a project.... > > This makes me feel like there you have an actual case behind this > whole discussion. > > If that's correct, it might be easier to discuss the actual case > rather than higher level and more abstract things. > > -Bertrand >
