[ 
http://issues.apache.org/jira/browse/INCUBATOR-44?page=comments#action_12431699 
] 
            
Robert Burrell Donkin commented on INCUBATOR-44:
------------------------------------------------

> One of the issues I've noticed in incubation is that the incubating project 
> often does not know 
> who can help in what area. 

good point

need to address this comprehensively somewhere in the documentation: possibly 
the FAQ or in a separate document.

> The trouble with the proposed patch is that it removes any clue as to 
> who might be the usual party to request help.

good point

> Maybe a better resolution would be to identify the responsible party for each 
> of the tasks noted:

i'd assumed that a Mentor would always do these tasks (see 
https://issues.apache.org/jira/browse/INCUBATOR-42). 

>Setting up the svn repo:
>
>The general "requesting resources" page says, "New projects will need to ask 
>for their 
> SVN-space to be created. Send to [EMAIL PROTECTED] and Cc your PMC. 
> Add an issue to Jira in the "Subversion" category." What it doesn't say is 
> who usually does the 
> request.
>
> Creation of mailing lists:
>
> The general "requesting resources" page says, "Gather the required 
> information about the new 
> lists. This includes the precise name and domain, the email addresses of the 
> people who will be 
> moderators (ideally three+ and well spread). Send to [EMAIL PROTECTED] and Cc 
> your PMC. 
> Add an issue to Jira in the "Mailing Lists" category."
>
> Who would normally be expected to submit the request?

good question :-)

it's been quite laissez-faire in the past but that's probably not a good answer 
going forward

probably the answer should be something like: anyone on the PMC can but 
typically the PMC chair will

probably would be good to add that to the document

> There is no detail on how to add an issue to which jira. Maybe a direct 
> reference to the correct 
> jira would help here.

+1

submit a patch :-)

for the www.apache.org site, use INFRA with component website

https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10410&sorter/order=DESC&sorter/field=priority&resolution=-1&component=11708

- robert

> [policy neutral] cut discursive material better handled in the guides
> ---------------------------------------------------------------------
>
>                 Key: INCUBATOR-44
>                 URL: http://issues.apache.org/jira/browse/INCUBATOR-44
>             Project: Incubator
>          Issue Type: Improvement
>          Components: policy
>            Reporter: Robert Burrell Donkin
>         Assigned To: Robert Burrell Donkin
>
> Cuts non-policy discursive material that is better located in the guides.
> This change is intended to be policy neutral.
> Index: site-author/incubation/Incubation_Policy.xml
> ===================================================================
> --- site-author/incubation/Incubation_Policy.xml        (revision 437587)
> +++ site-author/incubation/Incubation_Policy.xml        (working copy)
> @@ -285,21 +285,9 @@
>            <li>Incubator PMC mandating a helper Mentor</li>
>          </ul>
>          <p>
> -          Your project's mentors are able to undertake many of the setup
> -          tasks. See notes about how to
> -          <a href="http://www.apache.org/dev/reporting-issues.html";>request 
> project resources</a>
> -          such as new committer accounts and new mailing lists.
> -          (Note that a committer account will not be created
> -          <a href="http://www.apache.org/dev/pmc.html#newcommitter";>until the
> -          Contributor License Agreement (CLA) has been recorded.</a>)
> -        </p>
> -        <p>
> -          Your project committers/PPMC members need to become familiar with
> -          the <a href="http://www.apache.org/dev/";>ASF Infrastructure 
> information</a>
> -          and in particular the
> -          <a href="http://www.apache.org/dev/#pmc";>PMC</a> notes.
> -          Also see the <a href="../guides/pmc.html">Incubator PMC Guide</a>.
> -       </p>
> +          See <a href="http://www.apache.org/dev/reporting-issues.html";>how 
> to</a> 
> +          request project resources. 
> +         </p>
>       </section>
>        <section id="Ongoing+Activities">
>          <title>Ongoing Activities</title>
> Index: site-publish/incubation/Incubation_Policy.html
> ===================================================================
> --- site-publish/incubation/Incubation_Policy.html      (revision 437587)
> +++ site-publish/incubation/Incubation_Policy.html      (working copy)
> @@ -376,21 +376,9 @@
>            <li>Incubator PMC mandating a helper Mentor</li>
>          </ul>
>  <p>
> -          Your project's mentors are able to undertake many of the setup
> -          tasks. See notes about how to
> -          <a href="http://www.apache.org/dev/reporting-issues.html";>request 
> project resources</a>
> -          such as new committer accounts and new mailing lists.
> -          (Note that a committer account will not be created
> -          <a href="http://www.apache.org/dev/pmc.html#newcommitter";>until the
> -          Contributor License Agreement (CLA) has been recorded.</a>)
> -        </p>
> -<p>
> -          Your project committers/PPMC members need to become familiar with
> -          the <a href="http://www.apache.org/dev/";>ASF Infrastructure 
> information</a>
> -          and in particular the
> -          <a href="http://www.apache.org/dev/#pmc";>PMC</a> notes.
> -          Also see the <a href="../guides/pmc.html">Incubator PMC Guide</a>.
> -       </p>
> +          See <a href="http://www.apache.org/dev/reporting-issues.html";>how 
> to</a> 
> +          request project resources. 
> +         </p>
>  </div>
>  <h3>
>     <a name="Ongoing+Activities">Ongoing Activities</a>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to