Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CE719A32.146F7%aharui@adobe.com>
References: 
 <CALEq1Z81yp7z7zRBi9MTzfdwh0wds+mZxsKoNKkk73v3NG1znQ@mail.gmail.com>
	<CE719A32.146F7%aharui@adobe.com>
Date: Wed, 2 Oct 2013 10:09:41 -0700
Message-ID: 
 <CALEq1Z_ZGoYb9fLsfgvOtm2cm1OH9Pk47zPC2Y+5WuxLC-EvVQ@mail.gmail.com>
Subject: Re: Apache project bylaws
From: Doug Cutting <cutting@apache.org>
To: general@incubator.apache.org
Content-Type: text/plain; charset=UTF-8

On Wed, Oct 2, 2013 at 9:49 AM, Alex Harui <aharui@adobe.com> wrote:
> To me, agreeing on "the norm" is not the same as policy, especially policy
> that does not allow for exceptions.

I agree.  Establishing whether there is a norm is a useful first step.
 That's what I'm trying to take.  Thus far I've seen noone disagree
that consensus is most common for committer additions at Apache.  I've
also seen folks suggest that they prefer having norms than having
explicit bylaws for their projects.  I don't anticipate any policy
being established as a result of this discussion, except perhaps
better documenting what the assumed default is for projects that don't
choose to have explicit bylaws.

> And again, to me, "consensus != unanimity".

This might be another case where better documentation would help.  In
my experience at Apache, consensus is equated with unanimity.

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org