Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 2483 invoked from network); 31 Dec 2007 13:48:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Dec 2007 13:48:19 -0000 Received: (qmail 60081 invoked by uid 500); 31 Dec 2007 13:48:08 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 59572 invoked by uid 500); 31 Dec 2007 13:48:06 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 59561 invoked by uid 99); 31 Dec 2007 13:48:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Dec 2007 05:48:06 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of robertburrelldonkin@gmail.com designates 72.14.202.182 as permitted sender) Received: from [72.14.202.182] (HELO ro-out-1112.google.com) (72.14.202.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Dec 2007 13:47:44 +0000 Received: by ro-out-1112.google.com with SMTP id o35so525374rog.6 for ; Mon, 31 Dec 2007 05:47:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=OVLOsX7vbHQ2iaJf9TSLFYBo0kWAWXY1/ekd9tpH1dQ=; b=pfAnYk6M/kP2+iUuAZmcUKqXJhU6N4lo1yeI5dyNaIBAN8623ZiOeEEuulxmikzCLn3VDsdf+OTip28/DgfKZRgkBoJcVRGhkkbI30HgRHcWfbfBsXQYS4bha79WdJrB38J2+a6476dzoo60DytGwQ9HyNMAufjhZOeWY0x+/oA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=s4o74iE4q3w+B9Z4NSg3yvu+v6TC9xY0LUhxUK9lq0KyiF2uuCOxTFF4CVyUuKgBatOcQVvwJkvFnGQz7rCRp4HvvLm5O4KbY5eSr2txZ+m3j+Cg0smGDCKocG06hMamJfjCkU0C8aU5MwDnkiAPzOuM6Z42Z1GCifYPyL1Aczs= Received: by 10.114.161.11 with SMTP id j11mr10383037wae.127.1199108867688; Mon, 31 Dec 2007 05:47:47 -0800 (PST) Received: by 10.114.88.3 with HTTP; Mon, 31 Dec 2007 05:47:47 -0800 (PST) Message-ID: Date: Mon, 31 Dec 2007 13:47:47 +0000 From: "Robert Burrell Donkin" To: general@incubator.apache.org Subject: [POLICY] Streamline Setting+Up+a+New+Podling policy MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org http://incubator.apache.org/incubation/Incubation_Policy.html#Setting+Up+a+New+Podling falls somewhere between guideance and policy. given that process mistakes have been made (eg. https://issues.apache.org/jira/browse/INFRA-1341) IMHO it would be better to create a guide for this part of the process and streamline this section. a radical patch (below) would strip out all policy. for want of a better name, i've termed this guide 'bootstrap' (creation is already used for another part of the process) but suggestions welcomed. as discussed (http://mail-archives.apache.org/mod_mbox/incubator-general/200712.mbox/%3cf470f68e0712290934y31e65c26qe8d9758f2d3db5e1@mail.gmail.com%3e), though the current policy suggests that the mentors should do most of the work this is probably unnecessary since the IPMC has already approved it. so, i'd like to see this bit of policy removed anyway. the current policy lists mandates required infrastructure tasks (mailing lists, repository). i'm not sure that this is needed at all. if it is then it would be better to simply to ask that all proposed resources are created. the other bit is about the project status page. perhaps this does need to be explicitly stated. if so then i think it would be better to create this page as part of the 'creation' part of the process. opinions? - robert Index: site-author/incubation/Incubation_Policy.xml =================================================================== --- site-author/incubation/Incubation_Policy.xml (revision 607711) +++ site-author/incubation/Incubation_Policy.xml (working copy) @@ -288,30 +288,9 @@ Setting Up a New Podling

Once a proposal has been accepted -and the podling created -a Mentor SHOULD initiate the creation of: +and the podling created, +the Mentors SHALL bootstrap the podling.

-
    -
  • the project status page;
  • -
  • the mailing lists;
  • -
  • the repository space;
  • -
-

- Your project's mentors are able to undertake many of the setup - tasks. See notes about how to - request project resources - such as new committer accounts and new mailing lists. - (Note that a committer account will not be created - until the - Contributor License Agreement (CLA) has been recorded.) -

-

- Your project committers/PPMC members need to become familiar with - the ASF Infrastructure information - and in particular the - PMC notes. - Also see the Incubator PMC Guide. -

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