Further to Todd's point, Gerrit should not be mentioned in the bylaws as it is a mechanism, not policy.
Also, voting timeframes are usually 72 hours at the ASF, so you may want to use that. Hadoop adopted 7 days long ago, but it doesn't really gain much apart from extra waiting. Tom On Tue, Jul 19, 2016 at 12:52 AM, Todd Lipcon <[email protected]> wrote: > On Mon, Jul 18, 2016 at 1:46 PM, Jim Apple <[email protected]> wrote: > >> Please review, comment, and vote: https://gerrit.cloudera.org/#/c/3669/ >> >> I have written a draft of some bylaws for Apache Impala. They are >> mostly copied from Hadoop's bylaws, >> https://hadoop.apache.org/bylaws.html >> >> A number of the issues addressed in the bylaws are items that must be >> addressed before graduation. I am seeking PPMC feedback. >> >> According to this draft, bylaw changes require a lazy PPMC majority, >> "3 binding +1 votes and more binding +1 votes than -1 votes". Your >> vote is binding if you are on the PPMC, >> http://incubator.apache.org/projects/impala.html >> >> You can vote on this thread on the dev mailing list (archives and >> subscription info available here: >> http://mail-archives.apache.org/mod_mbox/incubator-impala-dev/) or you >> can vote on the code change itself in gerrit. >> > > One mentor comment: from an ASF perspective, official project votes must be > on the mailing list, not via gerrit. A code review "vote" is fine via > gerrit, but since this is more of an official project policy change, it > should be done via email. > > Of course, commenting on and revising the bylaws using gerrit as a forum > for easy discussion/review should be fine, so long as the end item is voted > on. > > I'd also suggest that the comment/review/discussion be left open a couple > days, and only once it appears people are done making comments, call the > official VOTE. Otherwise, people are voting on a (potentially) changing > artifact, which strikes me as odd. > > >> >> The vote will remain open for 7 days, until July 25th. If there is >> Lazy Majority at that point, I will commit this change in gerrit and >> ask a committer to git push it to the asf-site branch in our ASF repo, >> which will put this document on the website http://impala.apache.org/. >> >> If there is not Lazy Majority, I will revise the document and >> re-submit it for a vote. >> >> The bylaws can be changed again later by the same procedure. >> > > > > -- > Todd Lipcon > Software Engineer, Cloudera
