incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject svn commit: r1165623 [2/2] - /incubator/public/trunk/site-author/guides/graduation.xml
Date Tue, 06 Sep 2011 12:03:19 GMT

Modified: incubator/public/trunk/site-author/guides/graduation.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/graduation.xml?rev=1165623&r1=1165622&r2=1165623&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/graduation.xml [utf-8] (original)
+++ incubator/public/trunk/site-author/guides/graduation.xml [utf-8] Tue Sep  6 12:03:19 2011
@@ -1,291 +1,290 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!--
-	Licensed under the Apache License, Version 2.0 (the "License");
-	you may not use this file except in compliance with the License.
-	You may obtain a copy of the License at
-
-	http://www.apache.org/licenses/LICENSE-2.0
-
-	Unless required by applicable law or agreed to in writing, software
-	distributed under the License is distributed on an "AS IS" BASIS,
-	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-	See the License for the specific language governing permissions and
-	limitations under the License.
+    Licensed under the Apache License, Version 2.0 (the "License");
+    you may not use this file except in compliance with the License.
+    You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
 -->
 <document>
-	<properties>
-		<title>Guide to Successful Graduation</title>
-		<atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
-	</properties>
-	<body>
-		<section id="preamble">
-			<title>Guide to Successful Graduation</title>
-			<section id='TOC'><title>Contents</title><toc/></section>
-			<section id="abstract">
-				<title>Abstract</title>
-				<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>
+    <properties>
+        <title>Guide to Successful Graduation</title>
+        <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
+    </properties>
+    <body>
+        <section id="preamble">
+            <title>Guide to Successful Graduation</title>
+            <section id='TOC'><title>Contents</title><toc/></section>
+            <section id="abstract">
+                <title>Abstract</title>
+                <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>        
                 <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 
+                  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+at+incubator.apache.org">general</a> list at
-          incubator.
+                  incubator.
                 </p>
-			</section>
-		</section>
-		<section id="introduction">
-			<title>What is Graduation?</title>
-			<p>
-
-				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 <code><a 
+            </section>
+        </section>
+        <section id="introduction">
+            <title>What is Graduation?</title>
+            <p>
+                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 <code><a 
                 href='http://www.apache.org/foundation/voting.html'>VOTE</a></code>. 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 <a
+                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 <a
                 href="../incubation/Incubation_Policy.html#Graduating+from+the+Incubator">this</a>
                 section. Please post any questions about graduation
-				to the <a href="lists.html#general+at+incubator.apache.org">general incubator list</a>.
+                to the <a href="lists.html#general+at+incubator.apache.org">general incubator list</a>.
 
-			</p>
-			<section id='subproject-or-top-level'>
-				<title>Whether to Graduate to Subproject or to Top Level Project</title>
-				<p>
-					Each proposal has a <a
-					href='/incubation/Roles_and_Responsibilities.html#Sponsor'>Sponsor</a>.
-					The identity of the Sponsor indicates the natural
-					destination. For proposals sponsored by the <a 
+            </p>
+            <section id='subproject-or-top-level'>
+                <title>Whether to Graduate to Subproject or to Top Level Project</title>
+                <p>
+                    Each proposal has a <a
+                    href='/incubation/Roles_and_Responsibilities.html#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. However, the
-					destination is fixed only 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 <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 <code><a 
+                    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. However, the
+                    destination is fixed only 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 <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 <code><a 
                     href='http://www.apache.org/foundation/voting.html'>VOTE</a></code> 
                     is to approve the
-					transfer. For those seeking to graduation as a top level
-					project, this will be a recommendation to the <a 
+                    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>
-			</section>
-		</section>
-		<section id="requirements">
-			<title>Before You Graduate</title>
-			<p>
+                    Expect IPMC-ers to ask questions about the project
+                    including about the choice of destination. This is part of
+                    the normal process.
+
+                </p>
+            </section>
+        </section>
+        <section id="requirements">
+            <title>Before You Graduate</title>
+            <p>
 
-				Before you start thinking about graduation, you need to make 
+                Before you start thinking about 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.
+                This section will provide a shortlist for podlings to
+                determine if they meet the criteria for asking graduation.
 
-			</p>
+            </p>
 
-			<section id='checklist'>
-				<title>Graduation Check List</title>
-				<p>
+            <section id='checklist'>
+                <title>Graduation Check List</title>
+                <p>
 
-					The following is a short checklist giving an overview, not
-					a substitute for reading the content below.
+                    The following is a short checklist giving an overview, not
+                    a substitute for reading the content below.
 
-				</p>
-				<ol>
-					<li>Preparations
-						<ul>
-							<li>
+                </p>
+                <ol>
+                    <li>Preparations
+                        <ul>
+                            <li>
 
-								Complete (and sign off) tasks documented in
-								the <a href='#notes-status'>status file</a>
+                                Complete (and sign off) tasks documented in
+                                the <a href='#notes-status'>status file</a>
 
-							</li>
-							<li>
+                            </li>
+                            <li>
 
-								Demonstrate ability to <a
-								href='#releases'>create Apache releases</a>
+                                Demonstrate ability to <a
+                                href='#releases'>create Apache releases</a>
 
-							</li>
-							<li>
+                            </li>
+                            <li>
 
-								Demonstrate <a href='#community'>community
+                                Demonstrate <a href='#community'>community
                                 readiness</a>
 
-							</li>
-							<li>
+                            </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>
+                                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>
+                            </li>
+                        </ul>
+                    </li>
+                    <li>
 
-						Decide upon <a
-						href='#subproject-or-top-level'>destination</a>
+                        Decide upon <a
+                        href='#subproject-or-top-level'>destination</a>
 
-					</li>
-					<li>
+                    </li>
+                    <li>
 
-						Prepare a <a href='#tlp-resolution'>resolution</a>
-						<em>(top level candidates only)</em>.
+                        Prepare a <a href='#tlp-resolution'>resolution</a>
+                        <em>(top level candidates only)</em>.
 
-					</li>
+                    </li>
 
-					<li>
+                    <li>
 
-						<a href='#subproject-acceptance'>Subproject acceptance
-						<code>VOTE</code></a> by destination Project <em>(subproject
-						candidates only)</em>
+                        <a href='#subproject-acceptance'>Subproject acceptance
+                        <code>VOTE</code></a> by destination Project <em>(subproject
+                        candidates only)</em>
 
-					</li>
-					<li>
+                    </li>
+                    <li>
 
-						<a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator PMC (IPMC)</a>:
-						<ul>
-							<li>
+                        <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator PMC (IPMC)</a>:
+                        <ul>
+                            <li>
 
-								For top level candidates, this is a <a
-								href='#ipmc-top-level-recommendation'>recommendation
-								<code>VOTE</code></a>
+                                For top level candidates, this is a <a
+                                href='#ipmc-top-level-recommendation'>recommendation
+                                <code>VOTE</code></a>
 
-							</li>
-							<li>
+                            </li>
+                            <li>
 
-								For subproject candidates, this is a <a
-								href='#subproject-graduation'>graduation
-								approval <code>VOTE</code></a>
+                                For subproject candidates, this is a <a
+                                href='#subproject-graduation'>graduation
+                                approval <code>VOTE</code></a>
 
-							</li>
-						</ul>
-					</li>
-					<li>
-						Final <a href='#notes-on-hand-over'>hand-over</a>
-					</li>
-					<li>
+                            </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>
+                        Consider post graduation <a
+                        href='#project-first-steps'>tasks</a>
 
-					</li>
-				</ol>
-			</section>
+                    </li>
+                </ol>
+            </section>
 
-			<section id='notes-status'>
-				<title>Checking the Status File</title>
-				<p>
+            <section id='notes-status'>
+                <title>Checking the Status File</title>
+                <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.
+                    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>
+                </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 <a 
+                    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 <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.
-
-				</p>
-				<p>
-
-					The status file of the JUDDI project is <a
-					href='http://incubator.apache.org/projects/juddi.html'>one
-					example</a>.
-
-				</p>
-			</section>
-
-			<section id='releases'>
-				<title>Creating an Apache Release</title>
-				<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.
+                    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>
+            </section>
+
+            <section id='releases'>
+                <title>Creating an Apache Release</title>
+                <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>
 
-				</p>
-				<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.
 
-					Podlings do not need to actually <em>publish</em> a
+                </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
@@ -293,109 +292,109 @@
                     incubator project management committee</a> is usually the
                     simplest way to do this.
 
-				</p>
-				<p>
+                </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>
+            </section>
+
+            <section id="community">
+                <title>Creating an Open and Diverse community</title>
+                <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>
-			</section>
-
-			<section id="community">
-				<title>Creating an Open and Diverse community</title>
-				<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.
+                    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>
                 <p>
 
-					Apache projects are self-sustaining and self-governing
+                    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>
+                    <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
+                    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>
+                </p>
+                <p>
 
-					Read more on how to successfully build an open and diverse
+                    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>
+                </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>
 
-					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.
+                    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>
+                </p>
+                <p>
 
-					Growing an open and diverse meritocratic community is not
+                    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>
-			</section>
+                </p>
+            </section>
             <section id='notes-issues'>
               <title>Other Issues</title>
               <p>
@@ -408,231 +407,231 @@
                     resolution that are not covered. 
               </p>
             </section>
-		</section>
-		<section id="process">
-			<title>The Graduation Process</title>
+        </section>
+        <section id="process">
+            <title>The Graduation Process</title>
 
-			<section id="toplevel">
-				<title>Graduating to a Top Level Project</title>
+            <section id="toplevel">
+                <title>Graduating to a Top Level Project</title>
 
-				<p>
+                <p>
 
-					Top level projects are created by 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
-					graduate to a top level project.
+                    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>
+                </p>
+                <p>
 
-					Graduation to a top level project requires:
+                    Graduation to a top level project requires:
 
-					<ul>
+                    <ul>
                         <li>a charter for your project</li>
-						<li>a positive community graduation <code><a 
+                        <li>a positive community graduation <code><a 
                         href='http://www.apache.org/foundation/voting.html'>VOTE</a></code></li>
-						<li>a positive IPMC recommendation <code><a 
+                        <li>a positive IPMC recommendation <code><a 
                         href='http://www.apache.org/foundation/voting.html'>VOTE</a></code></li>
-						<li>the acceptance of the <a href='#tlp-resolution'>resolution</a> by the Board</li>
-					</ul>
+                        <li>the acceptance of the <a href='#tlp-resolution'>resolution</a> 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>
 
-					This process can take a while, since it typically sparks
-					some discussion inside the community and possibly in the
-					IPMC.
-
-				</p>
-				<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>
+                    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.
 
-				<img border="0" src="graduation-timeline.png"
+                </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>
+                <p>
 
-					For each event we scheduled one or two weeks. Even though
-					a <code><a 
+                    For each event we scheduled one or two weeks. Even though
+                    a <code><a 
                     href='http://www.apache.org/foundation/voting.html'>VOTE</a></code> 
                     is usually limited to 72 hours, you should prepare
-					for discussion and possibly having to cast a revote with a
-					revised proposal.
+                    for discussion and possibly having to cast a revote with a
+                    revised proposal.
 
-				</p>
+                </p>
 
-				<section id='tlp-community-vote'>
-					<title>Community Graduation Vote</title>
+                <section id='tlp-community-vote'>
+                    <title>Community Graduation Vote</title>
 
-					<p>
+                    <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 <code><a 
+                        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 <code><a 
                         href='http://www.apache.org/foundation/voting.html'>VOTE</a></code> (by the
-						community) on the graduation proposal.
+                        community) on the graduation proposal.
+
+                    </p>
+                    <p>
 
-					</p>
-					<p>
+                        This <code>VOTE</code> 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.
 
-						This <code>VOTE</code> 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>
-				</section>
-
-				<section id='tlp-resolution'>
-					<title>Preparing a Charter</title>
-					<p>
+                    </p>
+                </section>
 
-						So, in this case a suitable <a 
+                <section id='tlp-resolution'>
+                    <title>Preparing a Charter</title>
+                    <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 
+                        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>
-					<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 
+                        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 <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
-						the eve of graduation.
+                        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>
+                    </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.
+                        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>
+                    </p>
+                    <p>
 
-						If you read these resolutions you also see that you
+                        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 
                         <a href='ppmc.html'>PPMC</a> to choose one
                         person to act as the chair after graduation.
 
-					</p>
-				</section>
-				<section id='ipmc-top-level-recommendation'>
-					<title>The Recommendation Vote</title>
-					<p>
-
-						The <a href='#tlp-resolution'>resolution</a> should be proposed on the general
-                                                <a href="mailto:general@incubator.apache.org">
-						incubator list</a> before a <code><a href='http://www.apache.org/foundation/voting.html'>VOTE</a></code> 
+                    </p>
+                </section>
+                <section id='ipmc-top-level-recommendation'>
+                    <title>The Recommendation Vote</title>
+                    <p>
+
+                        The <a href='#tlp-resolution'>resolution</a> should be proposed on the general
+                        <a href="mailto:general@incubator.apache.org">
+                        incubator list</a> before a <code><a href='http://www.apache.org/foundation/voting.html'>VOTE</a></code> 
                         is started to allow feedback. Once a consensus has been reached, a <code>VOTE</code>
-						should be started on the same general incubator list by a member of the <a href='ppmc.html'>PPMC</a> proposing
-						that the <a
-						href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
-						recommends the resolution to the <a 
+                        should be started on the same general incubator list by a member of the <a href='ppmc.html'>PPMC</a> 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>
-				</section>
-				<section id='top-level-board-proposal'>
-					<title>Submission of the Resolution to the Board</title>
-					<p>
-
-						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='#tlp-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>
+                </section>
+                <section id='top-level-board-proposal'>
+                    <title>Submission of the Resolution to the Board</title>
+                    <p>
+
+                        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='#tlp-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>
+                    </p>
+                    <p>
 
-						Business for the <a 
+                        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.
+                        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>
+                    </p>
+                    <p>
 
-						The <code>board</code> list is private. 
+                        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='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>
-					<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 <code>VOTE</code> threads</li>
-						<li>Summary of the <code>VOTE</code> results</li>
-						<li>The <a href='#tlp-resolution'>resolution</a> text</li>
-					</ul>
-					<p>For example:</p>
+                        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 <code>VOTE</code> threads</li>
+                        <li>Summary of the <code>VOTE</code> results</li>
+                        <li>The <a href='#tlp-resolution'>resolution</a> text</li>
+                    </ul>
+                    <p>For example:</p>
 <note><pre>
 --
 From: &lt;you _at_ apache dot org&gt;
@@ -652,96 +651,96 @@ consider the draft resolution below at y
 --
 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>
-					<p>
+                    <p>
 
-						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 <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a> 
+                        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 <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>.
-
-					</p>
-				</section>
-			</section>
-			<section id="subproject">
-				<title>Graduating to a Subproject</title>
-				<p>
+                        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>.
 
-					Subprojects are accepted by a Project Management
-					Committee. The <a
+                    </p>
+                </section>
+            </section>
+            <section id="subproject">
+                <title>Graduating to a Subproject</title>
+                <p>
+
+                    Subprojects are accepted by a Project Management
+                    Committee. The <a
                     href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator Project Management Committee</a>
-					needs to approve the graduation of the podling to a
-					subproject.
+                    needs to approve the graduation of the podling to a
+                    subproject.
 
-				</p>
+                </p>
 
-				<section id='sp-community-vote'>
-					<title>Community Graduation Vote</title>
+                <section id='sp-community-vote'>
+                    <title>Community Graduation Vote</title>
 
-					<p>
+                    <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 
+                        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 
                         <code><a href='http://www.apache.org/foundation/voting.html'>VOTE</a></code>
                         (by the community) on the graduation proposal.
 
-					</p>
-					<p>
+                    </p>
+                    <p>
 
-						This <code>VOTE</code> 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 <code>VOTE</code>
+                        This <code>VOTE</code> 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 <code>VOTE</code>
                         is proposed.
 
-					</p>
-				</section>
+                    </p>
+                </section>
 
-				<section id='subproject-acceptance'>
-					<title>Subproject Acceptance Vote</title>
-					<p>
+                <section id='subproject-acceptance'>
+                    <title>Subproject Acceptance Vote</title>
+                    <p>
 
-						 A formal <code><a 
+                         A formal <code><a 
                          href='http://www.apache.org/foundation/voting.html'>VOTE</a></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>
-				</section>
-				<section id='subproject-graduation'>
-					<title>Graduation Approval Vote</title>
-					<p>
+                         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.
 
-						To graduate as a subproject, the <a 
+                     </p>
+                </section>
+                <section id='subproject-graduation'>
+                    <title>Graduation Approval Vote</title>
+                    <p>
+
+                        To graduate as a subproject, the <a 
                         href='/incubation/Roles_and_Responsibilities.html#Mentor'>Mentors</a> 
                         should start a <code><a 
                         href='http://www.apache.org/foundation/voting.html'>VOTE</a></code> 
@@ -753,43 +752,43 @@ Resolution draft:
                         subproject. This <code>VOTE</code>s should only be started once the
                         project has <code>VOTE</code>d to accept the subproject.
 
-					</p>
-				</section>
-			</section>
-		</section>
-		<section id="life-after-graduation">
-			<title>Life After Graduation</title>
-
-			<section id='notes-on-hand-over'>
-				<title>Handover</title>
-				<p>
+                    </p>
+                </section>
+            </section>
+        </section>
+        <section id="life-after-graduation">
+            <title>Life After Graduation</title>
+
+            <section id='notes-on-hand-over'>
+                <title>Handover</title>
+                <p>
 
-					This is the transfer of virtual resources from the care of
+                    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.
 
-				</p>
+                </p>
 
-				<section id='existing-project-hand-over'>
-					<title>Graduating as Subproject</title>
-					<p>
+                <section id='existing-project-hand-over'>
+                    <title>Graduating as Subproject</title>
+                    <p>
 
-						This is the simple case. The <a
+                        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>
-				</section>
+                    </p>
+                </section>
 
-				<section id='new-project-hand-over'>
-					<title>Graduating as New Top Level Project</title>
-					<p>
+                <section id='new-project-hand-over'>
+                    <title>Graduating as New Top Level Project</title>
+                    <p>
 
-						When graduating to a new project, the process is more
+                        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
@@ -802,10 +801,10 @@ Resolution draft:
                         worth someone posting a polite reminder to their
                         favorite director.
 
-					</p>
-					<p>
+                    </p>
+                    <p>
 
-						The 
+                        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>
@@ -813,68 +812,68 @@ Resolution draft:
                         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:
-					</p>
-
-					<ul>
-
-						<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. 
+                    </p>
+                    <p>
+                        Once appointed, the new Chair needs to:
+                    </p>
+
+                    <ul>
+
+                        <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. 
                             There are various ways to discover whether has been done:
                             <ul>
                               <li>
-                            Ask a friendly <a href='http://www.apache.org/foundation/members.html'>Member</a>.
+                                  Ask a friendly <a href='http://www.apache.org/foundation/members.html'>Member</a>.
                               </li>
                               <li>
-                            Examine the <code>asf-authorization-template</code> file.
-                            This is found in the 
-                            <code>https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/</code>
-                            directory of the private repository.
-                            <strong>Note</strong> that new Chairs without infrastructure
-                            karma will be unable to checkout this directory from
-                            subversion until they have PMC chair karma. So, checking
-                            out this directory is a reasonable test.
+                                  Examine the <code>asf-authorization-template</code> file.
+                                  This is found in the 
+                                  <code>https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/</code>
+                                  directory of the private repository.
+                                  <strong>Note</strong> that new Chairs without infrastructure
+                                  karma will be unable to checkout this directory from
+                                  subversion until they have PMC chair karma. So, checking
+                                  out this directory is a reasonable test.
                               </li>
                               <li>
-                            Watch for the infrastructure commit to 
-                            <code>asf-authorization-template</code>.
+                                  Watch for the infrastructure commit to 
+                                  <code>asf-authorization-template</code>.
                               </li>
-							  <li>Check out the <code>foundation/officers</code> folder from the private repository.</li>
-							  <li>Add yourself to the <code>foundation/officers/affiliations.txt</code> and the <code>foundation/officers/irs-disclosures.txt</code> files with the appropriate information.</li>
+                              <li>Check out the <code>foundation/officers</code> folder from the private repository.</li>
+                              <li>Add yourself to the <code>foundation/officers/affiliations.txt</code> and the <code>foundation/officers/irs-disclosures.txt</code> files with the appropriate information.</li>
+                            </ul>
+                        </li>
+                        <li>Review appropriate documentation:
+                            <ul>
+                                <li>
+                                    <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>
+                                </li>
+                                <li>
+                                    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>
+                                <li>
+                                    Reporting <a href='http://www.apache.org/foundation/board/calendar.html'>calendar</a>
+                                </li>
                             </ul>
                         </li>
-						<li>Review appropriate documentation:
-							<ul>
-								<li>
-									<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>
-								</li>
-								<li>
-									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>
-								<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 
+                        <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. Now is a good time to remove
                             the project from the Incubator reporting schedule.
-						</li>
-						<li>
-							Work with the <a 
+                        </li>
+                        <li>
+                            Work with the <a 
                             href='http://www.apache.org/dev/index.html#infra'>Apache Infrastructure team</a> 
                             to set up the top level project
                             infrastructure. The various infrastructure tasks that are required
@@ -884,13 +883,13 @@ Resolution draft:
                             for example). This should be created in the category 
                             <a 
                             href='https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&amp;mode=hide&amp;pid=10410&amp;sorter/order=DESC&amp;sorter/field=priority&amp;resolution=-1&amp;component=10858'>TLP Admin</a>.
-						</li>
-						<li>Add the new project to the foundation web site. You will need a member to help with this task. Instructions for updating the web site are <a href="http://www.apache.org/dev/infra-site.html">here</a>.</li>
-						<li>Add the new project's PMC chair to the <code>foundation/officers/irs-disclosures.txt</code> file. You will need a member to help with this task.</li>
-					</ul>
-					<p>
+                        </li>
+                        <li>Add the new project to the foundation web site. You will need a member to help with this task. Instructions for updating the web site are <a href="http://www.apache.org/dev/infra-site.html">here</a>.</li>
+                        <li>Add the new project's PMC chair to the <code>foundation/officers/irs-disclosures.txt</code> file. You will need a member to help with this task.</li>
+                    </ul>
+                    <p>
 
-						They should then be able to start assembling the new
+                        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 
@@ -898,252 +897,252 @@ Resolution draft:
                         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:
-							<ul>
-								<li>
-								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>
-								</li>
-							</ul>
-						</li>
-					</ul>
-					<p>
+                    </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:
+                            <ul>
+                                <li>
+                                    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>
+                                </li>
+                            </ul>
+                        </li>
+                    </ul>
+                    <p>
 
-						Once all this is in place, resources can start to be
+                        Once all this is in place, resources can start to be
                         handed over to the new project.
 
-					</p>
-					<p>
+                    </p>
+                    <p>
 
-						Please continue to hang around the Incubator and help
+                        Please continue to hang around the Incubator and help
                         new podlings have an easier time than you did!
 
-					</p>
-				</section>
-			</section>
-			<section id='project-first-steps'>
-				<title>First Steps Outside the Incubator</title>
-				<p>
-
-					Graduation is the first step in what is hopefully a long road.
-	                There are some issues which incubation may not cover.
-
-				</p>
-
-				<section id='transfer'>
-					<title>Transferring Resources</title>
-					<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>
-
-											Update the <code>incubator/site-publish/.htaccess</code> entry to
-	                                        redirect traffic from the old URLs to
-	                                        the new.  (svn location is at <code>http://svn.apache.org/repos/asf/incubator/public/trunk/site-publish/</code>)
-
-										</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.
+                    </p>
+                </section>
+            </section>
+            <section id='project-first-steps'>
+                <title>First Steps Outside the Incubator</title>
+                <p>
+
+                    Graduation is the first step in what is hopefully a long road.
+                    There are some issues which incubation may not cover.
+
+                </p>
+
+                <section id='transfer'>
+                    <title>Transferring Resources</title>
+                    <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>
 
-										</li>
+                                            Load the website into its new home.
+                                            See <a
+                                            href="http://www.apache.org/dev/#web">infra
+                                            notes</a>.
+
+                                        </li>
+                                        <li>
+
+                                            Update the <code>incubator/site-publish/.htaccess</code> entry to
+                                            redirect traffic from the old URLs to
+                                            the new.  (svn location is at <code>http://svn.apache.org/repos/asf/incubator/public/trunk/site-publish/</code>)
+
+                                        </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>
                                             Edit the Incubator website to remove the podling 
                                             from the list in <code>project.xml</code>. <a 
                                             href='website.html#Generating+the+top-level+website'>Here</a> explains how.
                                         </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>
-
-										Transfer podling related content from the
-	                                    <a
-	                                    href='http://wiki.apache.org/incubator/'>Incubator
-	                                    wiki</a> to the project wiki
-
-									</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>
-								<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>
-
-									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.
+                                    </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>
+
+                                        Transfer podling related content from the
+                                        <a
+                                        href='http://wiki.apache.org/incubator/'>Incubator
+                                        wiki</a> to the project wiki
+
+                                    </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>
+                                <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>
+                                </li>
+                                <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.
+
+                                </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.
+                                    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>
+                                </li>
                                 <li>
                                 
                                     Update website: replace links to old archives with 
@@ -1186,32 +1185,32 @@ Resolution draft:
                                    The chair should have karma to perform these
                                    tasks. 
                                 </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>

[... 50 lines stripped ...]


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


Mime
View raw message