You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by gi...@apache.org on 2017/07/13 01:36:27 UTC
[40/51] [partial] incubator git commit: Automatic Site Publish by
git-site-role
http://git-wip-us.apache.org/repos/asf/incubator/blob/73f8b0f7/content/guides/graduation.html
----------------------------------------------------------------------
diff --git a/content/guides/graduation.html b/content/guides/graduation.html
new file mode 100644
index 0000000..67e4497
--- /dev/null
+++ b/content/guides/graduation.html
@@ -0,0 +1,1268 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8"/>
+ <title>Guide to Successful Graduation</title>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+ <meta name="description" content="">
+ <meta name="author" content="">
+ <meta name="keywords" content="">
+ <meta name="generator" content="JBake">
+
+ <!-- Le styles -->
+ <link href="../css/incubator.css" rel="stylesheet">
+ <link href="../css/bootstrap.css" rel="stylesheet">
+ <link href="../css/asciidoctor.css" rel="stylesheet">
+ <link href="../css/base.css" rel="stylesheet">
+ <link href="../css/prettify.css" rel="stylesheet">
+
+ <!-- HTML5 shim, for IE6-8 support of HTML5 elements -->
+ <!--[if lt IE 9]>
+ <script src="../js/html5shiv.min.js"></script>
+ <![endif]-->
+
+ <!-- Fav and touch icons -->
+ <!--<link rel="apple-touch-icon-precomposed" sizes="144x144" href="../assets/ico/apple-touch-icon-144-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" sizes="114x114" href="../assets/ico/apple-touch-icon-114-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" sizes="72x72" href="../assets/ico/apple-touch-icon-72-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" href="../assets/ico/apple-touch-icon-57-precomposed.png">-->
+ <link rel="shortcut icon" href="https://www.apache.org/favicon.ico">
+ </head>
+ <body onload="prettyPrint()">
+ <div id="wrap">
+
+
+ <!-- Fixed navbar -->
+ <div class="navbar navbar-default navbar-fixed-top" role="navigation">
+ <div class="container">
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <a class="navbar-brand" href="https://incubator.apache.org"><i class="icon-home"></i>Apache Incubator</a>
+ </div>
+ <div class="navbar-collapse collapse">
+ <ul class="nav navbar-nav">
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Policies <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/policy/incubation.html">Incubation Policy</a></li>
+
+ <li><a href="https://incubator.apache.org/policy/process.html">Incubation Process</a></li>
+
+ <li><a href="https://incubator.apache.org/policy/roles_and_responsibilities.html">Roles and Responsibilities</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Proposals <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/proposal.html">A Guide To Proposal Creation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/entry.html">Enter The Incubator</a></li>
+
+ <li><a href="https://incubator.apache.org/podling-story.html">The Story of a Podling</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Podling Guides <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/branding.html">Incubator Branding Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/committer.html">Committers</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/community.html">Guide to Successful Community Building</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/graduation.html">Guide to Successful Graduation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/ip_clearance.html">IP Clearance</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/names.html">Podling Name Search Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/podling_sourcecontrol.html">Podling Source Control</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/ppmc.html">Podling Project Management Committee</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/press-kit.html">Podling Press Kit</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/releasemanagement.html">Release Management</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/retirement.html">Guide to Retirement</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/sites.html">Podling Websites</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/transitioning_asf.html">Initial Code Import</a></li>
+
+ <li><a href="/clutch">Clutch Report</a></li>
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">PMC Guides <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/chair.html">Incubator Chair Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/lists.html">Incubator Mailing Lists Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/mentor.html">Mentors' Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/participation.html">Guide to Participation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/pmc.html">The Incubator PMC</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/website.html">Updating the top-level Incubator website</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li>
+ <li><a href="http://www.apache.org/dev/">Developer Documentation</a></li>
+ <li><a href="http://www.apache.org/legal/">Legal</a></li>
+ <li><a href="http://www.apache.org/foundation/">Foundation</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ </ul>
+ </li>
+ <li><a href="https://incubator.apache.org/faq.html">FAQs</a></li>
+ </ul>
+ </div><!--/.nav-collapse -->
+ </div>
+ </div>
+ <div class="container">
+ <div class="row">
+ <div class="col-md-4 vcenter"><a href="https://www.apache.org/"><img src="http://www.apache.org/img/asf_logo.png" alt="The Apache Software Foundation" border="0" style="margin-top: 2px" width="250"></a></div>
+ <div class="col-md-4 vcenter"><a href="/"><img src="https://incubator.apache.org/images/incubator_feather_egg_logo_sm.png" alt="The Apache Software Foundation Incubator" border="0" style="margin-top: 2px" height="100"></a></div>
+ <div class="col-md-4 vcenter"><a href="https://www.apache.org/foundation/contributing.html"><img src="https://www.apache.org/images/SupportApache-small.png" height="75" width="75"></a></div>
+ </div>
+ </div>
+ <div class="top-container container">
+
+<div class="page-header">
+ <h1>Guide :: Guide to Successful Graduation</h1>
+</div>
+
+<div class="article-body">
+
+Estimated Reading Time: <span class="eta"></span>
+
+<p><div id="toc" class="toc">
+<div id="toctitle">Table of Contents</div>
+<ul class="sectlevel1">
+<li><a href="#what_is_graduation">What is Graduation?</a></li>
+<li><a href="#whether_to_graduate_to_subproject_or_to_top_level_project">Whether to Graduate to Subproject or to Top Level Project</a></li>
+<li><a href="#before_you_graduate">Before You Graduate</a>
+<ul class="sectlevel2">
+<li><a href="#graduation_check_list">Graduation Check List</a></li>
+<li><a href="#checking_the_status_file">Checking the Status File</a></li>
+</ul>
+</li>
+<li><a href="#ensure_suitable_project_name_and_product_names">Ensure suitable project name and product names</a></li>
+<li><a href="#creating_an_apache_release">Creating an Apache Release</a></li>
+<li><a href="#creating_an_open_and_diverse_community">Creating an Open and Diverse community</a>
+<ul class="sectlevel2">
+<li><a href="#other_issues">Other Issues</a></li>
+</ul>
+</li>
+<li><a href="#the_graduation_process">The Graduation Process</a>
+<ul class="sectlevel2">
+<li><a href="#graduating_to_a_top_level_project">Graduating to a Top Level Project</a></li>
+<li><a href="#community_graduation_vote">Community Graduation Vote</a></li>
+<li><a href="#preparing_a_charter">Preparing a Charter</a></li>
+<li><a href="#the_recommendation_vote">The Recommendation Vote</a></li>
+<li><a href="#submission_of_the_resolution_to_the_board">Submission of the Resolution to the Board</a></li>
+<li><a href="#press_releases_for_new_tlps">Press Releases for new TLPs</a></li>
+</ul>
+</li>
+<li><a href="#graduating_to_a_subproject">Graduating to a Subproject</a>
+<ul class="sectlevel2">
+<li><a href="#community_graduation_vote_2">Community Graduation Vote</a></li>
+<li><a href="#subproject_acceptance_vote">Subproject Acceptance Vote</a></li>
+<li><a href="#graduation_approval_vote">Graduation Approval Vote</a></li>
+</ul>
+</li>
+<li><a href="#life_after_graduation">Life After Graduation</a>
+<ul class="sectlevel2">
+<li><a href="#handover">Handover</a></li>
+<li><a href="#first_steps_outside_the_incubator">First Steps Outside the Incubator</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<div id="preamble">
+<div class="sectionbody">
+<div class="paragraph">
+<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>
+<div class="paragraph">
+<p><strong>This is just a guide. Policy is stated <a href="https://incubator.apache.org/incubation/Incubation_Policy.html">here</a>.</strong></p>
+</div>
+<div class="paragraph">
+<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+at+incubator.apache.org">general</a> list at
+incubator.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="what_is_graduation">What is Graduation?</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<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 <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong>. 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>
+</div>
+<div class="paragraph">
+<p>The road to graduation is pretty clear: depending on whether 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>
+</div>
+<div class="paragraph">
+<p>This document is offered for guidance and education only.
+Actual policy is documented in the <a href="../incubation/Incubation_Policy.html">Incubation PolicyGuide</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>.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="whether_to_graduate_to_subproject_or_to_top_level_project">Whether to Graduate to Subproject or to Top Level Project</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<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">IncubatorPMC (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>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<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 <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong>
+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>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="before_you_graduate">Before You Graduate</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>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.</p>
+</div>
+<div class="sect2">
+<h3 id="graduation_check_list">Graduation Check List</h3>
+<div class="paragraph">
+<p>The following is a short checklist giving an overview, not
+a substitute for reading the content below.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Preparations</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Complete (and sign off) tasks documented in the <a href="#notes-status">status file</a></p>
+</li>
+<li>
+<p>Ensure <a href="#notes-names">suitable names</a> for project name and product names</p>
+</li>
+<li>
+<p>Demonstrate ability to <a href="#releases">create Apache releases</a></p>
+</li>
+<li>
+<p>Demonstrate <a href="#community">community readiness</a></p>
+</li>
+<li>
+<p>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></p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Decide upon <a href="#subproject-or-top-level">destination</a></p>
+</li>
+<li>
+<p>Prepare a <a href="#tlp-resolution">resolution</a> <strong>(top level candidates only)</strong>.</p>
+</li>
+<li>
+<p><a href="#subproject-acceptance">Subproject acceptance <strong>VOTE</strong></a> by destination Project <strong>(subproject candidates only)</strong></p>
+</li>
+<li>
+<p><a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator PMC (IPMC)</a>:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>For top level candidates, this is a <a href="#ipmc-top-level-recommendation">recommendation <strong>VOTE</strong></a></p>
+</li>
+<li>
+<p>For subproject candidates, this is a <a href="#subproject-graduation">graduation approval <strong>VOTE</strong></a></p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Final <a href="#notes-on-hand-over">hand-over</a></p>
+</li>
+<li>
+<p>Consider post graduation <a href="#project-first-steps">tasks</a></p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="checking_the_status_file">Checking the Status File</h3>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<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 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>
+</div>
+<div class="paragraph">
+<p>The status file of the JUDDI project is <a href="http://incubator.apache.org/projects/juddi.html">one example</a>.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="ensure_suitable_project_name_and_product_names">Ensure suitable project name and product names</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Please read <a href="http://www.apache.org/foundation/marks/naming.html">detailed documentation here</a>.
+The "Process for ensuring suitable project and product names" is mandatory for every podling which wants to
+graduate.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="creating_an_apache_release">Creating an Apache Release</h2>
+<div class="sectionbody">
+<div class="exampleblock">
+<div class="content">
+<div class="paragraph">
+<p>Release Early, Release Often</p>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<p>Podlings do not need to actually <strong>publish</strong> 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_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">incubator project management committee</a> is usually the
+simplest way to do this.</p>
+</div>
+<div class="paragraph">
+<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>
+</div>
+</div>
+<div class="sect1">
+<h2 id="creating_an_open_and_diverse_community">Creating an Open and Diverse community</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<p>Apache projects are self-sustaining and self-governing
+communities. Long term success and health requires that
+these communities understand how to:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>recruit users, developers, committers and PMCers</p>
+</li>
+<li>
+<p>take responsible collective action</p>
+</li>
+<li>
+<p>disagree in public on technical matters without destroying personal relationships</p>
+</li>
+<li>
+<p>create an open, positive and inclusive atmosphere on the mailing lists</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<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 class="sect2">
+<h3 id="other_issues">Other Issues</h3>
+<div class="paragraph">
+<p>The Incubator relies more on people than rules: rather
+than try to create rules to cover every circumstance,
+rules are developed and codified as required. People
+are trusted to evolve process and policy. This guide
+can only document the most common issues and it is
+possible that there are other concerns that may require
+resolution that are not covered.</p>
+</div>
+<div class="paragraph">
+<p>Podlings who are unsure if they are ready to graduate may want to consider completing the link:http://community.apache.org/apache-way/apache-project-maturity-model.html" target="_new[Apache Project Maturity Model]. You may find this to be a useful guide when looking at various factors in your podling’s community.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="the_graduation_process">The Graduation Process</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="graduating_to_a_top_level_project">Graduating to a Top Level Project</h3>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<p>Graduation to a top level project requires:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>a charter for your project</p>
+</li>
+<li>
+<p>a positive community graduation <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong></p>
+</li>
+<li>
+<p>a positive IPMC recommendation <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong></p>
+</li>
+<li>
+<p>the acceptance of the <a href="#tlp-resolution">resolution</a> by the Board</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>This process can take a while, since it typically sparks
+some discussion inside the community and possibly in the
+IPMC.</p>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<p><span class="image"><img src="/images/graduation-timeline.png" alt="Graduation timeline"></span></p>
+</div>
+<div class="paragraph">
+<p>For each event we scheduled one or two weeks. Even though
+a <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong>
+is usually limited to 72 hours, you should prepare
+for discussion and possibly having to cast a revote with a
+revised proposal.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="community_graduation_vote">Community Graduation Vote</h3>
+<div class="paragraph">
+<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 <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong> (by the
+community) on the graduation proposal.</p>
+</div>
+<div class="paragraph">
+<p>This <strong>VOTE</strong> 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 notify the
+<a href="lists.html#general+at+incubator.apache.org">incubator general list</a> that the community vote is starting. Please do not Cc the
+vote to the general list as that creates confusion, instead you can either:
+- FWD the [VOTE] e-mail to the general list, or
+- Send a different copy to the general list indicating that a graduation community [VOTE] is in progress</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="preparing_a_charter">Preparing a Charter</h3>
+<div class="paragraph">
+<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:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Harmony (see section <strong>E. Establish the Apache Harmony project</strong> in the <a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_10_25.txt">October 2006 Board minutes</a>)</p>
+</li>
+<li>
+<p>OFBiz (see section <strong>B. Establish Apache Open for Business Project</strong> in the <a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_12_20.txt">December 2006 Board minutes</a>)</p>
+</li>
+<li>
+<p>Cayenne (see section <strong>C. Establish Apache Cayenne Project</strong> in the <a href="http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_12_20.txt">December 2006 Board minutes</a>)</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p><a href="/guides/graduation-template.txt">Click here for a template of this proposal to use.</a></p>
+</div>
+<div class="paragraph">
+<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.</p>
+</div>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<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
+<a href="ppmc.html">PPMC</a> to choose one
+person to act as the chair after graduation.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="the_recommendation_vote">The Recommendation Vote</h3>
+<div class="paragraph">
+<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 <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong>
+is started to allow feedback. Once a consensus has been reached, a <strong>VOTE</strong>
+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>
+</div>
+</div>
+<div class="sect2">
+<h3 id="submission_of_the_resolution_to_the_board">Submission of the Resolution to the Board</h3>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<p>Business for the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a> should be submitted by a post
+to the <strong>board</strong> mailing list. Posting from
+an Apache address is recommended. Mixing public and
+private lists on a post is not recommended.</p>
+</div>
+<div class="paragraph">
+<p>The <strong>board</strong> 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>
+</div>
+<div class="paragraph">
+<p>The submission should include:
+- A clear subject (for example <strong>Establish Foo TLP</strong>)
+- A brief introduction
+- The name of proposed VP
+- Links to the <strong>VOTE</strong> threads
+- Summary of the <strong>VOTE</strong> results
+- The <a href="#tlp-resolution">resolution</a> text</p>
+</div>
+<div class="paragraph">
+<p>For example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="paragraph">
+<p>From: <you <em>at</em> apache dot org>
+To: <board <em>at</em> apache dot org>
+CC: <<project>-private <em>at</em> incubator dot apache dot org>
+Subject: proposed resolution: establish <project> TLP</p>
+</div>
+<div class="paragraph">
+<p>Dear Apache Board,</p>
+</div>
+<div class="paragraph">
+<p><Project> is ready for graduation out of the incubator. So, please
+consider the draft resolution below at your next meeting.</p>
+</div>
+<div class="paragraph">
+<p><thank you, best regards, personal note if you wish, etc etc></p>
+</div>
+<div class="paragraph">
+<p><your name></p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="paragraph">
+<p>References:</p>
+</div>
+<div class="paragraph">
+<p>Home: <project home page>
+Vote by project: <link to vote thread on project list>
+Vote by incubator: <link to vote thread on general list></p>
+</div>
+<div class="paragraph">
+<p>Resolution draft:</p>
+</div>
+<div class="paragraph">
+<p><a href="#resolution goes here">72 characters wide,
+indent with 4 spaces</a></p>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><your e-mail sig, if you have one></p>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Please try to keep the <strong>board</strong> 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>
+</div>
+</div>
+<div class="sect2">
+<h3 id="press_releases_for_new_tlps">Press Releases for new TLPs</h3>
+<div class="paragraph">
+<p>Once there is clear consensus that the recommendation will happen,
+a member of the PPMC should contact ASF Marketing & Publicity at
+<strong>press(at)apache(dot)org</strong> if your project is interested in a
+formal press release announcing your graduation. This should be done
+roughly at the same time that the board resolution is sent.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="graduating_to_a_subproject">Graduating to a Subproject</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<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.</p>
+</div>
+<div class="sect2">
+<h3 id="community_graduation_vote_2">Community Graduation Vote</h3>
+<div class="paragraph">
+<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
+<strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong>
+(by the community) on the graduation proposal.</p>
+</div>
+<div class="paragraph">
+<p>This <strong>VOTE</strong> 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 <strong>VOTE</strong>
+is proposed.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="subproject_acceptance_vote">Subproject Acceptance Vote</h3>
+<div class="paragraph">
+<p>A formal <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong>
+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>
+</div>
+<div class="sect2">
+<h3 id="graduation_approval_vote">Graduation Approval Vote</h3>
+<div class="paragraph">
+<p>To graduate as a subproject, the <a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a> should start a <strong><a href="http://www.apache.org/foundation/voting.html">VOTE</a></strong>
+thread on the <a href="lists.html#general+at+incubator.apache.org">general list</a> proposing that the
+<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a> signs off the graduation of the podling as a
+subproject. This *VOTE*s should only be started once the
+project has *VOTE*d to accept the subproject.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="life_after_graduation">Life After Graduation</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="handover">Handover</h3>
+<div class="paragraph">
+<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.</p>
+</div>
+<div class="sect3">
+<h4 id="graduating_as_subproject">Graduating as Subproject</h4>
+<div class="paragraph">
+<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.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="graduating_as_new_top_level_project">Graduating as New Top Level Project</h4>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<p>The <a href="#tlp-resolution">resolution</a> will appoint a Chair for the new
+project. The Chair will also be appointed an
+<a href="http://www.apache.org/foundation/">Officer</a>
+of the Apache Software Foundation. This allows them
+access to official resources of the foundation as well
+as granting power to act on behalf of Apache.</p>
+</div>
+<div class="paragraph">
+<p>Once appointed, the new Chair needs to:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Subscribe to the <strong>board</strong> mailing list</p>
+</li>
+<li>
+<p>Subscribe to the <strong>infrastructure</strong> mailing list</p>
+</li>
+<li>
+<p>Ensure that they have been added to
+<a href="https://people.apache.org/phonebook.html?service=pmc-chairs">the PMC chairs group (pmc-chairs) in LDAP</a>.
+The ASF Secretary should do this without any action on the part
+of the new chair. As with above, if it has not happened within
+72 hours of the resolution passing, contact the secretary to remind them.</p>
+</li>
+<li>
+<p>Check out the <a href="https://svn.apache.org/repos/private/foundation/officers"><strong>foundation/officers</strong></a> folder from the private repository.
+Users with member or pmc-chairs karma can do this.</p>
+</li>
+<li>
+<p>Add yourself to the <mark>foundation/officers/affiliations.txt</mark> and the #foundation/officers/irs-disclosures.txt* files with the appropriate information.</p>
+</li>
+<li>
+<p>Add your details to the foundation web site Officer list at <a href="http://www.apache.org/foundation/index.html">http://www.apache.org/foundation/index.html</a> (in SVN at <a href="https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/foundation/">https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/foundation/</a>)</p>
+</li>
+<li>
+<p>Review appropriate documentation:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="http://www.apache.org/dev/pmc.html#chair">PMC Chair Duties</a></p>
+</li>
+<li>
+<p>PMC <a href="http://www.apache.org/dev/#pmc">documentation</a></p>
+</li>
+<li>
+<p>Jakarta <a href="http://wiki.apache.org/jakarta/RoleOfChair">Chair guide</a></p>
+</li>
+<li>
+<p>Incubator <a href="http://incubator.apache.org/guides/chair.html">Chair guide</a></p>
+</li>
+<li>
+<p>Reporting <a href="http://www.apache.org/foundation/board/calendar.html">calendar</a></p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>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.</p>
+</li>
+<li>
+<p>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
+(see <a href="#transfer">check list</a>)
+should be consolidated into a single issue (see <a href="https://issues.apache.org/jira/browse/INFRA-4069">this</a>
+for example). This should be created in the category
+<a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10410&sorter/order=DESC&sorter/field=priority&resolution=-1&component=10858">TLP Admin</a>.</p>
+</li>
+<li>
+<p>Ensure the PMC is added to the committee-info.txt file at <a href="https://svn.apache.org/repos/private/committers/board/committee-info.txt" class="bare">https://svn.apache.org/repos/private/committers/board/committee-info.txt</a>
+There are 3 sections which need to be updated; see instructions in the file.
+You may need to get a member to help with this.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<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="#tlp-resolution">resolution</a>. However, the Chair of the new project
+needs to ensure that private list is created and the
+membership subscribed.</p>
+</div>
+<div class="paragraph">
+<p>Members of the new PMC need to:
+- Subscribe to the private mailing list for the project
+- Review appropriate documentation:
+<strong> Apache <a href="http://www.apache.org/dev/pmc.html">PMC Guide</a>
+</strong> Related <a href="http://www.apache.org/dev/#pmc">documentation</a></p>
+</div>
+<div class="paragraph">
+<p>Once all this is in place, resources can start to be
+handed over to the new project.</p>
+</div>
+<div class="paragraph">
+<p>Please continue to hang around the Incubator and help
+new podlings have an easier time than you did!</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="first_steps_outside_the_incubator">First Steps Outside the Incubator</h3>
+<div class="paragraph">
+<p>Graduation is the first step in what is hopefully a long road.
+There are some issues which incubation may not cover.</p>
+</div>
+<div class="sect3">
+<h4 id="transferring_resources">Transferring Resources</h4>
+<div class="paragraph">
+<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>
+</div>
+<div class="paragraph">
+<p>Although the below checklist is still generally useful, <strong>the infrastructure process has been streamlined</strong>, see
+<a href="http://www.apache.org/dev/infra-contact#requesting-graduation" class="bare">http://www.apache.org/dev/infra-contact#requesting-graduation</a> . You might also want to check JIRA checklist tickets for projects that graduated in the last month or two.</p>
+</div>
+<div class="paragraph">
+<p>Checklist:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Update the Incubator status records</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Like the rest of incubation, graduation is a process. Updating your
+status records as you progress will enable others to assist.</p>
+</li>
+<li>
+<p>Update the podling
+<a href="#notes-status">status page</a>.
+All sections should now be filled in
+including <strong>EXIT</strong>. Take some
+time to read carefully since this page
+forms the final public record for
+graduation.</p>
+</li>
+<li>
+<p>Update the Incubator
+<a href="http://incubator.apache.org/projects/index.html">status page</a> to denote the project as "graduating" when you commence,
+then as "graduated" when you are finished.
+The notes <a href="#unincubate">below</a> will assist.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Source</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Post an announcement to the development list
+telling everyone that the repository is about
+to be moved</p>
+</li>
+<li>
+<p>Post an announcement containing instructions
+for developers describing how to <mark>svn switch</mark> their workspaces</p>
+</li>
+<li>
+<p>Update site, wikis, <strong>pom.xml</strong> and
+other resources to point to the new repository
+location.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Websites</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Transfer the podling website</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Load the website into its new home. See <a href="http://www.apache.org/dev/#web">infra notes</a>.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Update the <strong>incubator/site-publish/.htaccess</strong> entry to
+redirect traffic from the old URLs to
+the new. (svn location is at <strong><a href="http://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess" class="bare">http://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess</a></strong>) -
+NOTE: new Top Level Projects will most likely get an automatic redirection of their website from the Incubator hostname
+once the TLP’s distribution repository is moved by INFRA.</p>
+</li>
+<li>
+<p>Post an announcement to user and
+development lists</p>
+</li>
+<li>
+<p>When using Maven: update <strong>pom.xml</strong> for the location
+of the website, as well as the place
+where the site plugin will deploy the
+web site (when applicable).</p>
+<div class="ulist">
+<ul>
+<li>
+<p><strong>(Top Level Projects Only)</strong> Add Project To <a href="http://www.apache.org">www.apache.org</a></p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Check out <a href="https://svn.apache.org/repos/asf/infrastructure/site/trunk" class="bare">https://svn.apache.org/repos/asf/infrastructure/site/trunk</a></p>
+</li>
+<li>
+<p>Patch <mark>templates/blocks/projects.mdtext</mark></p>
+</li>
+<li>
+<p>Commit, and if you have karma then <a href="https://cms.apache.org/www/publish">publish</a> the updated www site</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Mailing lists</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>When your mail lists have been moved by infrastructure,
+post an announcement to your lists.</p>
+</li>
+<li>
+<p>When using Maven: update <strong>pom.xml</strong> 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.</p>
+</li>
+<li>
+<p>Send notice to any mailing list archivers
+that the
+address has changed, and possibly the location of
+your project (if it is listed there as being part of the
+incubator).</p>
+</li>
+<li>
+<p>Update website: replace links to old archives with
+links to new ones and add new links to historic
+archives from incubation.</p>
+</li>
+<li>
+<p>Check project-private mailing list membership.
+Mentors should be allowed to remain if they wish to
+do so. The subscriber list should otherwise match
+that on the resolution. See <a href="http://www.apache.org/dev/committers.html#mail-moderate">this</a> and
+the <a href="http://www.ezmlm.org/">EZMLM</a>
+"Moderator’s and Administrator’s Manual".</p>
+</li>
+<li>
+<p>Update mail addresses including:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>confluence commit messages (see adminstration documentation)</p>
+</li>
+<li>
+<p>issue tracking messages (see administration documentation)</p>
+</li>
+<li>
+<p>The chair should have karma to perform these tasks.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Double-check that all of your lists have sufficient active <a href="http://www.apache.org/dev/committers.html#mailing-list-moderators">moderators</a>.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Issue Tracking</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Check that the issue tracking system used by the podling reflects the project’s new status.
+*Distribution mirrors</p>
+</li>
+<li>
+<p>After you have a release at your new home (<mark>/dist/${project}/</mark> area), remove any distribution artefacts from your old <mark>/dist/incubator/${project}/</mark>
+area. Remember from the mirror guidelines that everything is automatically added to archive.apache.org anyway.</p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="final_revision_of_podling_incubation_records">Final Revision of Podling Incubation Records</h4>
+<div class="paragraph">
+<p>When a project has finished its graduation steps, 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:
+* Update the svn <strong>incubator/trunk/content/projects/${project}.xml</strong> file to show the project’s status.
+* Update the podling summary metadata file,
+i.e. <strong>incubator/trunk/content/podlings.xml</strong> svn file.
+See the content/podlings.dtd and follow examples of other recent graduates.
+At the beginning of the process, add the "graduating" element.
+When finished the graduation process, then:
+Change the podling status to "graduated";
+add the "enddate" attribute to document when the project graduated;
+add the "resolution" element (see other project examples);
+remove the "graduating" element.
+* After your project has finished reporting to the Incubator, then
+remove the "reporting" element from that <strong>podlings.xml</strong> file.
+* Ensure that other svn resources for your project have moved to your new home.
+* Review this whole graduation guide.
+* NOTE: Please edit this guide to add missing steps and clarifications.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="new_responsibilities">New Responsibilities</h4>
+<div class="sect4">
+<h5 id="oversight">Oversight</h5>
+<div class="paragraph">
+<p>During the stay in the Incubator, the
+<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator PMC (IPMC)</a>
+was responsible to the
+<a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>
+for oversight. A graduated project must now take
+responsibility for its own oversight.</p>
+</div>
+<div class="paragraph">
+<p>A project needs to ensure that its code base is
+clean from an IP perspective. New committers need to
+recruited, educated and mentored. Quality releases
+need to be cut. Community spirit needs to be maintained
+and conflicts resolved positively. Board reports need
+to be accurate and prompt.</p>
+</div>
+<div class="paragraph">
+<p>Help is still available but the
+appropriate bodies (infrastructure, community, legal
+and so on) should now be approached directly.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="security">Security</h5>
+<div class="paragraph">
+<p>Each project needs to be able to manage security issues
+discovered in their code. By their nature, these issues
+need to be dealt with in private. These issues may either
+be dealt with on a separate security list or on the
+private list. Which list is suitable for security issues
+should be noted.</p>
+</div>
+<div class="paragraph">
+<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. The new project
+should make contact with the team soon after graduation
+and not wait for the first issue to be raised.</p>
+</div>
+<div class="paragraph">
+<p>Projects should adopt a positive attitude towards
+security issues. It is easy to gain a poor reputation
+by mishandling of these issues. There are many people
+at Apache with considerable experience in this area
+so ask first.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="stay_in_touch">Stay In Touch</h5>
+<div class="paragraph">
+<p>Passing through the incubation process gives a very
+valuable perspective. Please help to improve the process
+by guiding new podlings and by developing improved policy
+and documentation on the <a href="lists.html#general+at+incubator.apache.org">general</a> list.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div></p>
+
+</div>
+
+ </div>
+ <div id="push"></div>
+ </div>
+
+ <div id="footer">
+ <div class="container">
+ <p class="muted credit">© 2017 The Apache Software Foundation | Licensed under the Apache License, Version 2.0.<br/>
+ Apache Incubator, Apache, the Apache feather logo, and the Apache Incubator project logo are trademarks of The Apache Software Foundation.</p>
+ </div>
+ </div>
+
+ <script src="../js/jquery-1.11.1.min.js"></script>
+ <script src="../js/bootstrap.min.js"></script>
+ <script src="../js/prettify.js"></script>
+ <script src="../js/readingTime.js"></script>
+ <script src="../js/incubator.js"></script>
+
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/incubator/blob/73f8b0f7/content/guides/ip_clearance.html
----------------------------------------------------------------------
diff --git a/content/guides/ip_clearance.html b/content/guides/ip_clearance.html
new file mode 100644
index 0000000..b2438f4
--- /dev/null
+++ b/content/guides/ip_clearance.html
@@ -0,0 +1,284 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8"/>
+ <title>IP Clearance</title>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+ <meta name="description" content="">
+ <meta name="author" content="">
+ <meta name="keywords" content="">
+ <meta name="generator" content="JBake">
+
+ <!-- Le styles -->
+ <link href="../css/incubator.css" rel="stylesheet">
+ <link href="../css/bootstrap.css" rel="stylesheet">
+ <link href="../css/asciidoctor.css" rel="stylesheet">
+ <link href="../css/base.css" rel="stylesheet">
+ <link href="../css/prettify.css" rel="stylesheet">
+
+ <!-- HTML5 shim, for IE6-8 support of HTML5 elements -->
+ <!--[if lt IE 9]>
+ <script src="../js/html5shiv.min.js"></script>
+ <![endif]-->
+
+ <!-- Fav and touch icons -->
+ <!--<link rel="apple-touch-icon-precomposed" sizes="144x144" href="../assets/ico/apple-touch-icon-144-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" sizes="114x114" href="../assets/ico/apple-touch-icon-114-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" sizes="72x72" href="../assets/ico/apple-touch-icon-72-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" href="../assets/ico/apple-touch-icon-57-precomposed.png">-->
+ <link rel="shortcut icon" href="https://www.apache.org/favicon.ico">
+ </head>
+ <body onload="prettyPrint()">
+ <div id="wrap">
+
+
+ <!-- Fixed navbar -->
+ <div class="navbar navbar-default navbar-fixed-top" role="navigation">
+ <div class="container">
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <a class="navbar-brand" href="https://incubator.apache.org"><i class="icon-home"></i>Apache Incubator</a>
+ </div>
+ <div class="navbar-collapse collapse">
+ <ul class="nav navbar-nav">
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Policies <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/policy/incubation.html">Incubation Policy</a></li>
+
+ <li><a href="https://incubator.apache.org/policy/process.html">Incubation Process</a></li>
+
+ <li><a href="https://incubator.apache.org/policy/roles_and_responsibilities.html">Roles and Responsibilities</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Proposals <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/proposal.html">A Guide To Proposal Creation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/entry.html">Enter The Incubator</a></li>
+
+ <li><a href="https://incubator.apache.org/podling-story.html">The Story of a Podling</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Podling Guides <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/branding.html">Incubator Branding Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/committer.html">Committers</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/community.html">Guide to Successful Community Building</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/graduation.html">Guide to Successful Graduation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/ip_clearance.html">IP Clearance</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/names.html">Podling Name Search Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/podling_sourcecontrol.html">Podling Source Control</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/ppmc.html">Podling Project Management Committee</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/press-kit.html">Podling Press Kit</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/releasemanagement.html">Release Management</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/retirement.html">Guide to Retirement</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/sites.html">Podling Websites</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/transitioning_asf.html">Initial Code Import</a></li>
+
+ <li><a href="/clutch">Clutch Report</a></li>
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">PMC Guides <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/chair.html">Incubator Chair Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/lists.html">Incubator Mailing Lists Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/mentor.html">Mentors' Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/participation.html">Guide to Participation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/pmc.html">The Incubator PMC</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/website.html">Updating the top-level Incubator website</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li>
+ <li><a href="http://www.apache.org/dev/">Developer Documentation</a></li>
+ <li><a href="http://www.apache.org/legal/">Legal</a></li>
+ <li><a href="http://www.apache.org/foundation/">Foundation</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ </ul>
+ </li>
+ <li><a href="https://incubator.apache.org/faq.html">FAQs</a></li>
+ </ul>
+ </div><!--/.nav-collapse -->
+ </div>
+ </div>
+ <div class="container">
+ <div class="row">
+ <div class="col-md-4 vcenter"><a href="https://www.apache.org/"><img src="http://www.apache.org/img/asf_logo.png" alt="The Apache Software Foundation" border="0" style="margin-top: 2px" width="250"></a></div>
+ <div class="col-md-4 vcenter"><a href="/"><img src="https://incubator.apache.org/images/incubator_feather_egg_logo_sm.png" alt="The Apache Software Foundation Incubator" border="0" style="margin-top: 2px" height="100"></a></div>
+ <div class="col-md-4 vcenter"><a href="https://www.apache.org/foundation/contributing.html"><img src="https://www.apache.org/images/SupportApache-small.png" height="75" width="75"></a></div>
+ </div>
+ </div>
+ <div class="top-container container">
+
+<div class="page-header">
+ <h1>Guide :: IP Clearance</h1>
+</div>
+
+<div class="article-body">
+
+Estimated Reading Time: <span class="eta"></span>
+
+<p><div id="toc" class="toc">
+<div id="toctitle">Table of Contents</div>
+<ul class="sectlevel1">
+<li><a href="#podling_ip_clearance">Podling IP Clearance</a>
+<ul class="sectlevel2">
+<li><a href="#background">Background</a></li>
+<li><a href="#establishing_provenance">Establishing Provenance</a></li>
+<li><a href="#ipmc_responsibility_around_ip_clearance">IPMC Responsibility around IP Clearance</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<div class="sect1">
+<h2 id="podling_ip_clearance">Podling IP Clearance</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="background">Background</h3>
+<div class="paragraph">
+<p>Existing codebases need to be imported through the standard IP clearance
+process. This means that a Software Grant Agreement
+(<a href="http://www.apache.org/licenses/#grants">SGA</a>)
+or Contributor License Agreement
+(<a href="http://www.apache.org/licenses/#clas">CLA</a>)
+need to be submitted
+for all copyright owners. This process may take a while so it is best to
+start as soon as the podling is accepted.</p>
+</div>
+<div class="paragraph">
+<p>The acceptance of the initial codebases is approved by the
+IPMC as part of the acceptance motion. So, no vote is required by the
+PPMC. Otherwise, follow the standard IP clearance process for podlings.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="establishing_provenance">Establishing Provenance</h3>
+<div class="paragraph">
+<p>Paperwork needs to be submitted to Apache that grants a legal license on the code
+to the Apache Software Foundation.
+As a rule of thumb, if all the material contributors to the code
+are joining the podling as initial contributors, then CLAs (individual or corporate)
+are all you need. The individuals must submit the 'individual' CLA (ICLA).
+If there are employers involved who might claim
+rights in the code, then corporate CLAs (CCLAs) are needed for those employers.</p>
+</div>
+<div class="paragraph">
+<p>If, on the other hand, there are material contributors who are <strong>
+not</strong> joining the podling as initial contributors, or if there
+are additional corporate entities who can claim rights in the code,
+then SGAs are required from those individuals or corporations.</p>
+</div>
+<div class="paragraph">
+<p>The foregoing is only a rule of thumb. Generally, the mentors of a new project
+will need to consult with <a href="mailto:general@incubator.apache.org">general@incubator.apache.org</a> or the Apache legal team
+about the particular circumstances.</p>
+</div>
+<div class="paragraph">
+<p>It may take some time to track down all contributors. It is not necessary to
+have paperwork on file for all contributions before the code is imported.
+It may be necessary to reverse some patches and rewrite areas of code if
+contributors cannot be found or at not happy about given Apache written
+permission to use their code.</p>
+</div>
+<div class="paragraph">
+<p>No releases are possible until the provenance of all the code to be release
+has been clearly established and the relevant paperwork filed with Apache. It is
+therefore important to keep the status updated.</p>
+</div>
+<div class="paragraph">
+<p>Receipts of ICLAs, CCLAs, and SGAs are recorded by the secretary in
+the private foundation repository. Reading is restricted to members and officers
+of the foundation. If there is no officer or member available then ask on the
+general list.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="ipmc_responsibility_around_ip_clearance">IPMC Responsibility around IP Clearance</h3>
+<div class="paragraph">
+<p>The board has charged the Incubator project with management of IP clearance for Apache.
+Instructions are <a href="http://incubator.apache.org/ip-clearance/index.html">here</a>.</p>
+</div>
+<div class="paragraph">
+<p>These equally apply to podlings. The Incubator project is responsible for all podlings
+and so is the receiving PMC. So, when a podling requests IP clearance, the
+IPMC wears <a href="http://www.apache.org/foundation/how-it-works.html#hats">two hats</a>.
+This may be a little confusing at first.</p>
+</div>
+<div class="paragraph">
+<p>The Incubator PMC must approve the clearance. This indicates that the project is
+happy to receive the code donated. When a new podling is created, this is done
+by the identification of existing codebases in the proposal. Otherwise, the
+IPMC delegates this decision to the PPMC.</p>
+</div>
+<div class="paragraph">
+<p>As usual, three binding votes are required. So, Mentors need to be involved in
+IP clearance for podlings. If too few binding VOTEs are posted on list,
+the VOTE will need to be posted to the general list for ratification.</p>
+</div>
+<div class="paragraph">
+<p>The second hat is technical IP clearance. Here, the IPMC needs to check that the
+paperwork is in order. Once the acceptance vote has been approved, an officer
+or member need to complete the process. For a podling, this will typically
+involve a Mentor.</p>
+</div>
+</div>
+</div>
+</div></p>
+
+</div>
+
+ </div>
+ <div id="push"></div>
+ </div>
+
+ <div id="footer">
+ <div class="container">
+ <p class="muted credit">© 2017 The Apache Software Foundation | Licensed under the Apache License, Version 2.0.<br/>
+ Apache Incubator, Apache, the Apache feather logo, and the Apache Incubator project logo are trademarks of The Apache Software Foundation.</p>
+ </div>
+ </div>
+
+ <script src="../js/jquery-1.11.1.min.js"></script>
+ <script src="../js/bootstrap.min.js"></script>
+ <script src="../js/prettify.js"></script>
+ <script src="../js/readingTime.js"></script>
+ <script src="../js/incubator.js"></script>
+
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/incubator/blob/73f8b0f7/content/guides/lists.html
----------------------------------------------------------------------
diff --git a/content/guides/lists.html b/content/guides/lists.html
new file mode 100644
index 0000000..1b9393d
--- /dev/null
+++ b/content/guides/lists.html
@@ -0,0 +1,266 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8"/>
+ <title>Incubator Mailing Lists Guide</title>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+ <meta name="description" content="">
+ <meta name="author" content="">
+ <meta name="keywords" content="">
+ <meta name="generator" content="JBake">
+
+ <!-- Le styles -->
+ <link href="../css/incubator.css" rel="stylesheet">
+ <link href="../css/bootstrap.css" rel="stylesheet">
+ <link href="../css/asciidoctor.css" rel="stylesheet">
+ <link href="../css/base.css" rel="stylesheet">
+ <link href="../css/prettify.css" rel="stylesheet">
+
+ <!-- HTML5 shim, for IE6-8 support of HTML5 elements -->
+ <!--[if lt IE 9]>
+ <script src="../js/html5shiv.min.js"></script>
+ <![endif]-->
+
+ <!-- Fav and touch icons -->
+ <!--<link rel="apple-touch-icon-precomposed" sizes="144x144" href="../assets/ico/apple-touch-icon-144-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" sizes="114x114" href="../assets/ico/apple-touch-icon-114-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" sizes="72x72" href="../assets/ico/apple-touch-icon-72-precomposed.png">
+ <link rel="apple-touch-icon-precomposed" href="../assets/ico/apple-touch-icon-57-precomposed.png">-->
+ <link rel="shortcut icon" href="https://www.apache.org/favicon.ico">
+ </head>
+ <body onload="prettyPrint()">
+ <div id="wrap">
+
+
+ <!-- Fixed navbar -->
+ <div class="navbar navbar-default navbar-fixed-top" role="navigation">
+ <div class="container">
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <a class="navbar-brand" href="https://incubator.apache.org"><i class="icon-home"></i>Apache Incubator</a>
+ </div>
+ <div class="navbar-collapse collapse">
+ <ul class="nav navbar-nav">
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Policies <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/policy/incubation.html">Incubation Policy</a></li>
+
+ <li><a href="https://incubator.apache.org/policy/process.html">Incubation Process</a></li>
+
+ <li><a href="https://incubator.apache.org/policy/roles_and_responsibilities.html">Roles and Responsibilities</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Proposals <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/proposal.html">A Guide To Proposal Creation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/entry.html">Enter The Incubator</a></li>
+
+ <li><a href="https://incubator.apache.org/podling-story.html">The Story of a Podling</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Podling Guides <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/branding.html">Incubator Branding Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/committer.html">Committers</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/community.html">Guide to Successful Community Building</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/graduation.html">Guide to Successful Graduation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/ip_clearance.html">IP Clearance</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/names.html">Podling Name Search Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/podling_sourcecontrol.html">Podling Source Control</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/ppmc.html">Podling Project Management Committee</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/press-kit.html">Podling Press Kit</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/releasemanagement.html">Release Management</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/retirement.html">Guide to Retirement</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/sites.html">Podling Websites</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/transitioning_asf.html">Initial Code Import</a></li>
+
+ <li><a href="/clutch">Clutch Report</a></li>
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">PMC Guides <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+
+ <li><a href="https://incubator.apache.org/guides/chair.html">Incubator Chair Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/lists.html">Incubator Mailing Lists Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/mentor.html">Mentors' Guide</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/participation.html">Guide to Participation</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/pmc.html">The Incubator PMC</a></li>
+
+ <li><a href="https://incubator.apache.org/guides/website.html">Updating the top-level Incubator website</a></li>
+
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li><a href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li>
+ <li><a href="http://www.apache.org/dev/">Developer Documentation</a></li>
+ <li><a href="http://www.apache.org/legal/">Legal</a></li>
+ <li><a href="http://www.apache.org/foundation/">Foundation</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ </ul>
+ </li>
+ <li><a href="https://incubator.apache.org/faq.html">FAQs</a></li>
+ </ul>
+ </div><!--/.nav-collapse -->
+ </div>
+ </div>
+ <div class="container">
+ <div class="row">
+ <div class="col-md-4 vcenter"><a href="https://www.apache.org/"><img src="http://www.apache.org/img/asf_logo.png" alt="The Apache Software Foundation" border="0" style="margin-top: 2px" width="250"></a></div>
+ <div class="col-md-4 vcenter"><a href="/"><img src="https://incubator.apache.org/images/incubator_feather_egg_logo_sm.png" alt="The Apache Software Foundation Incubator" border="0" style="margin-top: 2px" height="100"></a></div>
+ <div class="col-md-4 vcenter"><a href="https://www.apache.org/foundation/contributing.html"><img src="https://www.apache.org/images/SupportApache-small.png" height="75" width="75"></a></div>
+ </div>
+ </div>
+ <div class="top-container container">
+
+<div class="page-header">
+ <h1>Guide :: Incubator Mailing Lists Guide</h1>
+</div>
+
+<div class="article-body">
+
+Estimated Reading Time: <span class="eta"></span>
+
+<p><div id="toc" class="toc">
+<div id="toctitle">Table of Contents</div>
+<ul class="sectlevel1">
+<li><a href="#incubator_mailing_lists_guide">Incubator Mailing Lists Guide</a>
+<ul class="sectlevel2">
+<li><a href="#archive_policy">Archive Policy</a></li>
+<li><a href="#incubator_wide_mailing_lists">Incubator-wide Mailing Lists</a></li>
+<li><a href="#podlings_at_incubator_apache_org">podlings at incubator.apache.org</a></li>
+<li><a href="#podling_mailing_lists">Podling Mailing Lists</a></li>
+<li><a href="#foundation_wide_mailing_lists">Foundation-wide Mailing Lists</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<div class="sect1">
+<h2 id="incubator_mailing_lists_guide">Incubator Mailing Lists Guide</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="archive_policy">Archive Policy</h3>
+<div class="paragraph">
+<p>Please read the <a href="http://www.apache.org/foundation/public-archives.html">Apache Public Forum Archive Policy</a> before sending email to any list.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="incubator_wide_mailing_lists">Incubator-wide Mailing Lists</h3>
+<div class="sect3">
+<h4 id="general_at_incubator_apache_org">general at incubator.apache.org</h4>
+<div class="paragraph">
+<p>This is where general and public discussion of the Incubator takes place.
+- <a href="mailto:general-subscribe@incubator.apache.org">Subscribe</a>
+- <a href="mailto:general-unsubscribe@incubator.apache.org">Unsubscribe</a>
+- <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/">Archives</a></p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="cvs_at_incubator_apache_org">cvs at incubator.apache.org</h4>
+<div class="paragraph">
+<p>This is the Incubator’s "commits" list, named "cvs" for historical reasons. Changes made to the <a href="https://svn.apache.org/viewvc/incubator/public/trunk">Incubator codebase and website</a> and
+the <a href="http://wiki.apache.org/incubator">Incubator wiki</a> trigger automatic notifications to
+this list. Replies go to the <a href="general+at+incubator.apache.org">general list</a>.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="mailto:cvs-subscribe@incubator.apache.org">Subscribe</a></p>
+</li>
+<li>
+<p><a href="mailto:cvs-unsubscribe@incubator.apache.org">Unsubscribe</a></p>
+</li>
+<li>
+<p><a href="http://mail-archives.apache.org/mod_mbox/incubator-cvs/">Archives</a></p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="podlings_at_incubator_apache_org">podlings at incubator.apache.org</h3>
+<div class="paragraph">
+<p>This mail alias is for all of the dev lists for all active podlings. It is used
+for incubator wide announcements so that podlings don’t need to be subscribed to general for all information.
+Emails to podlings at incubator should be done as a BCC, with general in the to, in order to avoid spamming
+all of the podlings.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="podling_mailing_lists">Podling Mailing Lists</h3>
+<div class="paragraph">
+<p>Each podling under incubation has its own mailing lists, which should be easily discovered via the
+podling website or via the <a href="/projects/index.html">podling status pages</a>.
+These are the right place to get involved with a particular project or to ask project specific
+questions. They form the public record of the development of the project. All lists are <a href="http://mail-archives.apache.org">archived</a>.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="foundation_wide_mailing_lists">Foundation-wide Mailing Lists</h3>
+<div class="paragraph">
+<p>Many <a href="http://www.apache.org/foundation/mailinglists.html">ASF-wide lists</a> will
+also be of interest to Incubator participants. The
+<a href="http://www.apache.org/foundation/mailinglists.html#foundation-legal">legal discussion</a>,
+<a href="http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure">infrastructure</a>,
+and <a href="http://www.apache.org/foundation/mailinglists.html#foundation-community">community</a>
+lists are especially germane for PPMC members and release managers trying to develop their knowledge
+and stay current.</p>
+</div>
+</div>
+</div>
+</div></p>
+
+</div>
+
+ </div>
+ <div id="push"></div>
+ </div>
+
+ <div id="footer">
+ <div class="container">
+ <p class="muted credit">© 2017 The Apache Software Foundation | Licensed under the Apache License, Version 2.0.<br/>
+ Apache Incubator, Apache, the Apache feather logo, and the Apache Incubator project logo are trademarks of The Apache Software Foundation.</p>
+ </div>
+ </div>
+
+ <script src="../js/jquery-1.11.1.min.js"></script>
+ <script src="../js/bootstrap.min.js"></script>
+ <script src="../js/prettify.js"></script>
+ <script src="../js/readingTime.js"></script>
+ <script src="../js/incubator.js"></script>
+
+ </body>
+</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org