72 hours suffices; this gives everyone a workday to respond in the worst case, no matter where they live. We will seldom ask deep philosophical questions which require days of study to answer. We can always re-vote in situations where someone feels short-changed by a late Friday vote.
On Tue, Jul 30, 2013 at 10:05:07AM -0700, Andrew Bayer wrote: > It's not business hours - technically, by normal Apache standards, it's > just 72 hours. But it may make sense to amend that to 72 hours excluding > weekends? > > A. > > On Tue, Jul 30, 2013 at 9:52 AM, Everett Toews > <[email protected]>wrote: > > > Sorry I didn't catch it before but do we need to specify "72 business > > hours" instead of just "72 hours" in the 3.5. Voting Timeframes section? > > > > My understanding has always been that it's business hours. Apache Voting > > [1] isn't any more specific on the subject. > > > > Would making that change mean we need a new vote? > > > > Everett > > > > On Jul 30, 2013, at 10:58 AM, Andrew Bayer wrote: > > > > > Ok, let's have a vote on the proposed project bylaws at > > > https://wiki.apache.org/jclouds/Bylaws. The vote will operate by the > > lazy > > > 2/3 majority standard specified in the bylaws themselves) (at least 3 > > > binding +1s, and at least twice as many binding +1s as binding -1s). The > > > vote will be open for 72 hours - i.e., until 9am PDT on Friday, August > > 2nd. > > > Any committer or mentor has a binding vote. Thanks! > > > > > > I am +1 binding, fwiw. > > > > > > A. > > > > -- Andrew Gaul http://gaul.org/
