incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r547343 - in /incubator/public/trunk: site-author/guides/graduation.xml site-publish/guides/graduation.html
Date Thu, 14 Jun 2007 18:13:39 GMT
Author: rdonkin
Date: Thu Jun 14 11:13:38 2007
New Revision: 547343

URL: http://svn.apache.org/viewvc?view=rev&rev=547343
Log:
Patched changes made since Martijn's fork.

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=547343&r1=547342&r2=547343
==============================================================================
--- incubator/public/trunk/site-author/guides/graduation.xml (original)
+++ incubator/public/trunk/site-author/guides/graduation.xml Thu Jun 14 11:13:38 2007
@@ -45,6 +45,10 @@
 					the first steps that should be taken after
 					graduation.
 				</p>
+                <p>
+                    This is just a guide. Policy is stated 
+                    <a href='http://incubator.apache.org/incubation/Incubation_Policy.html'>here</a>.
+                </p>        
 			</section>
 		</section>
 		<section id="introduction">
@@ -88,7 +92,8 @@
 					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
+					destination: for proposals sponsored by the <a 
+                    href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>
or by
 					the <a
 					href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
 					PMC (IPMC)</a>, this is a top level project; for others,
@@ -107,7 +112,7 @@
 					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.
+					project by the <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
 
 				</p>
 				<p>
@@ -117,7 +122,8 @@
 					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.
+					project, this will be a recommendation to the <a 
+                    href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
 					Expect IPMC-ers to ask questions about the project
 					including about the choice of destination. This is part of
 					the normal process.
@@ -167,7 +173,7 @@
 							</li>
 							<li>
 
-								Ensure mentors and <a
+								Ensure <a href='/incubation/Roles_and_Responsibilities.html#Mentor'>Mentors</a>
and <a
 								href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
 								have no <a href='#notes-issues'>remaining
 								issues</a>
@@ -183,7 +189,7 @@
 					</li>
 					<li>
 
-						Prepare a <a href='#resolution'>resolution</a>
+						Prepare a <a href='#tlp-resolution'>resolution</a>
 						<em>(top level candidates only)</em>.
 
 					</li>
@@ -197,7 +203,7 @@
 					</li>
 					<li>
 
-						Incubator PMC VOTE:
+						<a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
PMC (IPMC)</a>:
 						<ul>
 							<li>
 
@@ -242,7 +248,9 @@
 
 					The status file is a great way of keeping tabs on how your
 					project is doing and what needs to be done to meet the
-					graduation criteria. The Incubator PMC will check this
+					graduation criteria. The <a 
+                    href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
PMC</a> 
+                    will check this
 					file when they vote on the graduation of your project.
 					Once all tasks are done and the listed criteria met, your
 					project may be ready for graduation.
@@ -397,10 +405,11 @@
 
 				<p>
 
-					Top level projects are created by the board. The <a
+					Top level projects are created by the <a 
+                    href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
The <a
 					href='/incubation/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
+					recommend to the Board that the project is ready to
 					graduate to a top level project.
 
 				</p>
@@ -413,7 +422,7 @@
 						<li>positive community graduation vote</li>
 						<li>writing a charter for your project</li>
 						<li>positive IPMC recommendation vote</li>
-						<li>acceptance of resolution by the Board</li>
+						<li>acceptance of <a href='#tlp-resolution'>resolution</a> by the
Board</li>
 					</ul>
 
 					This process can take a while, since it typically sparks
@@ -481,8 +490,10 @@
 					<title>Preparing A Charter</title>
 					<p>
 
-						So, in this case a suitable board resolution should be
-						drawn up by the community advised by the mentors.
+						So, in this case a suitable <a 
+                        href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>
resolution should be
+						drawn up by the community advised by the 
+                        <a href='/incubation/Roles_and_Responsibilities.html#Mentor'>Mentors</a>.
 						Committers can access the podling template for
 						resolutions in the <a
 						href="https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt">committers
@@ -512,7 +523,8 @@
 						The original proposal and the status document should
 						be consulted when creating this document. Projects
 						evolve over time and some deviation from the original
-						proposal may well prove acceptable. The board
+						proposal may well prove acceptable. The <a 
+                        href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>
 						resolution is the ultimate definition of the scope of
 						an Apache project. So, it is important that it
 						reflects the vision for the project as it appears on
@@ -543,13 +555,14 @@
 					<title>The Recommendation VOTE</title>
 					<p>
 
-						The resolution should be proposed on the general
+						The <a href='#tlp-resolution'>resolution</a> should be proposed on the
general
 						incubator list before a vote is started to allow
 						feedback. Once a consensus has been reached, a vote
 						should be started by a member of the PPMC proposing
 						that the <a
 						href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
-						recommends the resolution to the board.
+						recommends the resolution to the <a 
+                        href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
 
 					</p>
 				</section>
@@ -557,12 +570,12 @@
 					<title>Submission Of The Resolution To The Board</title>
 					<p>
 
-						Top level projects are created by a resolution by the
+						Top level projects are created by a <a href='#tlp-resolution'>resolution</a>
by the
 						<a
 						href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
-						Once the <a href='#resolution'>resolution</a> has been
+						Once the <a href='#tlp-resolution'>resolution</a> has been
 						finalized and consensus reached, it should be
-						submitted to the board. For inclusion in the agenda
+						submitted to the Board. For inclusion in the agenda
 						for the next meeting, the resolution should be
 						submitted at least 72 hours before that meeting. A
 						calendar for meetings is <a
@@ -571,7 +584,8 @@
 					</p>
 					<p>
 
-						Business for the board should be submitted by a post
+						Business for the <a 
+                        href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>
should be submitted by a post
 						to the <code>board</code> mailing list. Posting from
 						an Apache address is recommended. Mixing public and
 						private lists on a post is not recommended.
@@ -579,10 +593,13 @@
 					</p>
 					<p>
 
-						The board list is private. The usual <a
+						The <code>board</code> list is private. 
+                        The usual <a
 						href='http://www.apache.org/foundation/how-it-works.html#management'>netiquette</a>
 						for Apache private lists should be observed. So, it is
-						recommended that only the podling and IPMC private
+						recommended that only the podling and <a 
+                        href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>

+                        private
 						lists are CC'd (rather than the general incubator
 						list). Please treat responses with appropriate
 						confidentiality.
@@ -595,7 +612,7 @@
 						<li>The name of proposed VP</li>
 						<li>Links to the VOTE threads</li>
 						<li>Summary of the VOTE results</li>
-						<li>The resolution text</li>
+						<li>The <a href='#tlp-resolution'>resolution</a> text</li>
 					</ul>
 					<p>For example:</p>
 <note><pre>
@@ -631,11 +648,12 @@
 </pre></note>
 					<p>
 
-						Please try to keep the board list traffic low. Do not
+						Please try to keep the <code>board</code> list traffic low. Do not
 						submit reminders or ask whether messages have been
 						received on the list. <a
 						href='http://www.apache.org/foundation/members.html'>Apache
-						Members</a> have access to the Board archives and may
+						Members</a> have access to the <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>

+                        archives and may
 						observe Board meetings. To follow the progress of a
 						resolution, please ask a friendly Member or <a
 						href='http://www.apache.org/foundation/board/'>Director</a>.
@@ -700,8 +718,9 @@
 					<title>Graduation Approval VOTE</title>
 					<p>
 
-						To graduate as a subproject, the mentors should start
-                        a VOTE thread on the <a
+						To graduate as a subproject, the <a 
+                        href='/incubation/Roles_and_Responsibilities.html#Mentor'>Mentors</a>

+                        should start a VOTE thread on the <a
                         href='lists.html#general+at+incubator.apache.org'>general
                         list</a> proposing that the <a
                         href='incubation/Roles_and_Responsibilites.html#Incubator+Project+Management+Committee+%28PMC%29'>
@@ -721,7 +740,9 @@
 				<p>
 
 					This is the transfer of virtual resources from the care of
-                    the IPMC to the care of either the new or existing top
+                    the <a 
+                    href='/incubation/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 graduating community.
 
 				</p>
@@ -747,19 +768,20 @@
                         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
+                        href='http://www.apache.org/foundation/board/'>Board</a>.
+                        Usually once this happens, 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
+                        hours has passed since the Board meeting, it may be
                         worth someone posting a polite reminder to their
                         favorite director.
 
 					</p>
 					<p>
 
-						The board resolution will appoint a Chair for the new
+						The 
+                        <a href='#tlp-resolution'>resolution</a> will appoint
a Chair for the new
                         project. The Chair will also be appointed an <a
                         href='http://www.apache.org/foundation/'>Officer</a>
                         of the Apache Software Foundation. This allows them
@@ -773,8 +795,8 @@
 
 					<ul>
 
-						<li>Subscribe to the board mailing list</li>
-						<li>Subscribe to the infrastructure mailing list</li>
+						<li>Subscribe to the <code>board</code> mailing list</li>
+						<li>Subscribe to the <code>infrastructure</code> mailing list</li>
 						<li>Ensure that they have been added to the PMC chairs group in svnauth</li>
 						<li>Review appropriate documentation:
 							<ul>
@@ -796,7 +818,8 @@
 							</ul>
 						</li>
 						<li>
-							Work out a reporting schedule with the board. For
+							Work out a reporting schedule with the <a 
+                            href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
For
                             the first three months after graduation this will
                             be monthly. After that, the project should slot
                             into a quarterly reporting schedule.
@@ -811,8 +834,8 @@
 						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
+                        The starting membership is listed in the 
+                        <a href='#tlp-resolution'>resolution</a>. However, the
Chair of the new project
                         needs to ensure that private list is created and the
                         membership subscribed.
 
@@ -989,6 +1012,39 @@
 									</li>
 									</ol>
 								</li>
+								<li>
+								  <em>(Top Level Projects Only)</em>
+								  Add Project To
+								  <a href='http://www.apache.org'>
+								    www.apache.org
+								  </a>
+								  <ol>
+								    <li>
+								      Check out
+								      <code>
+								        https://svn.apache.org/repos/asf/infrastructure/site/trunk
+								      </code>
+								    </li>
+								    <li>
+								      Patch
+								      <code>
+								        xdocs/stylesheets/project.xml
+								      </code>
+								    </li>
+								    <li>
+								      If you have karma, regenerated and
+								      apply patch
+								    </li>
+								    <li>
+								      If you do not have karma, submit
+								      patch to
+								      <a
+								        href='https://issues.apache.org/jira/browse/INFRA'>
+								        infrastructure JIRA
+								      </a>
+								    </li>
+								  </ol>
+								</li>
 							</ol>
 						</li>
 						<li>Mailing lists
@@ -1042,26 +1098,51 @@
 						</li>
 					</ol>
 				</section>
-			</section>
-			<section id='security'>
-				<title>Security</title>
-				<p>
-
-					Each project needs to be able to manage security. By their
-	                nature, these issues need to be dealt with in private. These
-	                issues may either be dealt with on a separate list or by the
-	                private list. Which list is suitable for security issues
-	                should be noted.
-
-				</p>
-				<p>
-
-					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 id='unincubate'>
+            <title>Removing the Podling from Incubation</title>
+            <p>
+              When a project graduates, then the incubator resources
+              need to be updated to indicate that the project is no
+              longer incubating. Here are a few of the items that need
+              to be done:
+              <ul>
+                <li>
+                  Update the svn
+                  incubator/trunk/site-author/projects/podling/status.xml
+                  file to show the project's status
+                </li>
+                <li>
+                  Remove the project from the right navigation bar of
+                  the incubator web pages by updating svn
+                  incubator/trunk/site-author/stylesheets/project.xml
+                </li>
+                <li>
+                  Remove the project from the reporting calendar svn
+                  committers/board/incubator-info.txt
+                </li>
+              </ul>
+            </p>
+          </section>
+          <section id='security'>
+            <title>Security</title>
+            <p>
+    
+              Each project needs to be able to manage security. By their
+                      nature, these issues need to be dealt with in private. These
+                      issues may either be dealt with on a separate list or by the
+                      private list. Which list is suitable for security issues
+                      should be noted.
+    
+            </p>
+            <p>
+    
+              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>
 		</section>
 	</body>

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=547343&r1=547342&r2=547343
==============================================================================
--- incubator/public/trunk/site-publish/guides/graduation.html (original)
+++ incubator/public/trunk/site-publish/guides/graduation.html Thu Jun 14 11:13:38 2007
@@ -240,7 +240,9 @@
 Transferring Resources
  </a>
 </li>
-</ul>
+<li><a href='#unincubate'>
+Removing the Podling from Incubation
+ </a>
 </li>
 <li><a href='#security'>
 Security
@@ -249,6 +251,8 @@
 </ul>
 </li>
 </ul>
+</li>
+</ul>
 </div>
 <h3>
    <a name="abstract">Abstract</a>
@@ -266,6 +270,10 @@
 					the first steps that should be taken after
 					graduation.
 				</p>
+<p>
+                    This is just a guide. Policy is stated 
+                    <a href="http://incubator.apache.org/incubation/Incubation_Policy.html">here</a>.
+                </p>
 </div>
 </div>
            <h2><img src="/images/redarrow.gif" />
@@ -310,7 +318,7 @@
 <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
+					destination: for proposals sponsored by the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>
or by
 					the <a href="/incubation/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
@@ -326,7 +334,7 @@
 					subproject still falls within the scope of the project 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.
+					project by the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
 
 				</p>
 <p>
@@ -335,7 +343,7 @@
 					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.
+					project, this will be a recommendation to the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
 					Expect IPMC-ers to ask questions about the project
 					including about the choice of destination. This is part of
 					the normal process.
@@ -387,7 +395,7 @@
 							</li>
 							<li>
 
-								Ensure mentors and <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
+								Ensure <a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>
and <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
 								have no <a href="#notes-issues">remaining
 								issues</a>
 
@@ -401,7 +409,7 @@
 					</li>
 					<li>
 
-						Prepare a <a href="#resolution">resolution</a>
+						Prepare a <a href="#tlp-resolution">resolution</a>
 						<em>(top level candidates only)</em>.
 
 					</li>
@@ -415,7 +423,7 @@
 					</li>
 					<li>
 
-						Incubator PMC VOTE:
+						<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
PMC (IPMC)</a>:
 						<ul>
 							<li>
 
@@ -457,7 +465,8 @@
 
 					The status file is a great way of keeping tabs on how your
 					project is doing and what needs to be done to meet the
-					graduation criteria. The Incubator PMC will check this
+					graduation criteria. The <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
PMC</a> 
+                    will check this
 					file when they vote on the graduation of your project.
 					Once all tasks are done and the listed criteria met, your
 					project may be ready for graduation.
@@ -607,9 +616,9 @@
 <div class="section-content">
 <p>
 
-					Top level projects are created by the board. The <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
+					Top level projects are created by the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
The <a href="/incubation/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
+					recommend to the Board that the project is ready to
 					graduate to a top level project.
 
 				</p>
@@ -622,7 +631,7 @@
 						<li>positive community graduation vote</li>
 						<li>writing a charter for your project</li>
 						<li>positive IPMC recommendation vote</li>
-						<li>acceptance of resolution by the Board</li>
+						<li>acceptance of <a href="#tlp-resolution">resolution</a> by the
Board</li>
 					</ul>
 
 					This process can take a while, since it typically sparks
@@ -683,8 +692,9 @@
 <div class="section-content">
 <p>
 
-						So, in this case a suitable board resolution should be
-						drawn up by the community advised by the mentors.
+						So, in this case a suitable <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>
resolution should be
+						drawn up by the community advised by the 
+                        <a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>.
 						Committers can access the podling template for
 						resolutions in the <a href="https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt">committers
 						svn repository</a>. Also, resolutions are included in
@@ -712,7 +722,7 @@
 						The original proposal and the status document should
 						be consulted when creating this document. Projects
 						evolve over time and some deviation from the original
-						proposal may well prove acceptable. The board
+						proposal may well prove acceptable. The <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>
 						resolution is the ultimate definition of the scope of
 						an Apache project. So, it is important that it
 						reflects the vision for the project as it appears on
@@ -744,12 +754,12 @@
 <div class="section-content">
 <p>
 
-						The resolution should be proposed on the general
+						The <a href="#tlp-resolution">resolution</a> should be proposed on the
general
 						incubator list before a vote is started to allow
 						feedback. Once a consensus has been reached, a vote
 						should be started by a member of the PPMC proposing
 						that the <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
-						recommends the resolution to the board.
+						recommends the resolution to the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
 
 					</p>
 </div>
@@ -759,11 +769,11 @@
 <div class="section-content">
 <p>
 
-						Top level projects are created by a resolution by the
+						Top level projects are created by a <a href="#tlp-resolution">resolution</a>
by the
 						<a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
-						Once the <a href="#resolution">resolution</a> has been
+						Once the <a href="#tlp-resolution">resolution</a> has been
 						finalized and consensus reached, it should be
-						submitted to the board. For inclusion in the agenda
+						submitted to the Board. For inclusion in the agenda
 						for the next meeting, the resolution should be
 						submitted at least 72 hours before that meeting. A
 						calendar for meetings is <a href="http://www.apache.org/foundation/board/calendar.html">available</a>.
@@ -771,7 +781,7 @@
 					</p>
 <p>
 
-						Business for the board should be submitted by a post
+						Business for the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>
should be submitted by a post
 						to the <code>board</code> mailing list. Posting from
 						an Apache address is recommended. Mixing public and
 						private lists on a post is not recommended.
@@ -779,9 +789,11 @@
 					</p>
 <p>
 
-						The board list is private. The usual <a href="http://www.apache.org/foundation/how-it-works.html#management">netiquette</a>
+						The <code>board</code> list is private. 
+                        The usual <a href="http://www.apache.org/foundation/how-it-works.html#management">netiquette</a>
 						for Apache private lists should be observed. So, it is
-						recommended that only the podling and IPMC private
+						recommended that only the podling and <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>

+                        private
 						lists are CC'd (rather than the general incubator
 						list). Please treat responses with appropriate
 						confidentiality.
@@ -794,7 +806,7 @@
 						<li>The name of proposed VP</li>
 						<li>Links to the VOTE threads</li>
 						<li>Summary of the VOTE results</li>
-						<li>The resolution text</li>
+						<li>The <a href="#tlp-resolution">resolution</a> text</li>
 					</ul>
 <p>For example:</p>
 <div class="note">
@@ -832,10 +844,11 @@
 </div>
 <p>
 
-						Please try to keep the board list traffic low. Do not
+						Please try to keep the <code>board</code> list traffic low. Do not
 						submit reminders or ask whether messages have been
 						received on the list. <a href="http://www.apache.org/foundation/members.html">Apache
-						Members</a> have access to the Board archives and may
+						Members</a> have access to the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>

+                        archives and may
 						observe Board meetings. To follow the progress of a
 						resolution, please ask a friendly Member or <a href="http://www.apache.org/foundation/board/">Director</a>.
 
@@ -899,8 +912,8 @@
 <div class="section-content">
 <p>
 
-						To graduate as a subproject, the mentors should start
-                        a VOTE thread on the <a href="lists.html#general+at+incubator.apache.org">general
+						To graduate as a subproject, the <a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>

+                        should start a VOTE thread on the <a href="lists.html#general+at+incubator.apache.org">general
                         list</a> proposing that the <a href="incubation/Roles_and_Responsibilites.html#Incubator+Project+Management+Committee+%28PMC%29">
                         IPMC</a> signs off the graduation of the podling as a
                         subproject. This votes should only be started once the
@@ -921,7 +934,8 @@
 <p>
 
 					This is the transfer of virtual resources from the care of
-                    the IPMC to the care of either the new or existing top
+                    the <a href="/incubation/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 graduating community.
 
 				</p>
@@ -946,18 +960,19 @@
 
 						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
+                        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 <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
+                        hours has passed since the Board meeting, it may be
                         worth someone posting a polite reminder to their
                         favorite director.
 
 					</p>
 <p>
 
-						The board resolution will appoint a Chair for the new
+						The 
+                        <a href="#tlp-resolution">resolution</a> will appoint
a Chair for the new
                         project. The Chair will also be appointed an <a href="http://www.apache.org/foundation/">Officer</a>
                         of the Apache Software Foundation. This allows them
                         access to official resources of the foundation as well
@@ -969,8 +984,8 @@
 					</p>
 <ul>
 
-						<li>Subscribe to the board mailing list</li>
-						<li>Subscribe to the infrastructure mailing list</li>
+						<li>Subscribe to the <code>board</code> mailing list</li>
+						<li>Subscribe to the <code>infrastructure</code> mailing list</li>
 						<li>Ensure that they have been added to the PMC chairs group in svnauth</li>
 						<li>Review appropriate documentation:
 							<ul>
@@ -992,7 +1007,7 @@
 							</ul>
 						</li>
 						<li>
-							Work out a reporting schedule with the board. For
+							Work out a reporting schedule with the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
For
                             the first three months after graduation this will
                             be monthly. After that, the project should slot
                             into a quarterly reporting schedule.
@@ -1006,8 +1021,8 @@
 
 						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
+                        The starting membership is listed in the 
+                        <a href="#tlp-resolution">resolution</a>. However, the
Chair of the new project
                         needs to ensure that private list is created and the
                         membership subscribed.
 
@@ -1181,6 +1196,38 @@
 									</li>
 									</ol>
 								</li>
+								<li>
+								  <em>(Top Level Projects Only)</em>
+								  Add Project To
+								  <a href="http://www.apache.org">
+								    www.apache.org
+								  </a>
+								  <ol>
+								    <li>
+								      Check out
+								      <code>
+								        https://svn.apache.org/repos/asf/infrastructure/site/trunk
+								      </code>
+								    </li>
+								    <li>
+								      Patch
+								      <code>
+								        xdocs/stylesheets/project.xml
+								      </code>
+								    </li>
+								    <li>
+								      If you have karma, regenerated and
+								      apply patch
+								    </li>
+								    <li>
+								      If you do not have karma, submit
+								      patch to
+								      <a href="https://issues.apache.org/jira/browse/INFRA">
+								        infrastructure JIRA
+								      </a>
+								    </li>
+								  </ol>
+								</li>
 							</ol>
 						</li>
 						<li>Mailing lists
@@ -1232,27 +1279,54 @@
 						</li>
 					</ol>
 </div>
+<h4>
+   <a name="unincubate">Removing the Podling from Incubation</a>
+</h4>
+<div class="section-content">
+<p>
+              When a project graduates, then the incubator resources
+              need to be updated to indicate that the project is no
+              longer incubating. Here are a few of the items that need
+              to be done:
+              <ul>
+                <li>
+                  Update the svn
+                  incubator/trunk/site-author/projects/podling/status.xml
+                  file to show the project's status
+                </li>
+                <li>
+                  Remove the project from the right navigation bar of
+                  the incubator web pages by updating svn
+                  incubator/trunk/site-author/stylesheets/project.xml
+                </li>
+                <li>
+                  Remove the project from the reporting calendar svn
+                  committers/board/incubator-info.txt
+                </li>
+              </ul>
+            </p>
 </div>
-<h3>
+<h4>
    <a name="security">Security</a>
-</h3>
+</h4>
 <div class="section-content">
 <p>
-
-					Each project needs to be able to manage security. By their
-	                nature, these issues need to be dealt with in private. These
-	                issues may either be dealt with on a separate list or by the
-	                private list. Which list is suitable for security issues
-	                should be noted.
-
-				</p>
-<p>
-
-					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>
+    
+              Each project needs to be able to manage security. By their
+                      nature, these issues need to be dealt with in private. These
+                      issues may either be dealt with on a separate list or by the
+                      private list. Which list is suitable for security issues
+                      should be noted.
+    
+            </p>
+<p>
+    
+              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>
 </div>
          </td>



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


Mime
View raw message