That's a reasonable argument, and I won't argue with you on it.
On Fri, Apr 4, 2014 at 11:56 AM, John Vines <vi...@apache.org> wrote: > The current line is unacceptable. It can also be implied that every single > code change needs to be up for review before it can be committed. It had > been contested in the last vote with no clarity on what it meant, leaving > others questioning whether it should not be there. > > Yet, in spite of that, it was implored that we should pass the bylaws > anyway and then amend after the fact. Given the turn around on bylaw > changes and the time it would take to sort this matter out, I decided it's > best to take out this potentially malicious line from our bylaws until > something a more sound can be put in place. > > > On Fri, Apr 4, 2014 at 11:49 AM, Bill Havanki <bhava...@clouderagovt.com > >wrote: > > > -1 > > > > Removing the line with no substitute is unacceptable. It can be implied > > that code changes are not subject to review and/or community approval, > > without the alluded-to commit and review standard in place. I doubt any > > Apache project's bylaws omit the line (checked: Hadoop, HBase, Hive, > > ZooKeeper, Pig). > > > > It's better to work the commit and review policy, and then update the > line > > accordingly. > > > > Also, the rule has also been in place for less than two hours. Really. It > > hasn't even proven to be a problem yet. This drama is unbecoming to our > > community. > > > > Bill H > > > > > > On Fri, Apr 4, 2014 at 11:36 AM, Christopher <ctubb...@apache.org> > wrote: > > > > > +1 > > > > > > -- > > > Christopher L Tubbs II > > > http://gravatar.com/ctubbsii > > > > > > > > > On Fri, Apr 4, 2014 at 11:18 AM, Josh Elser <josh.el...@gmail.com> > > wrote: > > > > +1 > > > > > > > > Minor correction, the bylaws currently state "version 0" so it should > > be > > > > replaced with "version 1". > > > > > > > > > > > > On 4/4/14, 11:04 AM, John Vines wrote: > > > >> > > > >> This is a proposal to strike the code change action from the bylaws. > > > This > > > >> is being requested because there is substantial ambiguity about the > > > >> standards being declared / whether this should be part of our bylaws > > > and, > > > >> until these are clarified, should be removed. > > > >> > > > >> Specifically, it is the following line which shall be removed > > > >> > > > >> Code Change A change made to a codebase of the project. This > includes > > > >> source code, documentation, website content, etc.Lazy approval, > moving > > > to > > > >> consensus approval upon vetoActive committers1 > > > >> > > > >> > > > >> The current bylaws are visibile at > > > >> > > > >> http://accumulo.apache.org/bylaws.html > > > >> > > > >> This vote will be open for 7 days, until 11 April 2014, 15:10 UTC. > > > >> > > > >> Upon successful completion of this vote, the first line of the > > document > > > >> body > > > >> will be replaced with "This is version 2 of the bylaws," and the > > > >> aforementioned line will be removed. > > > >> > > > >> This vote requires majority approval to pass: at least 3 +1 votes > and > > > more > > > >> +1 > > > >> than -1's. > > > >> > > > >> [ ] +1 - "I approve of these proposed bylaw changes and accept them > > > >> for the Apache > > > >> Accumulo project." > > > >> [ ] +0 - "I neither approve nor disapprove of these proposed bylaw > > > >> changes, > > > >> but accept them for the Apache Accumulo project." > > > >> [ ] -1 - "I do not approve of these proposed bylaw changes and do > not > > > >> accept them for the Apache Accumulo project because..." > > > >> > > > >> Thank you. > > > >> > > > > > > > > > > > > > > > -- > > // Bill Havanki > > // Solutions Architect, Cloudera Govt Solutions > > // 443.686.9283 > > > -- // Bill Havanki // Solutions Architect, Cloudera Govt Solutions // 443.686.9283