incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1771988 - in /incubator/public/trunk/content/guides: graduation.xml proposal.xml
Date Wed, 30 Nov 2016 02:12:31 GMT
Author: johndament
Date: Wed Nov 30 02:12:31 2016
New Revision: 1771988

Clarified mentor participation in a podling.  Moved maturity model out of checklist and into
other issues section.


Modified: incubator/public/trunk/content/guides/graduation.xml
--- incubator/public/trunk/content/guides/graduation.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/graduation.xml [utf-8] Wed Nov 30 02:12:31 2016
@@ -42,8 +42,8 @@
-                    This is just a guide. Policy is stated 
-                    <a href=''>here</a>.
+                    <b>This is just a guide. Policy is stated 
+                    <a href=''>here</a>.</b>
                   Help to improve the system by posting a patch for
@@ -186,9 +186,6 @@
                                 have no <a href='#notes-issues'>remaining issues</a>
-                            <li>
-	                            Complete the <a href=""
target="_new">Apache Project Maturity Model</a>
-	                        </li>
@@ -424,8 +421,11 @@
                     are trusted to evolve process and policy. This guide
                     can only document the most common issues and it is
                     possible that there are other concerns that may require
-                    resolution that are not covered. 
+                    resolution that are not covered.
+              <p>
+	      Podlings who are unsure if they are ready to graduate may want to consider completing
the <a href=""
target="_new">Apache Project Maturity Model</a>.  You may find this to be a useful
guide when looking at various factors in your podling's community.
+	          </p>
         <section id="process">

Modified: incubator/public/trunk/content/guides/proposal.xml
--- incubator/public/trunk/content/guides/proposal.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/proposal.xml [utf-8] Wed Nov 30 02:12:31 2016
@@ -1011,24 +1011,9 @@ Lists <a href="&root-path;/incubation/In
 individuals nominated as <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>

 [<a href="&root-path;/incubation/Incubation_Policy.html#Mentor">definition</a>]
for the candidate.
-                    <p>
-It is common for additional Mentors to <a href='participation.html#mentors'>volunteer</a>
their services
-during the development of the proposal. The number of Mentors for a Podling is limited only
by the
-energy and interest of those eligible to Mentor. Three Mentors gives a quorum and allows

-a Podling more autonomy. The current consensus is that three or more Mentors makes the
-incubation process run more smoothly.
-                </p>
-                <p>
-Note that since Mentors are appointed by the 
-<a href="&root-path;/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">
-Incubator PMC</a> 
-at the end of the acceptance process, they have no formal role until the proposal is accepted.

-But informal enthusiasm from nominee Mentors is taken as a good sign.
-				</p>
-				<p>
-There is no restriction on the number of informal mentors (note the small <em>m</em>)

-that a Podling may have. These can be very useful but have no formal role in the process.
-				</p>
+	<a href='participation.html#mentors'>Three Mentors</a> gives a quorum and allows
a Podling more autonomy from the <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
PMC</a>, so the current consensus is that three Mentors is a good number. Any experienced
Apache community member can provide informal mentorship anyway, what's important is to make
sure the podling has enough regularly available mentors to progress smoothly.  There is no
restriction on the number of mentors, formal or informal, a Podling may have.
             <section id='template-sponsoring-entity'><title>Sponsoring Entity</title>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message