Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of gstein@gmail.com designates
 209.85.212.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <9511FA99-F12B-453D-8CEF-B991197E9C00@yahoo.com>
References: <CE72EC46.1490E%aharui@adobe.com>
	<9511FA99-F12B-453D-8CEF-B991197E9C00@yahoo.com>
Date: Fri, 4 Oct 2013 14:47:41 -0500
Message-ID: 
 <CABD8fLWAcA0iYzQNUZ5rLzEG7pMmm=dEXVwTez_uPoknb=K6EA@mail.gmail.com>
Subject: Re: Apache project bylaws
From: Greg Stein <gstein@gmail.com>
To: general@incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11c3494a5174ce04e7ef9357

--001a11c3494a5174ce04e7ef9357
Content-Type: text/plain; charset=ISO-8859-1

On Oct 3, 2013 12:52 PM, "Joseph Schaefer" <joe_schaefer@yahoo.com> wrote:
>...
> e.g. how to vote properly
> on personnel issues, and that should entirely suffice. Even Greg
> doesn't seem to know what consensus voting means in this context,

Really, Joe? Why did you throw that in? I know what consensus voting is. I
also know some PMCs allow vetoes when adding new members. That was the
point of my prior email: you are right that committership is done by
consensus across the ASF, but that doesn't strictly hold for PMC
membership. I think Roy phrased it once as "I am allowed to veto/refuse to
work with that person. They are free to copy the codebase and establish a
community of people willing to work with that person."

Cheers,
-g

--001a11c3494a5174ce04e7ef9357--