incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r536657 - in /incubator/public/trunk: site-author/guides/graduation.xml site-publish/guides/graduation.html
Date Wed, 09 May 2007 21:17:13 GMT
Author: rdonkin
Date: Wed May  9 14:17:12 2007
New Revision: 536657

URL: http://svn.apache.org/viewvc?view=rev&rev=536657
Log:
Improved linking.

Modified:
    incubator/public/trunk/site-author/guides/graduation.xml
    incubator/public/trunk/site-publish/guides/graduation.html

Modified: incubator/public/trunk/site-author/guides/graduation.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/graduation.xml?view=diff&rev=536657&r1=536656&r2=536657
==============================================================================
--- incubator/public/trunk/site-author/guides/graduation.xml (original)
+++ incubator/public/trunk/site-author/guides/graduation.xml Wed May  9 14:17:12 2007
@@ -97,7 +97,8 @@
                                 </a>
                             </li>
                             <li>
-                           Ensure mentors and IPMC have no 
+                           Ensure mentors and 
+  <a href='/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
have no 
                            <a href='#notes-issues'>remaining issues</a>
                             </li>
                         </ul>
@@ -140,18 +141,21 @@
                    <p>
 Each proposal has a <a href='incubation/Roles_and_Responsibilities#Sponsor'>Sponsor</a>.
 The identity of the Sponsor indicates the natural destination: for proposals sponsored by
the
-board or by the incubator PMC (IPMC), this is a top level project; for others, this is as
a subproject
+board or by the 
+<a href='/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
PMC (IPMC)</a>, 
+this is a top level project; for others, this is as a subproject
 of the sponsoring project but the destination is fixed on graduation, not entry. Projects
grow
 and evolve during the graduation process. As gradation approaches, this original preference
 should be reviewed based on where the project is now.
                    </p>
                    <p>
 Graduation as a subproject is only possible if the subproject still falls with the scope
of the project
-and requires the consent of the project PMC. Graduation as a project requires the formation
-of the new project by the board.
+and requires the consent of the project <a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMC</a>.

+Graduation as a project requires the formation of the new project by the board.
                    </p>
                    <p>
-The IPMC will also express a democratic opinion. For those seeking to graduate to a subproject
+The <a href='/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>

+will also express a democratic opinion. For those seeking to graduate to a subproject
 this vote is to approve the transfer. For those seeking to graduation as a top level project,
this
 will be a recommendation to the board. Expect IPMC-ers to ask questions about the project

 including about the choice of destination. This is part of the normal process.
@@ -162,7 +166,7 @@
             <title>Graduating To Top Level</title>
             <p>
                 Top level projects are created by the board. The
-                Incubator Project Management Committee (IPMC) can
+<a href='/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
Project Management Committee (IPMC)</a> can
                 therefore only recommend to the board that the project
                 is ready to graduate to a top level project.
             </p>
@@ -222,7 +226,7 @@
                     incubator list before a vote is started to allow
                     feedback. Once a consensus has been reached, a vote
                     should be started by a mentor proposing that the
-                    IPMC recommends the resolution to the board.
+<a href='/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
recommends the resolution to the board.
                 </p>
             </section>
         </section>
@@ -235,7 +239,8 @@
             <section id='subproject-acceptance'>
                 <title>Subproject Acceptance VOTE</title>
                 <p>
- A formal <code>VOTE</code> by the Project PMC to accept the podling as a subproject
is a 
+ A formal <code>VOTE</code> by the Project 
+ <a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMC</a>
to accept the podling as a subproject is a 
  prerequisite. Sometimes, projects may feel that the podling has grown too big and would
be 
  better as a top level project. The Chair of the project is the right contact.
                  </p>
@@ -277,8 +282,9 @@
 				<p>
 If you are going to cut a release (which is highly recommended), then please read 
 the <a href="releasemanagement.html">Incubator Release Management Guide</a> for
hints,
-tips and guidelines for cutting a release that will get approved by the IPMC without 
-problems.
+tips and guidelines for cutting a release that will get approved by the 
+<a href='/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>

+without problems.
 				</p>
             </section>
         </section>
@@ -319,7 +325,8 @@
 				<p>
 One of the exit criteria is that the podling needs to have an open and diverse
 <a href="http://www.apache.org/foundation/glossary.html#Meritocracy">meritocratic</a>
community. 
-To show this to the IPMC, it can be beneficial to vote and accept a couple of 
+To show this to the <a href='/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>,

+it can be beneficial to vote and accept a couple of 
 new contributors during incubation: this shows that you are open to accept new 
 developers and grow your community (note: this is not a requirement, but will help
 the graduation process). It will also allow you to diversify
@@ -463,7 +470,8 @@
             </section>
             <section id='notes-on-hand-over'><title>On The Handover</title>
                 <p>
-This is the transfer of virtual resources from the care of the IPMC
+This is the transfer of virtual resources from the care of the 
+<a href='/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
 to the care of either the new or existing top level project taking charge of the graudating
 community.		
 				</p>
@@ -480,7 +488,8 @@
 When graduating to a new project, the process is more complex. Creating a new project requires
 a <a href='http://www.apache.org/foundation/board/calendar.html'>resolution</a>
to be passed
 by the <a href='http://www.apache.org/foundation/board/'>board</a>. Usually once
this happens,
-members of the board will inform the appropriate chairs and PMCs. Occasionally, this will

+members of the board will inform the appropriate chairs and 
+<a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMCs</a>.
Occasionally, this will 
 be missed: if more than 72 hours has passed since the board meeting, it may be worth 
 someone posting a polite reminder to their favourite director.
 					</p>
@@ -533,7 +542,9 @@
 						</li>
 					</ul>
 					<p>
-They should then be able to start assembling the new PMC. The starting membership 
+They should then be able to start assembling the new 
+<a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMC</a>.

+The starting membership 
 is listed in the board resolution. However, the Chair of the new project
 needs to ensure that private list is created and the membership subscribed.
 					</p>
@@ -674,8 +685,8 @@
 	                    suitable for security issues should be noted.
 	                </p>
 	                <p>
-	                	Volunteers need to be found from the PMC to act as first
-	                	contacts on security matters.
+	                	Volunteers need to be found from the <a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMC</a>

+	                	to work with the Apache security team and act as first contacts on security
matters.
 	                </p>
 	            </section>
 	        </section>

Modified: incubator/public/trunk/site-publish/guides/graduation.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/graduation.html?view=diff&rev=536657&r1=536656&r2=536657
==============================================================================
--- incubator/public/trunk/site-publish/guides/graduation.html (original)
+++ incubator/public/trunk/site-publish/guides/graduation.html Wed May  9 14:17:12 2007
@@ -345,7 +345,8 @@
                                 </a>
                             </li>
                             <li>
-                           Ensure mentors and IPMC have no 
+                           Ensure mentors and 
+  <a href="/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
have no 
                            <a href="#notes-issues">remaining issues</a>
                             </li>
                         </ul>
@@ -392,18 +393,21 @@
 <p>
 Each proposal has a <a href="incubation/Roles_and_Responsibilities#Sponsor">Sponsor</a>.
 The identity of the Sponsor indicates the natural destination: for proposals sponsored by
the
-board or by the incubator PMC (IPMC), this is a top level project; for others, this is as
a subproject
+board or by the 
+<a href="/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
PMC (IPMC)</a>, 
+this is a top level project; for others, this is as a subproject
 of the sponsoring project but the destination is fixed on graduation, not entry. Projects
grow
 and evolve during the graduation process. As gradation approaches, this original preference
 should be reviewed based on where the project is now.
                    </p>
 <p>
 Graduation as a subproject is only possible if the subproject still falls with the scope
of the project
-and requires the consent of the project PMC. Graduation as a project requires the formation
-of the new project by the board.
+and requires the consent of the project <a href="http://www.apache.org/foundation/how-it-works.html#structure">PMC</a>.

+Graduation as a project requires the formation of the new project by the board.
                    </p>
 <p>
-The IPMC will also express a democratic opinion. For those seeking to graduate to a subproject
+The <a href="/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>

+will also express a democratic opinion. For those seeking to graduate to a subproject
 this vote is to approve the transfer. For those seeking to graduation as a top level project,
this
 will be a recommendation to the board. Expect IPMC-ers to ask questions about the project

 including about the choice of destination. This is part of the normal process.
@@ -416,7 +420,7 @@
 <div class="section-content">
 <p>
                 Top level projects are created by the board. The
-                Incubator Project Management Committee (IPMC) can
+<a href="/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
Project Management Committee (IPMC)</a> can
                 therefore only recommend to the board that the project
                 is ready to graduate to a top level project.
             </p>
@@ -480,7 +484,7 @@
                     incubator list before a vote is started to allow
                     feedback. Once a consensus has been reached, a vote
                     should be started by a mentor proposing that the
-                    IPMC recommends the resolution to the board.
+<a href="/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
recommends the resolution to the board.
                 </p>
 </div>
 </div>
@@ -498,7 +502,8 @@
 </h3>
 <div class="section-content">
 <p>
- A formal <code>VOTE</code> by the Project PMC to accept the podling as a subproject
is a 
+ A formal <code>VOTE</code> by the Project 
+ <a href="http://www.apache.org/foundation/how-it-works.html#structure">PMC</a>
to accept the podling as a subproject is a 
  prerequisite. Sometimes, projects may feel that the podling has grown too big and would
be 
  better as a top level project. The Chair of the project is the right contact.
                  </p>
@@ -546,8 +551,9 @@
 <p>
 If you are going to cut a release (which is highly recommended), then please read 
 the <a href="releasemanagement.html">Incubator Release Management Guide</a> for
hints,
-tips and guidelines for cutting a release that will get approved by the IPMC without 
-problems.
+tips and guidelines for cutting a release that will get approved by the 
+<a href="/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>

+without problems.
 				</p>
 </div>
 </div>
@@ -594,7 +600,8 @@
 <p>
 One of the exit criteria is that the podling needs to have an open and diverse
 <a href="http://www.apache.org/foundation/glossary.html#Meritocracy">meritocratic</a>
community. 
-To show this to the IPMC, it can be beneficial to vote and accept a couple of 
+To show this to the <a href="/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>,

+it can be beneficial to vote and accept a couple of 
 new contributors during incubation: this shows that you are open to accept new 
 developers and grow your community (note: this is not a requirement, but will help
 the graduation process). It will also allow you to diversify
@@ -763,7 +770,8 @@
 </h3>
 <div class="section-content">
 <p>
-This is the transfer of virtual resources from the care of the IPMC
+This is the transfer of virtual resources from the care of the 
+<a href="/incubatuion/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
 to the care of either the new or existing top level project taking charge of the graudating
 community.		
 				</p>
@@ -786,7 +794,8 @@
 When graduating to a new project, the process is more complex. Creating a new project requires
 a <a href="http://www.apache.org/foundation/board/calendar.html">resolution</a>
to be passed
 by the <a href="http://www.apache.org/foundation/board/">board</a>. Usually once
this happens,
-members of the board will inform the appropriate chairs and PMCs. Occasionally, this will

+members of the board will inform the appropriate chairs and 
+<a href="http://www.apache.org/foundation/how-it-works.html#structure">PMCs</a>.
Occasionally, this will 
 be missed: if more than 72 hours has passed since the board meeting, it may be worth 
 someone posting a polite reminder to their favourite director.
 					</p>
@@ -839,7 +848,9 @@
 						</li>
 					</ul>
 <p>
-They should then be able to start assembling the new PMC. The starting membership 
+They should then be able to start assembling the new 
+<a href="http://www.apache.org/foundation/how-it-works.html#structure">PMC</a>.

+The starting membership 
 is listed in the board resolution. However, the Chair of the new project
 needs to ensure that private list is created and the membership subscribed.
 					</p>
@@ -987,8 +998,8 @@
 	                    suitable for security issues should be noted.
 	                </p>
 <p>
-	                	Volunteers need to be found from the PMC to act as first
-	                	contacts on security matters.
+	                	Volunteers need to be found from the <a href="http://www.apache.org/foundation/how-it-works.html#structure">PMC</a>

+	                	to work with the Apache security team and act as first contacts on security
matters.
 	                </p>
 </div>
 </div>



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


Mime
View raw message