Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of justin.erenkrantz@gmail.com
 designates 64.233.162.203 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=DP3q6gSSXiWro6dsatK9hasujaGWKRGjoPbgaa9yVPYFTvXzuWyOF+GTILfkArk5T81usldj7sM6WRmTzMkGm6U/CclNL+EDEsN2+n+Zpy9vsZ2lnvcX3zVvMJoJFY0084GH58QM7U+rsnmk36Ba84+fPIanOxdM/w0RYmMi4gw=
Message-ID: <5c902b9e0603151503h2cdd6964m3646fe88bc0c7548@mail.gmail.com>
Date: Wed, 15 Mar 2006 15:03:18 -0800
From: "Justin Erenkrantz" <justin@erenkrantz.com>
Sender: justin.erenkrantz@gmail.com
To: general@incubator.apache.org
Subject: Re: [doc] Incubation Policy -> "Acceptance of Proposal by Sponsor"
Cc: jta@bristowhill.com
In-Reply-To: <44189851.9050603@toolazydogs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <44179265.9000608@bristowhill.com>
	 <5c902b9e0603142108r1509ecd9j5b54830946e6cee2@mail.gmail.com>
	 <441874C4.8010407@toolazydogs.com>
	 <5c902b9e0603151334n2375e0b3x359a2c9b3f1f8886@mail.gmail.com>
	 <44189851.9050603@toolazydogs.com>

On 3/15/06, Alan D. Cabrera <list@toolazydogs.com> wrote:
> I can extrapolate from past behavior on important podling votes.  My
> reservations are fair and based on past behavior.

No one other than an Incubator PMC member can acknowledge receipt of a
message intended for the Incubator PMC.  The notice message should be
sent to general@incubator.  If tardiness of the entire PMC becomes an
issue, we deal with it at that point.  However, I disagree that
tardiness is a pervasive issue.

> I agree with your statement about code imports but I didn't realize that
> they could stop a podling from being created.  IIUC, the Incubator PMC
> has final say on graduation but not on initiation.  Am I wrong in this
> understanding?

The Incubator PMC exists to ensure that all policies and procedures
are enforced for code donations and imports.  If a PMC member has a
procedural question, it must be cleared up before the podling is
created.  For example, the sponsoring PMC may state that they want to
import code into Subversion under the GPL.  That's clearly a no-no and
should be stopped sooner rather than later.

> While I agree that this would be unlikely and that common sense should
> govern the behavior of good cooperative communities, are we not writing
> policy?

Your suggestion removes the Incubator PMC's ability to perform oversight.

In the hypothetical example above with importing GPL (or some other
procedural/policy violation), the Incubator PMC can and should have
the authority to stop the sponsoring PMC from creating such a podling.

Now, what I am stating (and perhaps confusing the issue for you) is
that the Incubator PMC shouldn't be making technical judgments (such
as "no one wants X" or "I don't like Y") - but it has the
responsibility to ensure policies and procuedres are followed.  This
is why podlings can't perform any releases without the explicit
approval of the Incubator PMC.  The Incubator was created by the Board
to ensure our policies are followed.  -- justin

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