It is intended to be a "technical discussion", in the sense of the bylaws statement (in section "Roles and Responsibilities: Committers"), "Committers may cast binding votes on any technical discussion regarding any subproject." I therefore intended it to be a majority vote of Committers.
Interestingly, this need to discuss tooling and other issues that go beyond a simple "code change" is not addressed in the "Decision Making: Actions" section of the bylaws. That need seems to have been overlooked in the current rev of that section. But I do not agree that such issues are "code changes"; it relates to the tools we depend on to make code changes, which is clearly qualitatively different. --Matt On Mon, Dec 3, 2012 at 10:37 AM, Doug Cutting <cutt...@apache.org> wrote: > On Sat, Nov 24, 2012 at 12:13 PM, Matt Foley <ma...@apache.org> wrote: > > Vote closes at 12:30pm PST on Saturday 1 December. > > It's not clear to me what kind of a vote this is. It seems closest to > a code change vote, since it implies code changes, although without a > specific patch yet proposed. As such it would follow lazy consensus > rules. Or is it merely intended as a straw poll, to gauge community > opinion? > > Doug >
