incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r547326 - in /incubator/public/trunk/site-publish/guides: graduation-timeline.png graduation.html
Date Thu, 14 Jun 2007 17:41:50 GMT
Author: rdonkin
Date: Thu Jun 14 10:41:49 2007
New Revision: 547326

URL: http://svn.apache.org/viewvc?view=rev&rev=547326
Log:
IMHO Cleaner to commit generated versions and keep everything in sync.

Added:
    incubator/public/trunk/site-publish/guides/graduation-timeline.png   (with props)
Modified:
    incubator/public/trunk/site-publish/guides/graduation.html

Added: incubator/public/trunk/site-publish/guides/graduation-timeline.png
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/graduation-timeline.png?view=auto&rev=547326
==============================================================================
Binary file - no diff available.

Propchange: incubator/public/trunk/site-publish/guides/graduation-timeline.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

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=547326&r1=547325&r2=547326
==============================================================================
--- incubator/public/trunk/site-publish/guides/graduation.html (original)
+++ incubator/public/trunk/site-publish/guides/graduation.html Thu Jun 14 10:41:49 2007
@@ -20,10 +20,8 @@
  <head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
   <link rel="stylesheet" href="/style/style.css" type="text/css" />
-    <link rel="alternate" title="
-            general@incubator.apache.org Archives
-        " type="application/atom+xml" href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom" />
-    <title>Graduation Guide (DRAFT) - Apache Incubator</title>
+    <link rel="alternate" title="general@incubator.apache.org Archives" type="application/atom+xml" href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom" />
+    <title>Guide to successful graduation (DRAFT) - Apache Incubator</title>
  </head>
  <body>        
   <table border="0" width="100%" cellspacing="0">
@@ -100,17 +98,20 @@
     <!-- CONTENT -->
     <td align="left" valign="top" class="content">
                 <h2><img src="/images/redarrow.gif" />
-   <a name="preamble">Graduation Guide (DRAFT)</a>
+   <a name="preamble">Guide to successful graduation (DRAFT)</a>
 </h2>
 <div class="section-content">
 <h3>
    <a name="status">Status - DRAFT</a>
 </h3>
 <div class="section-content">
+<p>This document is under development.</p>
 <p>
-                    This document is under
-                    <a href="#help-wanted">development</a>.
-                </p>
+					Help to improve the system by posting a patch for
+					this document to the incubator section of JIRA or a
+					comment to the <a href="lists.html">general</a> list at
+					incubator.
+				</p>
 </div>
 <h3>
    <a name="TOC">Contents</a>
@@ -118,7 +119,7 @@
 <div class="section-content">
 <ul>
 <li><a href='#preamble'>
-Graduation Guide (DRAFT)
+Guide to successful graduation (DRAFT)
  </a>
  <ul>
 <li><a href='#status'>
@@ -133,35 +134,53 @@
 Abstract
  </a>
 </li>
-<li><a href='#background'>
-Background
- </a>
+</ul>
 </li>
-<li><a href='#help-wanted'>
-Help Wanted!
+<li><a href='#introduction'>
+What is graduation?
+ </a>
+ <ul>
+<li><a href='#subproject-or-top-level'>
+To Graduate To Subproject Or To Top Level
  </a>
 </li>
 </ul>
 </li>
+<li><a href='#requirements'>
+Before you graduate
+ </a>
+ <ul>
 <li><a href='#checklist'>
 Graduation Check List
  </a>
 </li>
-<li><a href='#understanding'>
-Understanding The Graduation Process
+<li><a href='#notes-status'>
+Checking the status file
  </a>
- <ul>
-<li><a href='#subproject-or-top-level'>
-To Graduate To Subproject Or To Top Level
+</li>
+<li><a href='#releases'>
+Creating an Apache release
+ </a>
+</li>
+<li><a href='#community'>
+Having an open and diverse community
  </a>
 </li>
 </ul>
 </li>
-<li><a href='#graduate-to-top-level'>
-Graduating To Top Level
+<li><a href='#process'>
+The graduation process
+ </a>
+ <ul>
+<li><a href='#toplevel'>
+Graduating to a top level project
  </a>
  <ul>
-<li><a href='#resolution'>
+<li><a href='#tlp-community-vote'>
+Community Graduation Vote
+ </a>
+</li>
+<li><a href='#tlp-resolution'>
 Preparing A Charter
  </a>
 </li>
@@ -176,9 +195,13 @@
 </ul>
 </li>
 <li><a href='#subproject'>
-Graduation To A Subproject
+Graduating to a subproject
  </a>
  <ul>
+<li><a href='#sp-community-vote'>
+Community Graduation Vote
+ </a>
+</li>
 <li><a href='#subproject-acceptance'>
 Subproject Acceptance VOTE
  </a>
@@ -189,44 +212,12 @@
 </li>
 </ul>
 </li>
-<li><a href='#project-needs'>
-Some Things A Project Needs To Understand
- </a>
- <ul>
-<li><a href='#releases'>
-How To Create An Apache Release
- </a>
-</li>
-</ul>
-</li>
-<li><a href='#notes'>
-Notes
- </a>
- <ul>
-<li><a href='#notes-status'>
-On The Status File
- </a>
-</li>
-<li><a href='#notes-community'>
-On Community
- </a>
- <ul>
-<li><a href='#community-vote'>
-Community Graduation Vote
- </a>
-</li>
 </ul>
 </li>
-<li><a href='#notes-issues'>
-On Remaining Obstacles
+<li><a href='#life-after-graduation'>
+Life after graduation
  </a>
  <ul>
-<li><a href='#notes-releases'>
-Creating A Release
- </a>
-</li>
-</ul>
-</li>
 <li><a href='#notes-on-hand-over'>
 On The Handover
  </a>
@@ -245,14 +236,12 @@
 First Steps Outside The Incubator
  </a>
  <ul>
-<li><a href='#unincubate'>
-Removing the Podling from Incubation
- </a>
-</li>
 <li><a href='#transfer'>
 Transferring Resources
  </a>
 </li>
+</ul>
+</li>
 <li><a href='#security'>
 Security
  </a>
@@ -260,275 +249,554 @@
 </ul>
 </li>
 </ul>
-</li>
-</ul>
 </div>
 <h3>
    <a name="abstract">Abstract</a>
 </h3>
 <div class="section-content">
 <p>
-                    The intent of this document is to help podlings 
-                    understand the process of 
-                    graduation and offer some views about how to approach it. 
-                    It also links to the Incubator 
-                    <a href="http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator">exit policies</a>.
-                    It is not an inflexible standard but represents a
-                    consensus condensed from previous discussions on the
-                    incubator general list. It also describes some of
-                    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>
+					The intent of this document is to help podlings
+					understand the process of
+					graduation and offer some views about how to approach it.
+					It also links to the Incubator
+					<a href="http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator">exit policies</a>.
+					It is not an inflexible standard but represents a
+					consensus condensed from previous discussions on the
+					incubator general list. It also describes some of
+					the first steps that should be taken after
+					graduation.
+				</p>
 </div>
-<h3>
-   <a name="background">Background</a>
-</h3>
+</div>
+           <h2><img src="/images/redarrow.gif" />
+   <a name="introduction">What is graduation?</a>
+</h2>
 <div class="section-content">
 <p>
-                    Graduation is a democratic process. In the end, it
-                    comes down to a vote. This document is offered for
-                    guidance and education only. Actual policy is documented in
-                    the 
-                    <a href="../incubation/Incubation_Policy.html">Incubation
-                    Policy Guide</a> in the section titled
-                    <a href="../incubation/Incubation_Policy.html#Graduating+from+the+Incubator">Exiting
-                    the Incubator</a>.
-                    Please post any questions about graduation to the
-                    <a href="lists.html">general incubator list</a>.
-                </p>
-</div>
+
+				Graduation is the act of a Podling becoming either a
+				subproject under an already existing Apache project, or
+				becoming a top level Apache project. Graduating is a
+				democratic process: in the end, it comes down to a vote. Note
+				that during your stay in the incubator, you are already busy
+				with the process of Graduating: by adopting Apache procedures,
+				growing and fostering your community, having (civil) fights
+				concerning code style (tabs versus spaces), cutting releases
+				and so forth. All these acts have an influence on your
+				projects graduation.
+
+			</p>
+<p>
+
+				The road to graduation pretty clear: depending on wether your
+				project wants to become a top level project, or join as a
+				subproject under an already existing project the steps are
+				fairly simple but do take time and effort. This document
+				provides guidelines for making this process run smooth.
+
+			</p>
+<p>
+				This document is offered for guidance and education only.
+				Actual policy is documented in the <a href="../incubation/Incubation_Policy.html">Incubation Policy
+				Guide</a> in the section titled <a href="../incubation/Incubation_Policy.html#Graduating+from+the+Incubator">Exiting
+				the Incubator</a>. Please post any questions about graduation
+				to the <a href="lists.html">general incubator list</a>.
+
+			</p>
 <h3>
-   <a name="help-wanted">Help Wanted!</a>
+   <a name="subproject-or-top-level">To Graduate To Subproject Or To Top Level</a>
 </h3>
 <div class="section-content">
 <p>
-                    Help to improve the system by posting a patch for
-                    this document to the incubator section of JIRA or a
-                    comment to the <a href="lists.html">general</a> list at incubator.
-                </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 <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
+					destination is fixed on graduation, not entry. Projects
+					grow and evolve during the graduation process. As
+					graduation 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 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.
+
+				</p>
+<p>
+
+					The <a href="/incubation/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.
+
+				</p>
 </div>
 </div>
            <h2><img src="/images/redarrow.gif" />
-   <a name="checklist">Graduation Check List</a>
+   <a name="requirements">Before you graduate</a>
 </h2>
 <div class="section-content">
 <p>
-                    The following is a short checklist giving an overview, not a
-                    substitute for reading the content below.
-                </p>
+
+				Before you start graduation, you need to make sure you are
+				ready and meet the requirements imposed on Apache projects.
+				This section will provide a shortlist for Podlings to
+				determine if they meet the criteria for asking graduation.
+
+			</p>
+<h3>
+   <a name="checklist">Graduation Check List</a>
+</h3>
+<div class="section-content">
+<p>
+
+					The following is a short checklist giving an overview, not
+					a substitute for reading the content below.
+
+				</p>
 <ol>
-                    <li>Preparations
-                        <ul>
-                            <li>
-                                Complete (and sign off) tasks documented
-                                in the
-                                <a href="#notes-status">status file</a>
-                            </li>
-                            <li>
-                                Demonstrate ability to
-                                <a href="#releases">
-                                    create Apache releases
-                                </a>
-                            </li>
-                            <li>
-                                Demonstrate
-                                <a href="#notes-community">
-                                    community readiness
-                                </a>
-                            </li>
-                            <li>
-                           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>
-                            </li>
-                        </ul>
-                    </li>
-                    <li>
-Decide upon <a href="#subproject-or-top-level">destination</a>
-                    </li>
-                    <li>
-Prepare a <a href="#resolution">resolution</a> <em>(top level candidates only)</em>.
-                    </li>
-                    <li>
-<a href="#subproject-acceptance">Subproject acceptance vote</a> by destination Project
-<em>(subproject candidates only)</em>
-                    </li>
-                    <li>
-<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator PMC (IPMC)</a> VOTE:
-                        <ul>
-                            <li>
- For top level candidates, this is a
- <a href="#ipmc-top-level-recommendation">recommendation vote</a> 
-                             </li>
-                             <li>
-For subproject candidates, this is a 
-<a href="#subproject-graduation">graduation approval vote</a>                   
-                             </li>
-                        </ul>
-                    </li>
-                    <li>
- Final <a href="#notes-on-hand-over">hand-over</a>
-                    </li>
-                    <li>
-Consider post graduation <a href="#project-first-steps">tasks</a>
-                    </li>
-                </ol>
+					<li>Preparations
+						<ul>
+							<li>
+
+								Complete (and sign off) tasks documented in
+								the <a href="#notes-status">status file</a>
+
+							</li>
+							<li>
+
+								Demonstrate ability to <a href="#releases">create Apache releases</a>
+
+							</li>
+							<li>
+
+								Demonstrate <a href="#community">community
+                                readiness</a>
+
+							</li>
+							<li>
+
+								Ensure mentors 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>
+
+							</li>
+						</ul>
+					</li>
+					<li>
+
+						Decide upon <a href="#subproject-or-top-level">destination</a>
+
+					</li>
+					<li>
+
+						Prepare a <a href="#resolution">resolution</a>
+						<em>(top level candidates only)</em>.
+
+					</li>
+
+					<li>
+
+						<a href="#subproject-acceptance">Subproject acceptance
+						vote</a> by destination Project <em>(subproject
+						candidates only)</em>
+
+					</li>
+					<li>
+
+						Incubator PMC VOTE:
+						<ul>
+							<li>
+
+								For top level candidates, this is a <a href="#ipmc-top-level-recommendation">recommendation
+								vote</a>
+
+							</li>
+							<li>
+
+								For subproject candidates, this is a <a href="#subproject-graduation">graduation
+								approval vote</a>
+
+							</li>
+						</ul>
+					</li>
+					<li>
+						Final <a href="#notes-on-hand-over">hand-over</a>
+					</li>
+					<li>
+
+						Consider post graduation <a href="#project-first-steps">tasks</a>
+
+					</li>
+				</ol>
 </div>
-           <h2><img src="/images/redarrow.gif" />
-   <a name="understanding">Understanding The Graduation Process</a>
-</h2>
+<h3>
+   <a name="notes-status">Checking the status file</a>
+</h3>
 <div class="section-content">
+<p>
+
+					The status file records and summarizes incubation-related
+					information on the podling. The <a href="ppmc.html#Incubator+ASF+Board+Reports">PPMC</a> is
+					responsible for keeping this file current. Before you are
+					able to graduate, all tasks need to be completed.
+
+				</p>
+<p>
+
+					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
+					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.
+
+				</p>
+<p>
+
+					The status file of the JUDDI project is <a href="http://incubator.apache.org/projects/juddi.html">one
+					example</a>.
+
+				</p>
+</div>
 <h3>
-   <a name="subproject-or-top-level">To Graduate To Subproject Or To Top Level</a>
+   <a name="releases">Creating an Apache release</a>
 </h3>
 <div class="section-content">
+<blockquote cite="http://catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html">
+					<p>Release Early, Release Often</p>
+					<div align="right">
+						<p>
+							<a href="http://catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html">Eric Steven Raymond</a>
+						</p>
+					</div>
+				</blockquote>
+<p>
+
+					Projects need to cut releases. Apache projects need to
+					understand how to cut Apache releases. Therefore it is an
+					important step during your stay in the incubator to
+					demonstrate the ability to create an Apache Release.
+
+				</p>
+<p>
+
+					Podlings do not need to actually <em>publish</em> a
+                    release to demonstrate that they understand how to
+                    accomplish such a feat. However, creating a release that
+                    is approved by the <a href="incubation/Roles_and_Responsibilites.html#Incubator+Project+Management+Committee+%28PMC%29">
+                    incubator project management committee</a> is usually the
+                    simplest way to do this.
+
+				</p>
+<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 <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
+					without problems.
+
+				</p>
+</div>
+<h3>
+   <a name="community">Having an open and diverse community</a>
+</h3>
+<div class="section-content">
+<p>
+
+					A major criterion for graduation is to have developed an
+					open and diverse <a href="http://www.apache.org/foundation/glossary.html#Meritocracy">meritocratic</a>
+					community. Time has demonstrated that these kinds of
+					communities are more robust and productive than more
+					closed ones.
+
+				</p>
+<p>
+
+					Apache projects are self-sustaining and self-governing
+                    communities. Long term success and health requires that
+                    these communities understand how to:
+
+                </p>
+<ul>
+                	<li>recruit users, developers, committers and PMCers</li>
+                	<li>take responsible collective action</li>
+					<li>disagree in public on technical matters without destroying personal relationships</li>
+					<li>create an open, positive and inclusive atmosphere on the mailing lists</li>
+				</ul>
+<p>
+
+					Graduation tests whether (in the opinion of the <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>)
+                    a podling has learned enough and is responsible enough to
+                    sustain itself as such a community.
+
+				</p>
+<p>
+
+					Read more on how to successfully build an open and diverse
+                    community for your podling in the <a href="community.html">community guide</a>.
+
+				</p>
+<p>
+
+					As a project grows, it needs to renew itself by accepting
+					new committers. A project needs to learn how it can
+					recruit new developers and committers into the community.
+					Accepting new committers usually increases the diversity
+					of the project. So, this process is very beneficial. <a href="community.html">Community building</a> requires
+					energy which could have been spent on code development but
+					this cost is an important investment for the future of the
+					project.
+
+				</p>
+<p>
+
+					The openness of the community is not only measured by the
+					number of contributors. Open and respectful discussions on
+					the mailing lists are vital. Ways to resolve technical
+					conflict without destroying personal relationships must be
+					learned. Learning to use mailing lists effectively is very
+					important. If this can be achieved, then you have shown to
+					be a lively, active and successful community. The future
+					looks bright.
+
+				</p>
+<p>
+
+					The project is considered to have a diverse community when
+					it is not highly dependent on any single contributor
+					(there are at least 3 legally independent committers and
+					there is no single company or entity that is vital to the
+					success of the project). Basically this means that when a
+					project mostly consists of contributors from one company,
+					this is a sign of not being diverse enough. You can
+					mitigate this requirement by admitting more external
+					contributors to your project that have no tie to the
+					single entity.
+
+				</p>
 <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
-<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 destination is fixed on graduation, not entry. Projects grow
-and evolve during the graduation process. As graduation 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 <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 
-<a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
-                   </p>
-<p>
-The <a href="/incubation/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 <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.
-                   </p>
+
+					Growing an open and diverse meritocratic community is not
+                    something that just happens: it takes work. Read the <a href="community.html">building a community guide</a> for
+                    guidelines, hints and tips on how you can accomplish this
+                    for your project.
+
+				</p>
 </div>
 </div>
            <h2><img src="/images/redarrow.gif" />
-   <a name="graduate-to-top-level">Graduating To Top Level</a>
+   <a name="process">The graduation process</a>
 </h2>
 <div class="section-content">
-<p>
-                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 graduate to a top level project.
-            </p>
 <h3>
-   <a name="resolution">Preparing A Charter</a>
+   <a name="toplevel">Graduating to a top level project</a>
 </h3>
 <div class="section-content">
 <p>
-                    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 the
-                    Board minutes, which are posted publicly
-                    <a href="http://www.apache.org/foundation/board/calendar.html">
-                        here
-                    </a>
-                    . These contain numerous examples. Good examples include:
-                    <ul>
-                    <li> Harmony (see section <em>E. Establish the Apache 
-                         Harmony project</em> in the 
-                         <a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_10_25.txt">October 2006 Board minutes</a>)
-                    </li>
-                    <li> OFBiz (see section 
-                         <em>B. Establish Apache Open for Business Project</em>
-                         in the
-                         <a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_12_20.txt">December 2006 Board minutes</a>)
-                    </li>
-                    <li> Cayenne (see section 
-                         <em>C. Establish Apache Cayenne Project</em>
-                         in the
-                         <a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_12_20.txt">December 2006 Board minutes</a>)
-                    </li>
-                    </ul>
-                </p>
+
+					Top level projects are created by the board. 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
+					graduate to a top level project.
+
+				</p>
 <p>
-                    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
-                    <a href="#resolution">resolution</a> 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
-                    the eve of graduation.
-                </p>
+
+					The following steps are needed for graduating to a top
+					level project:
+
+					<ul>
+						<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>
+					</ul>
+
+					This process can take a while, since it typically sparks
+					some discussion inside the community and possibly in the
+					IPMC.
+
+				</p>
 <p>
-                    A good resolution is neither too narrow nor too
-                    broad. If the project's scope is too narrow, then
-                    its activities will be unnecessarily constrained.
-                    If a project's scope is too broad then it may lack
-                    focus and suffer from governance issues.
-                </p>
+
+					Here's an estimated timeline for the graduation process.
+					It should help you understand when you should start
+					ramping up your community to get timely graduation and
+					make the process smooth.
+
+				</p>
+<map name="GraffleExport">
+					<area shape="rect" coords="13,112,84,155" href="#tlp-community-vote" />
+					<area shape="rect" coords="15,166,511,209" href="#tlp-resolution" />
+					<area shape="rect" coords="12,220,83,263" href="#ipmc-top-level-recommendation" />
+					<area shape="rect" coords="15,273,79,317" href="#top-level-board-proposal" />
+					<area shape="rect" coords="232,330,293,369" href="http://people.apache.org/calendar.html" />
+				</map>
+<img border="0" src="graduation-timeline.png" usemap="#GraffleExport" alt="Graduation timeline" title="Graduation timeline" />
+<p>
+
+					For each event we scheduled one or two weeks. Even though
+					a vote is usually limited to 72 hours, you should prepare
+					for discussion and possibly having to cast a revote with a
+					revised proposal.
+
+				</p>
+<h4>
+   <a name="tlp-community-vote">Community Graduation Vote</a>
+</h4>
+<div class="section-content">
+<p>
+
+						A community needs to be willing to govern itself
+						before it can become a top level project. A good way
+						to demonstrate this is through a free vote (by the
+						community) on the graduation proposal.
+
+					</p>
+<p>
+
+						This vote is not a requirement but is recommended. It
+						is unlikely that <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
+						members will vote to approve graduation unless the <a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>
+						and community positively express their readiness for
+						graduation. It is wise to copy the <a href="lists.html#general+at+incubator.apache.org">incubator
+						general list</a> when the vote is proposed.
+
+					</p>
 </div>
-<h3>
+<h4>
+   <a name="tlp-resolution">Preparing A Charter</a>
+</h4>
+<div class="section-content">
+<p>
+
+						So, in this case a suitable board resolution should be
+						drawn up by the community advised by the mentors.
+						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
+						the Board minutes, which are posted publicly <a href="http://www.apache.org/foundation/board/calendar.html">
+						here </a> . These contain numerous examples. Good
+						examples include:
+
+						<ul>
+							<li>
+								Harmony (see section <em>E. Establish the Apache Harmony project</em> in the
+								<a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_10_25.txt">October 2006 Board minutes</a>)
+							</li>
+							<li>
+								OFBiz (see section <em>B. Establish Apache Open for Business Project</em> in the
+								<a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_12_20.txt">December 2006 Board minutes</a>)
+							</li>
+							<li>
+								Cayenne (see section <em>C. Establish Apache Cayenne Project</em> in the
+								<a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_12_20.txt">December 2006 Board minutes</a>)
+							</li>
+						</ul>
+					</p>
+<p>
+
+						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
+						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
+						the eve of graduation.
+
+					</p>
+<p>
+
+						A good resolution is neither too narrow nor too broad.
+						If the project's scope is too narrow, then its
+						activities will be unnecessarily constrained. If a
+						project's scope is too broad then it may lack focus
+						and suffer from governance issues.
+
+
+					</p>
+<p>
+
+						If you read these resolutions you also see that you
+                        need to appoint a <a href="http://www.apache.org/foundation/glossary.html#Chair">Chair</a>
+                        for your project. It is up to the PPMC to choose one
+                        person to act as the chair after graduation.
+
+					</p>
+</div>
+<h4>
    <a name="ipmc-top-level-recommendation">The Recommendation VOTE</a>
-</h3>
+</h4>
 <div class="section-content">
 <p>
-                    The <a href="#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 
-                    <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
-                </p>
+
+						The resolution 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.
+
+					</p>
 </div>
-<h3>
+<h4>
    <a name="top-level-board-proposal">Submission Of The Resolution To The Board</a>
-</h3>
+</h4>
 <div class="section-content">
 <p>
-Top level projects are created by a <a href="#resolution">resolution</a> by the 
-<a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>. Once the 
-resolution has been finalised and consensus reached, 
-it should be 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>.
-                </p>
-<p>
-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. 
-                </p>
+
+						Top level projects are created by a resolution by the
+						<a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
+						Once the <a href="#resolution">resolution</a> has been
+						finalized and consensus reached, it should be
+						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>.
+
+					</p>
 <p>
-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 <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.
-              </p>
+
+						Business for the board 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.
+
+					</p>
 <p>
-The submission should include:
-                </p>
+
+						The board 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
+						lists are CC'd (rather than the general incubator
+						list). Please treat responses with appropriate
+						confidentiality.
+
+					</p>
+<p>The submission should include:</p>
 <ul>
-                  <li>A clear subject (for example <em>Establish Foo TLP</em>)</li>
-                  <li>A brief introduction</li>
-                  <li>The name of proposed VP</li>
-                  <li>Links to the VOTE threads</li>
-                  <li>Summary of the VOTE results</li>
-                  <li>The <a href="#resolution">resolution</a> text</li>
-                </ul>
-<p>
-For example:
-                </p>
+						<li>A clear subject (for example <em>Establish Foo TLP</em>)</li>
+						<li>A brief introduction</li>
+						<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>
+					</ul>
+<p>For example:</p>
 <div class="note">
 <note><pre>
 --
@@ -549,217 +817,125 @@
 --
 References:
 
-    Home: &lt;project home page&gt;
-    Vote by project: &lt;link to vote thread on project list&gt;
-    Vote by incubator: &lt;link to vote thread on general list&gt;
+	Home: &lt;project home page&gt;
+	Vote by project: &lt;link to vote thread on project list&gt;
+	Vote by incubator: &lt;link to vote thread on general list&gt;
 
 Resolution draft:
 
-    &lt;&lt;resolution goes here, 72 characters wide,
-     indent with 4 spaces&gt;&gt;
+	&lt;&lt;resolution goes here, 72 characters wide,
+	 indent with 4 spaces&gt;&gt;
 
 --
 &lt;your e-mail sig, if you have one&gt;
 </pre></note>
 </div>
 <p>
-Please try to keep the board 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 observe Board meetings. To follow the
-progress of a <a href="#resolution">resolution</a>, please ask a friendly Member or 
-<a href="http://www.apache.org/foundation/board/">Director</a>.  
-                </p>
-</div>
-</div>
-           <h2><img src="/images/redarrow.gif" />
-   <a name="subproject">Graduation To A Subproject</a>
-</h2>
-<div class="section-content">
-<p>
-                Subprojects are accepted by a Project Management Committee. 
-				The Incubator Project Management Committee needs to approve 
-				the graduation of the podling to a subproject.
-            </p>
-<h3>
-   <a name="subproject-acceptance">Subproject Acceptance VOTE</a>
-</h3>
-<div class="section-content">
-<p>
- 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>
-</div>
-<h3>
-   <a name="subproject-graduation">Graduation Approval VOTE</a>
-</h3>
-<div class="section-content">
-<p>
- 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 project has VOTEd to accept the subproject. 
-                </p>
+
+						Please try to keep the board 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
+						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>.
+
+					</p>
 </div>
 </div>
-           <h2><img src="/images/redarrow.gif" />
-   <a name="project-needs">Some Things A Project Needs To Understand</a>
-</h2>
-<div class="section-content">
 <h3>
-   <a name="releases">How To Create An Apache Release</a>
+   <a name="subproject">Graduating to a subproject</a>
 </h3>
 <div class="section-content">
-<blockquote cite="http://catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html">
 <p>
-Release Early, Release Often
-</p>
-<div align="right"><p>
-<a href="http://catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html">Eric Steven Raymond</a>
-</p></div>
-                </blockquote>
-<p>
-Projects need to cut releases. Apache projects need to understand how to
-cut Apache releases.
-                 </p>
-<p>
-Podlings do not need to actually publish a release to demonstrate that
-they understand how to accomplish such a feat. However, creating a release that is approved
-by the <a href="incubation/Roles_and_Responsibilites.html#Incubator+Project+Management+Committee+%28PMC%29">
-incubator project management committee</a> is 
-usually the simplest way to do this. 
-                 </p>
-<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 
-<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a> 
-without problems.
+
+					Subprojects are accepted by a Project Management
+					Committee. The Incubator Project Management Committee
+					needs to approve the graduation of the podling to a
+					subproject.
+
 				</p>
-</div>
-</div>
-           <h2><img src="/images/redarrow.gif" />
-   <a name="notes">Notes</a>
-</h2>
-<div class="section-content">
-<h3>
-   <a name="notes-status">On The Status File</a>
-</h3>
+<h4>
+   <a name="sp-community-vote">Community Graduation Vote</a>
+</h4>
 <div class="section-content">
 <p>
-                The status file records and summarizes incubation-related 
-                information on the podling.  
-                The <a href="ppmc.html#Incubator+ASF+Board+Reports">PPMC</a>
-                is responsible for keeping this file current.
-                </p>
+
+						A community needs to be willing to govern itself
+						before it can become a top level project. A good way
+						to demonstrate this is through a free vote (by the
+						community) on the graduation proposal.
+
+					</p>
 <p>
-<a href="http://incubator.apache.org/projects/juddi.html">This</a> is one example.
-                </p>
+
+						This vote is not a requirement but is recommended. It
+						is unlikely that <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
+						members will vote to approve graduation unless the <a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>
+						and community positively express their readiness for
+						graduation. It is wise to copy the <a href="lists.html#general+at+incubator.apache.org">incubator
+						general list</a> and the <a href="/incubation/Roles_and_Responsibilities.html#Sponsor">sponsoring
+						top level project</a> when the vote is proposed.
+
+					</p>
 </div>
-<h3>
-   <a name="notes-community">On Community</a>
-</h3>
-<div class="section-content">
-<p>
-Apache projects are self-sustaining and self-governing communities.
-Long term success and health requires that these communities understand how to:
-                </p>
-<ul>
-                	<li>recruit users, developers, committers and PMCers</li>
-                	<li>take responsible collective action</li>
-					<li>disagree in public on technical matters without destroying personal relationships</li>
-					<li>create an open, positive and inclusive atmosphere on the mailing lists</li>
-				</ul>
-<p>
-Graduation tests whether (in the opinion of the 
-<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>)
-a podling has learned enough and is responsible enough to sustain itself as such a community.
-				</p>
-<p>
-					Read more on how to successfully build an open and diverse community for your podling in
-					the <a href="community.html">community guide</a>.
-				</p>
 <h4>
-   <a name="community-vote">Community Graduation Vote</a>
+   <a name="subproject-acceptance">Subproject Acceptance VOTE</a>
 </h4>
 <div class="section-content">
 <p>
-A community needs to be willing to govern itself before it can become a top level project.
-A good way to demonstrate this is through a free vote (by the community) on the graduation proposal.
 
-                        </p>
-<p>
-This vote is not a requirement but is recommended. It is unlikely that 
-<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a> 
-members will vote to approve graduation unless 
-the 
-<a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>
-and community positively express their readiness for graduation.
-It is wise to copy the <a href="lists.html#general+at+incubator.apache.org">incubator general list</a> 
-and (in the case of graduation as a subproject) the 
-<a href="/incubation/Roles_and_Responsibilities.html#Sponsor">sponsoring top level project</a> when the
-vote is proposed.
-                    </p>
-</div>
+						 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>
 </div>
-<h3>
-   <a name="notes-issues">On Remaining Obstacles</a>
-</h3>
-<div class="section-content">
-<p>
-How to resolve remaining obstacles preventing graduation depends on the nature
-of these obstacles. Notes on a few follow. 
-<a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a> should be able to answer
-other questions (or point out those people who can).
-                </p>
 <h4>
-   <a name="notes-releases">Creating A Release</a>
+   <a name="subproject-graduation">Graduation Approval VOTE</a>
 </h4>
 <div class="section-content">
 <p>
-The easiest way for a podling to demonstrate the ability to create Apache releases is
-to create one. The 
-<a href="/incubation/Incubation_Policy.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a> 
-checks form and not function. It is occasionally convenient to 
-cut a release for verification where the form is correct but the actual code function is not 
-entirely suitable for users and this is fine.
+
+						To graduate as a subproject, the mentors 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
+                        project has VOTEd to accept the subproject.
+
 					</p>
-<p>
-See (for technical details): 
-                	</p>
-<ul>
-						<li>
-<a href="http://www.apache.org/dev/index.html#releases">Apache Release Documentation</a>
-						</li>
-						<li>
-<a href="releasemanagement.html">Incubator Release Guide</a>
-						</li>
-                	</ul>
 </div>
 </div>
+</div>
+           <h2><img src="/images/redarrow.gif" />
+   <a name="life-after-graduation">Life after graduation</a>
+</h2>
+<div class="section-content">
 <h3>
    <a name="notes-on-hand-over">On The Handover</a>
 </h3>
 <div class="section-content">
 <p>
-This is the transfer of virtual resources from the care of 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.		
+
+					This is the transfer of virtual resources from the care of
+                    the IPMC to the care of either the new or existing top
+                    level project taking charge of the graduating community.
+
 				</p>
 <h4>
    <a name="existing-project-hand-over">Graduating As Subproject</a>
 </h4>
 <div class="section-content">
 <p>
-This is the simple case. The 
-<a href="/incubation/Roles_and_Responsibilities.html#Chair+of+the+Incubator+PMC">IPMC Chair</a>
-and the Chair of the project accepting the graduating community organize the handover
-between themselves.
+
+						This is the simple case. The <a href="/incubation/Roles_and_Responsibilities.html#Chair+of+the+Incubator+PMC">IPMC
+                        Chair</a> and the Chair of the project accepting the
+                        graduating community organize the handover between
+                        themselves.
+
 					</p>
 </div>
 <h4>
@@ -767,96 +943,100 @@
 </h4>
 <div class="section-content">
 <p>
-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 
-<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 favorite director.
-					</p>
-<p>
-The Board resolution 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 as granting power to
-act on behalf of Apache.  
+
+						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 <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
+                        favorite director.
+
+					</p>
+<p>
+
+						The board resolution 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
+                        as granting power to act on behalf of Apache.
+
 					</p>
 <p>
-Once appointed, the new Chair needs to:
+						Once appointed, the new Chair needs to:
 					</p>
 <ul>
-						<li>
-Subscribe to the <code>board</code> mailing list
-						</li>
-						<li>
-Subscribe to the infrastructure mailing list
-						</li>
-						<li>
-Ensure that they have been added to the PMC chairs group in svnauth
-						</li>
-						<li>
-Review appropriate documentation:
+
+						<li>Subscribe to the board mailing list</li>
+						<li>Subscribe to the infrastructure mailing list</li>
+						<li>Ensure that they have been added to the PMC chairs group in svnauth</li>
+						<li>Review appropriate documentation:
 							<ul>
 								<li>
-<a href="http://www.apache.org/dev/pmc.html#chair">PMC Chair Duties</a>
+									<a href="http://www.apache.org/dev/pmc.html#chair">PMC Chair Duties</a>
 								</li>
 								<li>
-PMC <a href="http://www.apache.org/dev/#pmc">documentation</a>
+									PMC <a href="http://www.apache.org/dev/#pmc">documentation</a>
 								</li>
 								<li>
-Jakarta <a href="http://wiki.apache.org/jakarta/RoleOfChair">Chair guide</a>
+									Jakarta <a href="http://wiki.apache.org/jakarta/RoleOfChair">Chair guide</a>
 								</li>
-							    <li>
-Incubator <a href="http://incubator.apache.org/guides/chair.html">Chair guide</a>
+								<li>
+									Incubator <a href="http://incubator.apache.org/guides/chair.html">Chair guide</a>
 								</li>
-							    <li>
-Reporting <a href="http://www.apache.org/foundation/board/calendar.html">calendar</a>
+								<li>
+									Reporting <a href="http://www.apache.org/foundation/board/calendar.html">calendar</a>
 								</li>
 							</ul>
 						</li>
 						<li>
-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.
+							Work out a reporting schedule with the board. For
+                            the first three months after graduation this will
+                            be monthly. After that, the project should slot
+                            into a quarterly reporting schedule.
 						</li>
 						<li>
-Work with infrastructure to set up the lists for the new project.
+							Work with infrastructure to set up the lists for
+                            the new project.
 						</li>
 					</ul>
 <p>
-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 <a href="#resolution">resolution</a>. However, the Chair of the new project
-needs to ensure that private list is created and the membership subscribed.
-					</p>
-<p>
-Members of the new PMC need to:
+
+						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>
+<p>Members of the new PMC need to:</p>
 <ul>
-						<li>
-Subscribe to the private mailing list for the project
-						</li>
-						<li>
-Review appropriate documentation:
+						<li>Subscribe to the private mailing list for the project</li>
+						<li>Review appropriate documentation:
 							<ul>
 								<li>
-Apache <a href="http://www.apache.org/dev/pmc.html">PMC Guide</a>
+								Apache <a href="http://www.apache.org/dev/pmc.html">PMC Guide</a>
 								</li>
 								<li>
-Related <a href="http://www.apache.org/dev/#pmc">documentation</a>
+								Related <a href="http://www.apache.org/dev/#pmc">documentation</a>
 								</li>
 							</ul>
 						</li>
 					</ul>
 <p>
-Once all this is in place, resources can start to be handed over 
-to the new project.
+
+						Once all this is in place, resources can start to be
+                        handed over to the new project.
+
 					</p>
 <p>
-Please continue to hang around the Incubator and help new podlings have
-an easier time than you did!
+
+						Please continue to hang around the Incubator and help
+                        new podlings have an easier time than you did!
+
 					</p>
 </div>
 </div>
@@ -865,189 +1045,214 @@
 </h3>
 <div class="section-content">
 <p>
-	                Graduation is the first step in what is hopefully a long
-	                road. There are some issues which incubation may not
-	                cover.
-	            </p>
-<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>
+
+					Graduation is the first step in what is hopefully a long road.
+	                There are some issues which incubation may not cover.
+
+				</p>
 <h4>
    <a name="transfer">Transferring Resources</a>
 </h4>
 <div class="section-content">
 <p>
-	When a project graduates, then the infrastructure resources (mailing lists, websites, source, etc.) 
-	need to be transferred from the Incubator to a project's new home.
-	                </p>
-<p>
-	 Checklist:
-	                </p>
+
+						When a project graduates, then the infrastructure
+	                    resources (mailing lists, websites, source, etc.) need to
+	                    be transferred from the Incubator to a project's new home.
+
+					</p>
+<p>Checklist:</p>
 <ol>
-	                    <li>Source
-	                        <ol>
-	                        <li>
-Post an announcement to the development list telling everyone that the 
-repository is about to be moved	                        
-	                        </li>
-	                        <li>
-	                        <code>svn move</code>
-	                        the podling source tree
-	                        </li><li>
-Post an announcement containing instructions for developers 
-describing how to <code>svn switch</code> their workspaces
-                            </li>
-							<li>
-Update site, wikis, <code>pom.xml</code> and other resources to point to the new repository 
-location.
-							</li>
-                            </ol>
-	                    </li>
-	                    <li>
-	                        Websites
-	                        <ol>
-	                            <li>
-	Transfer the podling website
-	                            <ol>
-	                                <li>
-	    Load the website into its new home.
-	    See <a href="http://www.apache.org/dev/#web">infra notes</a>.
-	                                </li>
-	                                <li>
-	    Use a  <code>.htaccess</code> entry to redirect traffic from the old URLs to the new.
-	                                </li>
-	                                <li>
-	    Delete the podling website from <code>/www/incubator.apache.org</code> on 
-	    <code>people.apache.org</code>.
-	                                </li>
-	                                <li>
-Post an announcement to user and development lists
-	                                </li>
+						<li>Source
+							<ol>
+								<li>
+
+									Post an announcement to the development list
+	                                telling everyone that the repository is about
+	                                to be moved
+
+								</li>
+								<li>
+									<code>svn move</code> the podling source tree
+								</li>
+								<li>
+
+									Post an announcement containing instructions
+	                                for developers describing how to <code>svn
+	                                switch</code> their workspaces
+
+								</li>
+								<li>
+
+									Update site, wikis, <code>pom.xml</code> and
+	                                other resources to point to the new repository
+	                                location.
+
+								</li>
+							</ol>
+						</li>
+						<li>
+							Websites
+							<ol>
+								<li>Transfer the podling website
+									<ol>
+										<li>
+
+											Load the website into its new home.
+	                                        See <a href="http://www.apache.org/dev/#web">infra
+	                                        notes</a>.
+
+										</li>
+										<li>
+
+											Use a <code>.htaccess</code> entry to
+	                                        redirect traffic from the old URLs to
+	                                        the new.
+
+										</li>
+										<li>
+
+											Delete the podling website from
+	                                        <code>/www/incubator.apache.org</code>
+	                                        on <code>people.apache.org</code>.
+
+										</li>
+										<li>
+
+											Post an announcement to user and
+	                                        development lists
+
+										</li>
+										<li>
+
+											When using Maven: update
+	                                        <code>pom.xml</code> for the location
+	                                        of the website, as well as the place
+	                                        where the site plugin will deploy the
+	                                        web site (when applicable).
+
+										</li>
+									</ol>
+								</li>
+								<li>Update the Incubator site
+									<ol>
+										<li>
+
+											Update the Incubator <a href="http://incubator.apache.org/projects/index.html">status
+	                                        page</a>
+
+										</li>
+										<li>
+
+											Update the podling <a href="#notes-status">status page</a>.
+	                                        All sections should now be filled in
+	                                        including <em>EXIT</em>. Take some
+	                                        time to read carefully since this page
+	                                        forms the final public record for
+	                                        graduation.
+
+										</li>
+										<li>Remove the podling from <code>project.xml</code></li>
+										<li>Regenerate the Incubator website</li>
+										<li>Commit</li>
+										<li>Update the Incubator website</li>
+									</ol>
+								</li>
+								<li>Wiki
+									<ol>
+									<li>
+
+										<em>(Top level projects)</em> <a href="http://www.apache.org/dev/reporting-issues.html#wiki">request</a>
+	                                    a new wiki (if it is a moinmoin based wiki).
+
+									</li>
 									<li>
-When using Maven: update <code>pom.xml</code> for the location of the website, as well as 
-the place where the site plugin will deploy the web site (when applicable).
+
+										Transfer podling related content from the
+	                                    <a href="http://wiki.apache.org/incubator/">Incubator
+	                                    wiki</a> to the project wiki
+
 									</li>
-	                            </ol></li>
-	                            <li>Update the Incubator site
-	                                <ol>
-	                                    <li>
-	Update the Incubator <a href="http://incubator.apache.org/projects/index.html">status page</a>
-	                                    </li>
-	                                    <li>
-	Update the podling <a href="#notes-status">status page</a>. 
-	All sections should now be filled in including <em>EXIT</em>.
-	Take some time to read carefully since this page forms the final public record for graduation.
-	                                    </li>
-	                                    <li>
-	Remove the podling from <code>project.xml</code>
-	                                    </li>
-	                                    <li> 
-	Regenerate the Incubator website
-	                                    </li>
-	                                    <li>
-	Commit
-	                                    </li>
-	                                    <li>
-	Update the Incubator website
-	                                    </li>
-	                                 </ol>
-	                            </li>
-	                            <li>Wiki
-	                                <ol>
-	                                    <li>
-	<em>(Top level projects)</em> 
-	<a href="http://www.apache.org/dev/reporting-issues.html#wiki">request</a> a new wiki.
-	                                    </li>
-	                                    <li>
-	 Transfer podling related content from 
-	 the <a href="http://wiki.apache.org/incubator/">Incubator wiki</a> to the project wiki
-	                                    </li>
-	                                    <li>
-Post an announcement to user and development lists
-	                                    </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
-	                        <ol>
-	                            <li>
-	<a href="http://www.apache.org/dev/reporting-issues.html#mail">Request</a>
-	that podlings lists be transferred to their new home. Any new mailing lists should
-	be requested at the same time.
-	                            </li>
-	                            <li>
-When this has been executed by infrastructure, post an announcement to user
-and development lists
-	                            </li>
+									<li>
+										Make sure your documentation points to the new wiki address
+									</li>
+									<li>
+										Post an announcement to user and development lists
+									</li>
+									</ol>
+								</li>
+							</ol>
+						</li>
+						<li>Mailing lists
+							<ol>
 								<li>
-When using Maven: update <code>pom.xml</code> for the new mailing list address(es). Also update any
-documents on your website that show how to subscribe to the lists and/or find archives.
+
+									<a href="http://www.apache.org/dev/reporting-issues.html#mail">Request</a>
+		                            that podlings lists be transferred to their new
+		                            home. Any new mailing lists should be requested at
+		                            the same time.
+
+								</li>
+
+								<li>
+
+									When this has been executed by infrastructure,
+		                            post an announcement to user and development lists
+
 								</li>
 								<li>
-Send notice to <a href="http://nabble.com">nabble.com</a> (if they archive your 
-incubator mailing list) that the address has changed, and possibly the location 
-of your project (if it is listed as being part of the incubator). Repeat for other
-known mailing list archivers.
+
+									When using Maven: update <code>pom.xml</code> for
+		                            the new mailing list address(es). Also update any
+		                            documents on your website that show how to
+		                            subscribe to the lists and/or find archives.
+
+								</li>
+								<li>
+
+									Send notice to <a href="http://nabble.com">nabble.com</a> (if they
+		                            archive your incubator mailing list) that the
+		                            address has changed, and possibly the location of
+		                            your project (if it is listed as being part of the
+		                            incubator). Repeat for other known mailing list
+		                            archivers.
+
+								</li>
+							</ol>
+						</li>
+						<li>Issue Tracking
+							<ol>
+								<li>
+
+									Check that the issue tracking system used by the
+		                            podling reflects the project's new status.
+
 								</li>
-								
-	                        </ol>
-	                    </li>
-	                    <li>Issue Tracking
-	                        <ol>
-	                            <li>
-	Check that the issue tracking system used by the podling 
-        reflects the project's new status. In particular, the email 
-        notifications should be changed to refer to the new email alias 
-        for the project.
-	                            </li>
-	                        </ol>
-	                    </li>
-	                </ol>
+							</ol>
+						</li>
+					</ol>
 </div>
-<h4>
+</div>
+<h3>
    <a name="security">Security</a>
-</h4>
+</h3>
 <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>
-</div>
+
+					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>
          </td>



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


Mime
View raw message