You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by po...@apache.org on 2017/07/06 00:20:54 UTC
[23/51] incubator git commit: Continuing progress on converting to
asciidoc.
Continuing progress on converting to asciidoc.
Project: http://git-wip-us.apache.org/repos/asf/incubator/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator/commit/f59ab76b
Tree: http://git-wip-us.apache.org/repos/asf/incubator/tree/f59ab76b
Diff: http://git-wip-us.apache.org/repos/asf/incubator/diff/f59ab76b
Branch: refs/heads/master
Commit: f59ab76b0efd84f6653df460f1a341d10acc3bb0
Parents: bfa7c88
Author: John D. Ament <jo...@apache.org>
Authored: Mon Apr 17 20:08:57 2017 -0400
Committer: John D. Ament <jo...@apache.org>
Committed: Mon Apr 17 20:10:56 2017 -0400
----------------------------------------------------------------------
assets/images/EPS/apache_incubator_CMYK.eps | Bin 0 -> 2271382 bytes
.../images/EPS/apache_incubator_black_CMYK.eps | Bin 0 -> 2266798 bytes
assets/images/EPS/apache_incubator_red_CMYK.eps | Bin 0 -> 2267054 bytes
.../images/EPS/apache_incubator_white_CMYK.eps | Bin 0 -> 2273042 bytes
assets/images/graduation-timeline.png | Bin 0 -> 54670 bytes
.../images/incbuator_feather_egg_logo_crop.png | Bin 0 -> 51002 bytes
.../incubator_feather_egg_logo_bw_crop.png | Bin 0 -> 56218 bytes
.../incubator_feather_egg_logo_red_crop.png | Bin 0 -> 68766 bytes
.../incubator_feather_egg_logo_wb_crop.png | Bin 0 -> 59188 bytes
assets/images/incubator_power_ring.jpg | Bin 0 -> 419206 bytes
assets/images/incubator_ring_airflow.jpg | Bin 0 -> 219169 bytes
assets/images/incubator_ring_logo.png | Bin 0 -> 507621 bytes
assets/images/template_airflow.jpg | Bin 0 -> 1867175 bytes
assets/images/template_hawq.jpg | Bin 0 -> 1864271 bytes
assets/images/template_spot.jpg | Bin 0 -> 1769584 bytes
pages/guides/branding.ad | 63 +-
pages/guides/chair.ad | 58 +-
pages/guides/committer.ad | 104 +-
pages/guides/community.ad | 191 ++++
pages/guides/entry.ad | 82 ++
pages/guides/graduation-template.txt | 52 +
pages/guides/graduation.ad | 715 ++++++++++++
pages/guides/ip_clearance.ad | 43 +
pages/guides/lists.ad | 60 +
pages/guides/mentor.xml | 290 +++++
pages/guides/names.xml | 366 ++++++
pages/guides/participation.ad | 119 ++
pages/guides/pmc.ad | 34 +
pages/guides/podling_bootstrap.ad | 334 ++++++
pages/guides/podling_sourcecontrol.ad | 108 ++
pages/guides/ppmc-offer.txt | 58 +
pages/guides/ppmc.ad | 246 +++++
pages/guides/press-kit.ad | 108 ++
pages/guides/proposal.xml | 1045 ++++++++++++++++++
pages/guides/releasemanagement.ad | 49 +
pages/guides/retirement.ad | 104 ++
pages/guides/sites.ad | 111 ++
pages/guides/website.ad | 43 +
pages/policy/roles_and_responsibilities.ad | 254 +++++
replacements | 2 +
40 files changed, 4547 insertions(+), 92 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/EPS/apache_incubator_CMYK.eps
----------------------------------------------------------------------
diff --git a/assets/images/EPS/apache_incubator_CMYK.eps b/assets/images/EPS/apache_incubator_CMYK.eps
new file mode 100644
index 0000000..c228028
Binary files /dev/null and b/assets/images/EPS/apache_incubator_CMYK.eps differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/EPS/apache_incubator_black_CMYK.eps
----------------------------------------------------------------------
diff --git a/assets/images/EPS/apache_incubator_black_CMYK.eps b/assets/images/EPS/apache_incubator_black_CMYK.eps
new file mode 100644
index 0000000..a00a0c0
Binary files /dev/null and b/assets/images/EPS/apache_incubator_black_CMYK.eps differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/EPS/apache_incubator_red_CMYK.eps
----------------------------------------------------------------------
diff --git a/assets/images/EPS/apache_incubator_red_CMYK.eps b/assets/images/EPS/apache_incubator_red_CMYK.eps
new file mode 100644
index 0000000..7dfedd6
Binary files /dev/null and b/assets/images/EPS/apache_incubator_red_CMYK.eps differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/EPS/apache_incubator_white_CMYK.eps
----------------------------------------------------------------------
diff --git a/assets/images/EPS/apache_incubator_white_CMYK.eps b/assets/images/EPS/apache_incubator_white_CMYK.eps
new file mode 100644
index 0000000..7e4b1c8
Binary files /dev/null and b/assets/images/EPS/apache_incubator_white_CMYK.eps differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/graduation-timeline.png
----------------------------------------------------------------------
diff --git a/assets/images/graduation-timeline.png b/assets/images/graduation-timeline.png
new file mode 100644
index 0000000..9ba02d5
Binary files /dev/null and b/assets/images/graduation-timeline.png differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/incbuator_feather_egg_logo_crop.png
----------------------------------------------------------------------
diff --git a/assets/images/incbuator_feather_egg_logo_crop.png b/assets/images/incbuator_feather_egg_logo_crop.png
new file mode 100644
index 0000000..3ad7e45
Binary files /dev/null and b/assets/images/incbuator_feather_egg_logo_crop.png differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/incubator_feather_egg_logo_bw_crop.png
----------------------------------------------------------------------
diff --git a/assets/images/incubator_feather_egg_logo_bw_crop.png b/assets/images/incubator_feather_egg_logo_bw_crop.png
new file mode 100644
index 0000000..377e4e3
Binary files /dev/null and b/assets/images/incubator_feather_egg_logo_bw_crop.png differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/incubator_feather_egg_logo_red_crop.png
----------------------------------------------------------------------
diff --git a/assets/images/incubator_feather_egg_logo_red_crop.png b/assets/images/incubator_feather_egg_logo_red_crop.png
new file mode 100644
index 0000000..e7bc1a7
Binary files /dev/null and b/assets/images/incubator_feather_egg_logo_red_crop.png differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/incubator_feather_egg_logo_wb_crop.png
----------------------------------------------------------------------
diff --git a/assets/images/incubator_feather_egg_logo_wb_crop.png b/assets/images/incubator_feather_egg_logo_wb_crop.png
new file mode 100644
index 0000000..3ec9f6d
Binary files /dev/null and b/assets/images/incubator_feather_egg_logo_wb_crop.png differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/incubator_power_ring.jpg
----------------------------------------------------------------------
diff --git a/assets/images/incubator_power_ring.jpg b/assets/images/incubator_power_ring.jpg
new file mode 100644
index 0000000..340fc68
Binary files /dev/null and b/assets/images/incubator_power_ring.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/incubator_ring_airflow.jpg
----------------------------------------------------------------------
diff --git a/assets/images/incubator_ring_airflow.jpg b/assets/images/incubator_ring_airflow.jpg
new file mode 100644
index 0000000..a64fe30
Binary files /dev/null and b/assets/images/incubator_ring_airflow.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/incubator_ring_logo.png
----------------------------------------------------------------------
diff --git a/assets/images/incubator_ring_logo.png b/assets/images/incubator_ring_logo.png
new file mode 100644
index 0000000..43a9815
Binary files /dev/null and b/assets/images/incubator_ring_logo.png differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/template_airflow.jpg
----------------------------------------------------------------------
diff --git a/assets/images/template_airflow.jpg b/assets/images/template_airflow.jpg
new file mode 100644
index 0000000..aed34aa
Binary files /dev/null and b/assets/images/template_airflow.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/template_hawq.jpg
----------------------------------------------------------------------
diff --git a/assets/images/template_hawq.jpg b/assets/images/template_hawq.jpg
new file mode 100644
index 0000000..9d88182
Binary files /dev/null and b/assets/images/template_hawq.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/assets/images/template_spot.jpg
----------------------------------------------------------------------
diff --git a/assets/images/template_spot.jpg b/assets/images/template_spot.jpg
new file mode 100644
index 0000000..83cfd2b
Binary files /dev/null and b/assets/images/template_spot.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/branding.ad
----------------------------------------------------------------------
diff --git a/pages/guides/branding.ad b/pages/guides/branding.ad
index 6549a0d..e7e967f 100644
--- a/pages/guides/branding.ad
+++ b/pages/guides/branding.ad
@@ -1,4 +1,15 @@
-= Branding Guide
+//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.
+= Incubator Branding Guide
Apache Incubator PMC
2002-10-16
:jbake-type: guide
@@ -7,12 +18,10 @@ Apache Incubator PMC
:toc:
:imagesdir: ../images/
-== Purpose of this document
Podlings are, by definition, not yet fully accepted as part of the
Apache Software Foundation. Therefore, they are subject to additional
branding constraints, on top of the
-<a href="http://www.apache.org/foundation/marks/responsibility">branding
-guidelines for top-level projects</a>.
+link:http://www.apache.org/foundation/marks/responsibility[branding guidelines for top-level projects]
== Publicity throughout the Incubation Process
@@ -22,15 +31,15 @@ on the types of publicity seeking that are permitted. We refer to
seeking publicity (seeding news stories, etc.).
*Podling is in proposal/or pre-code-drop process*: No publicity
-seeking is permitted. A podling is not allowed to be called <i>Apache
-"Podling-Name"</i> name until the podling is officially in
+seeking is permitted. A podling is not allowed to be called Apache
+_Podling-Name_ name until the podling is officially in
Incubation, public mailing lists are announced, and code has been
submitted into our repositories.
*Podling has been approved for incubation, podling has launched
public mailing lists, and podling has dropped code into
-repository*: A podling *MUST* now be called _Apache
-"Podling-Name"_ (see link:#naming[Naming] below).
+repository*: A podling *MUST* now be called Apache
+_Podling-Name_ (see link:#Naming[Naming] below).
A podling and affiliated persons can issue press releases that
reference the podling, but cannot issue press releases with the
specific intent of announcing the Podling. Podling can conduct
@@ -51,16 +60,14 @@ joint press release with any other affiliated organizations or groups.
== Naming
After a podling has been approved, the lists are created, and the initial
-code drop has commenced, the podling _MUST_ be referred to as *Apache
-"Podling-Name"* _AND_ mention that the project is
-under Incubation. Suitable mentions include:
+ code drop has commenced, the podling *MUST* be referred to as Apache
+ _Podling-Name_ *AND* mention that the project is
+ under Incubation. Suitable mentions include:
-- Inclusion of the ++http://"podling-name".incubator.apache.org/++ URL
-- *Apache "Podling-Name"* is currently undergoing Incubation at the Apache Software Foundation.
+- Inclusion of the http://_podling-name_.incubator.apache.org/ URL
+- Apache _Podling-Name_ is currently undergoing Incubation at the Apache Software Foundation.
-Other references may only be used upon prior approval by the
-Incubator PMC. These statements only need to be disclosed upon the
-first reference in a document.
+Other references may only be used upon prior approval by the Incubator PMC. These statements only need to be disclosed upon the first reference in a document.
== Disclaimers
@@ -69,15 +76,18 @@ website and in all documentation (including releases) stating that
they are in incubation. Podlings SHOULD use the following text for
all disclaimers (replace the underlined phrases as appropriate):
- Apache *Podling-Name* is an effort
- undergoing incubation at The Apache Software Foundation (ASF),
- sponsored by the *name of Apache TLP sponsor*. Incubation is required of all
- newly accepted projects until a further review indicates that the
- infrastructure, communications, and decision making process have
- stabilized in a manner consistent with other successful ASF projects.
- While incubation status is not necessarily a reflection of the
- completeness or stability of the code, it does indicate that the
- project has yet to be fully endorsed by the ASF.
+[quote]
+====
+Apache _Podling-Name_ is an effort
+undergoing incubation at The Apache Software Foundation (ASF),
+sponsored by the _name of Apache TLP sponsor_. Incubation is required of all
+newly accepted projects until a further review indicates that the
+infrastructure, communications, and decision making process have
+stabilized in a manner consistent with other successful ASF projects.
+While incubation status is not necessarily a reflection of the
+completeness or stability of the code, it does indicate that the
+project has yet to be fully endorsed by the ASF.
+====
Podlings wishing to use a different disclaimer message MUST have the
disclaimer approved by the Incubator PMC prior to use.
@@ -86,8 +96,7 @@ For releases, the text SHOULD be included in a separate DISCLAIMER file
stored alongside the NOTICE and LICENSE files.
== Incubator Logo
-Podlings websites SHOULD contain the Apache Incubator Project
-logo as sign of affiliation.
+Podlings websites should follow the logo description from link:press-kit.html[Press Kit for Podlings].
== Publicity activities
Podlings MUST coordinate with the Apache Public Relations Committee on
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/chair.ad
----------------------------------------------------------------------
diff --git a/pages/guides/chair.ad b/pages/guides/chair.ad
index 3f3b399..248fc4c 100644
--- a/pages/guides/chair.ad
+++ b/pages/guides/chair.ad
@@ -1,3 +1,14 @@
+//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.
= Incubator Chair Guide
Apache Incubator PMC
2002-10-16
@@ -7,21 +18,27 @@ Apache Incubator PMC
:toc:
:imagesdir: ../images/
-== Adding a new PMC member
-For a new PMC member being voted in, follow the link:http://www.apache.org/dev/pmc.html#newpmc[standard procedure]. For an ASF Member exercising their prerogative to join the IPMC by request, the only change in procedure is to alter the text of the NOTICE sent to the Board:
+== Adding New Incubator PMC Members
-----
+For a new PMC member being voted in, follow the link:http://www.apache.org/dev/pmc.html#newpmc[standard procedure].
+
+For an ASF Member exercising their prerogative to join the IPMC by request, the only change in procedure
+is to alter the text of the NOTICE sent to the Board:
+
+[source]
+--
To: board at apache.org
CC: private at incubator.apache.org
Subject: [NOTICE] *Jane Doe* for Incubator PMC
Body:
Apache Member *Jane Doe* has requested to join the Incubator PMC.
-----
+--
After the NOTICE period expires, a welcome message should be sent to the new IPMC member.
-----
+[source]
+--
Welcome to the Apache Incubator Project.
Here is some information to get you started as a PMC member.
@@ -33,26 +50,39 @@ Here is some information to get you started as a PMC member.
- the base incubator URL is https://svn.apache.org/repos/asf/incubator
-- all the public information, rules and policies about the Apache Incubator is in https://svn.apache.org/repos/asf/incubator/public/trunk/, and thus published on https://incubator.apache.org/
+- all the public information, rules and policies about the
+Apache Incubator is in
+https://svn.apache.org/repos/asf/incubator/public/trunk/,
+and thus published on https://incubator.apache.org/
-- https://home.apache.org/phonebook.html?ctte=incubator lists all PMC members. This is periodically regenerated from https://svn.apache.org/repos/private/committers/board/committee-info.txt.
+- https://home.apache.org/phonebook.html?ctte=incubator
+lists all PMC members. This is periodically regenerated from
+https://svn.apache.org/repos/private/committers/board/committee-info.txt.
-- the Incubator website is maintained and published according to the instructions at http://incubator.apache.org/guides/website.html
+- the Incubator website is maintained and published according to the
+instructions at http://incubator.apache.org/guides/website.html
-- status documents about Incubating projects are under incubator/public/trunk/content/project/ directory; please keep the ones you are mentoring updated
+- status documents about Incubating projects are under
+incubator/public/trunk/content/project/ directory;
+please keep the ones you are mentoring updated
-- all committers on all incubating projects have access to the 'incubator/public' repository, so they can participate in the general Incubator Project as committers
+- all committers on all incubating projects have access to
+the 'incubator/public' repository, so they can
+participate in the general Incubator Project as committers
-- please read our work documents under incubator/public/trunk/content/incubation/ for more information about the incubation process; they are published under https://incubator.apache.org/incubation/
+- please read our work documents under
+incubator/public/trunk/content/incubation/
+for more information about the incubation process; they are
+published under https://incubator.apache.org/incubation/
Thanks for helping us!
-----
+--
== Board Report
The Incubator link:http://www.apache.org/foundation/board/reporting[reports] monthly to the Apache
link:http://www.apache.org/foundation/board[Board of Directors]. The report itself is the collaborative effort of
-many Incubator contributors, but the Chair is ultimately responsible for ensuring that it is filed.
+many Incubator contributors, but the Chair is ultimately responsible for ensuring that it is filed.
The Board appreciates receiving the IPMC report:
@@ -61,7 +91,7 @@ The Board appreciates receiving the IPMC report:
- with an accurate summary of the state of the reporting podlings
The "runbook" for managing the preparation of the report is implemented as a script which prints out documentation,
-instructions, literal commands, due dates, etc: https://svn.apache.org/repos/asf/incubator/public/trunk/report_runbook.py[report_runbook.py]
+instructions, literal commands, due dates, etc in link:https://svn.apache.org/repos/asf/incubator/public/trunk/report_runbook.py[report_runbook.py]
Many of the tasks documented in the runbook may be attended to by either the Chair or a designee such as a "Report
Manager", but it's the Chair who is accountable for overseeing the process.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/committer.ad
----------------------------------------------------------------------
diff --git a/pages/guides/committer.ad b/pages/guides/committer.ad
index 5e8e04d..53d6332 100644
--- a/pages/guides/committer.ad
+++ b/pages/guides/committer.ad
@@ -1,5 +1,16 @@
-= Committer Guide
-Apache Incubator PMC`
+//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.
+= Committers
+Apache Incubator PMC
2002-10-16
:jbake-type: guide
:jbake-status: published
@@ -7,78 +18,69 @@ Apache Incubator PMC`
:toc:
:imagesdir: ../images/
-The link:http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Committers[Roles and Responsibilities] document describes the general role of a
-committer on an incubating project. This page provides links to
-more information to help new committers get started.
+The link:/policy/incubation.html#Committers[Roles and Responsibilities] document describes the general role of a
+committer on an incubating project. This page provides links to more information to help new committers get started.
== Mailing Lists
-
Everything -- but *everything*-- inside the Apache world
occurs or is reflected in email. As some people say, 'If it isn't
in my email, it didn't happen.' Decisions only get made on public
-Apache mail lists -- not anywhere off list, such as IRC, IM, or private
+Apache mail lists -- not anywhere off list, such as IRC, IM, or private
emails.
Each project has a set of lists, which are typically called
-*project*-dev, *project*-user, and
-*project*-commits. A few link:http://www.apache.org/foundation/mailinglists.html[Apache-wide lists] cross all boundaries, including:
-
-- _committers_: sends important messages to all Apache committers; it's not used for discussions;
-- _community_: where all Apache committers can discuss things that are about Apache;
-- _infrastructure_: where the roots and the infrastructure team discuss and work on the Apache infrastructure needs;
-- _legal-discuss_: where Apache committers can ask questions that have a legal aspect;
-- _repository_: discussions about the Apache artifact repository;
-- _party_: where people plan how to have fun. :-)
-
-Action items for committers include:
-
-- Become familiar with Apache developer link:http://www.apache.org/dev/contrib-email-tips.html[Tipsfor email contributors].
-- Subscribe to the -user, -dev, and -commits lists for your project.
+dev@*project*, user@*project*, and
+commits@*project*. A few link:http://www.apache.org/foundation/mailinglists.html[Apache-wide lists] cross all boundaries, including:
+
+- *committers*: sends important messages to all
+Apache committers; it's not used for discussions;
+- *community*: where all Apache committers can
+discuss things that are about Apache;
+- *infrastructure*: where the roots and the
+infrastructure team discuss and work on the Apache
+infrastructure needs;
+- *legal-discuss*: where Apache committers can
+ask questions that have a legal aspect;
+- *repository*: discussions about the Apache artifact repository;
+- *party*: where people plan how to have fun. :-)
+
+=== Action items for committers include:
+
+- Become familiar with Apache developer link:http://www.apache.org/dev/contrib-email-tips.html[Tips for email contributors].
+- Subscribe to the user, dev, and commits lists for your project.
- Become aware of what else is going on in the Incubator by subscribing to the Incubator's general list.
-- Become aware of what else is going on at the ASF by subscribing to the
-link:http://www.apache.org/foundation/mailinglists.html#foundation-community[community],
-link:http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure[infrastructure],
-and link:http://www.apache.org/foundation/mailinglists.html#foundation-legal[legal-discuss] Apache-wide lists.
-
+- Become aware of what else is going on at the ASF by subscribing to the link:http://www.apache.org/foundation/mailinglists.html#foundation-community[community], link:http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure[infrastructure], and link:http://www.apache.org/foundation/mailinglists.html#foundation-legal[legal-discuss] Apache-wide lists.
Apache also has private lists. For example, your project will
-probably have a private mail list named *project*-private,
-which your Podling PMC will use for sensitive discussions. Never
-mix public and private mail lists in the same post -- see the
+probably have a private mail list named private@*project*.incubator.apache.org,
+which your Podling PMC will use for sensitive discussions. Never
+mix public and private mail lists in the same post -- see the
section titled link:http://www.apache.org/foundation/how-it-works.html#management[Balancing confidentiality and public discussion]
in link:http://www.apache.org/foundation/how-it-works.html[How it Works]. For example, never include both your dev and private
lists in the same post. Posting to the dev list is sufficient
because each member of your Podling PMC will also be on that
-list.
+list.
== Project Web Site
-The Incubator link:sites.html[Podling Websites] guide documents how to get
-your project web site going.
+The Incubator link:sites.html[Podling Websites] guide documents how to get your project web site going.
== Committer Resources
-- The link:http://www.apache.org/dev/new-committers-guide.html[Guide for New Committers ]is a great place to start and
-points to additional committer-only resources.
-
-- Browse the pages at http://www.apache.org/dev/ often.
+- The link:http://www.apache.org/dev/new-committers-guide.html[Guide for New Committers ]is a great place to start and points to additional committer-only resources.
+- Browse the pages at link:http://www.apache.org/dev[http://www.apache.org/dev/] often.
+- Subscribe to the link:http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure[infrastructure] list, then raise awareness on your project on what goes on behind the scenes.
-- Subscribe to the link:http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure[infrastructure] list, then
-raise awareness on your project on what goes on behind the
-scenes.
-- Be proactive about responding to infrastructure issues on
-your project mailing lists. Does the web server seem to be
-down? Is Jira or Subversion down? Check the link:http://www.apache.org/dev/#status[status of servers]
-and explain the reason to your project lists (as you can
-see, no need to alert the ASF infrastructure people).
+Be proactive about responding to infrastructure issues on your project mailing lists. Does the web server seem to be down? Is Jira or Subversion down? Check the link:http://www.apache.org/dev/#status[status of servers]
+and explain the reason to your project lists (as you can see, no need to alert the ASF infrastructure people).
== Podling PMC (PPMC)
-
-If you are a member of your PPMC, become familiar with the link:../incubation/Incubation_Policy.html[Incubation Policy]
-and see the link:ppmc.html[Podling PMC Guide].
+If you are a member of your PPMC, become familiar with the link:/policy/incubation.html[Incubation Policy] and see the link:ppmc.html[Podling PMC Guide].
== Questions?
+If you have any questions, please ask on the Incubator's
+general mail list.
+Don't forget to check the information at:
-If you have any questions, please ask on the Incubator's general mail list. Don't forget to check the information at:
-
-- http://www.apache.org/dev/ -- it is one of the most current resources for committers.
-- link:general.html#FAQ[Incubator General FAQ]
\ No newline at end of file
+- link:http://www.apache.org/dev[http://www.apache.org/dev/]
+** it is one of the most current resources for committers.
+- link:general.html#FAQ[Incubator General FAQ]
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/community.ad
----------------------------------------------------------------------
diff --git a/pages/guides/community.ad b/pages/guides/community.ad
new file mode 100644
index 0000000..907ed1b
--- /dev/null
+++ b/pages/guides/community.ad
@@ -0,0 +1,191 @@
+//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.
+= Guide to Successful Community Building
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+Help to improve the system by posting a patch for
+this document to the incubator section of JIRA or a
+comment to the link:lists.html[general] list at
+incubator.
+
+== Abstract
+
+The intent of this document is to help podlings the
+importance of building an open and diverse community for
+their project. It gives guidelines on how to accept new
+committers and PPMC members, and how to enable more
+community involvement, taking off the burden of answering
+every question yourself.
+
+== What is an open and diverse community?
+
+A major criterion for graduation is to have developed an open
+and diverse link:http://www.apache.org/foundation/glossary.html#Meritocracy[meritocratic]
+community. Time has demonstrated that these kinds of
+communities are more robust and productive than more closed
+ones.
+
+=== People
+
+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. link:#notes-community[Community building] requires energy
+which could have been spent on code development but this cost
+is an important investment for the future of the project.
+
+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.
+
+=== Communication
+
+
+Mailing lists are the life blood of Apache communities. They
+are the primary mode of discourse and constitute a public and
+historic record of the project. Other forms of communication
+(P2P, F2F, personal emails and so on) are secondary. There are
+well founded fears about use of these media for project
+communication. Though many projects successfully blend other
+forms of communications, care needs to be taken since
+out-of-band communications have led to difficulties in the
+past. The reason is that communications on other than the
+public mail aliases exclude parts of the community. Even
+publicly advertised IRC chats can be exclusionary due to time
+zone constraints or conflicting time commitments by community
+members who might want to participate.
+
+Apache project mailing lists are public, well indexed and well
+archived. This allows anyone to monitor (both in real time and
+by browsing the archives) what's happening. Opinions expressed
+are public and poor behavior risks a poster's reputation.
+
+Private communications tend to be more candid but also more
+likely to be ill-judged. Back channel communication tend to be
+divisive, excluding some members of the group. This tends to
+have a corrosive effect on the collective spirit of the
+community. Mistrust builds when opinions backed by blocks of
+developers arise fully formed on list.
+
+Communication through other channels also reduces the chance
+of link:http://en.wikipedia.org/wiki/Serendipity[serendipity].
+As with most social networks, most subscribers to a mailing
+list never post and most posts come from a tiny minority of
+subscribers. Some passive subscribers are just interested in
+where the project is going but others understand related
+fields and have a limited intersection of interest. This
+second group will often post when this topic arises on list.
+Using public mailing lists to develop designs allows the
+chance encounter of ideas which often results in innovation.
+
+If alternative forums are used by a project, it is important
+to try to minimize the chances of problems arising. All
+matters of substance need to be moved back to the mailing
+lists. Public records should be kept and posted back to the
+list. Regular reminders should be posted to remind people that
+other secondary forms of communication exist.
+
+There are a limited number of topics such as security issues
+and discussions about people which are best handled in
+private. As much business of the project as possible should
+take place on public lists but the private list is available
+for those matters of a sensitive nature. Good netiquette
+requires that permission from the poster should be sought
+before making public, posts made to a private list. Try to
+avoid cross-posting between public and private forums. Take
+care not to post a reply to a private post to a public forum
+without permission.
+
+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.
+
+=== Community Building
+
+Before a podling graduates, it must create a diverse and
+self-sustaining community. Community building is tough: it
+takes time, effort and more than a little magic. There is no
+secret recipe, just hard work. In order to overcome this
+obstacle, committers may need to devote more time to community
+building and less to development.
+
+The link:mailto:community@apache.org[community mailing list] is open to all Apache committers. This is the right
+list for questions about community and on community building.
+Subscriptions should be from an Apache email address.
+
+==== Raising The Profile
+
+Sometimes, a podling is just not well-enough known. There
+are simply not enough users to allow new developers to be
+recruited. Overcoming this means finding ways to raise the
+profile of the podling. Some ideas:
+
+- Improve the website
+- Improve the information provided within each release and release more often
+- Committers who blog should join link:http://www.apache.org/dev/committers.html#planetapache[PlanetApache]
+- Use grassroots media
+- Encourage downstream distributions to include a packaged version
+- Submit talks to conferences
+- link:http://www.feathercast.org[Feathercast]
+- Write articles
+
+==== Building a community by stepping back a little
+
+
+If the podling has lots of users but very few new
+developers then this means that more work is required to
+encourage users to become developers. A common cause of
+this is that committers are too quick to create code to
+solve user problems. It's good to respond quickly to
+requests by users. However, once a project gains momentum,
+it may be more productive for the long term health of a
+project to encourage users to become more involved at the
+expense of user satisfaction.
+
+Try to encourage expert users to answer questions. This
+may mean intentionally allowing a time gap before
+answering user questions. Encourage users to post by
+taking the time to deal politely and positively with
+misunderstandings and by replying to threads which have
+been answered well by a user to confirm that they are
+right. Avoid engaging in flame wars on user lists. Ignore
+trolls.
+
+Try to encourage users to become developers. When they
+give a good answer that isn't covered in the
+documentation, ask them to submit a patch. When users
+suggest a good design or extension, ask for volunteers to
+help implement rather than just coding it up.
+
+==== Helping Developers Become Committers
+
+If a podling has no trouble attracting developers but
+trouble retaining them long enough for them to become
+committers then this highlights an issue with the
+recruitment process. To become an Apache committer, a
+developer needs to hang around long enough to accumulate a
+track record of contributions. This often requires
+encouragement and help from existing committers.
+
+Promptly reviewing patches is important. The way that
+patches are applied is also important. Provide credit in
+the commit message and when closing the JIRA. It's also
+good to encourage developers by suggesting new related
+work they may like to volunteer for.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/entry.ad
----------------------------------------------------------------------
diff --git a/pages/guides/entry.ad b/pages/guides/entry.ad
new file mode 100644
index 0000000..61e3039
--- /dev/null
+++ b/pages/guides/entry.ad
@@ -0,0 +1,82 @@
+//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.
+= Enter The Incubator
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+This document is under link:#help-wanted[development]. At the moment, this
+is just a skeleton outline.
+
+== Background
+
+This document is descriptive not normative. It discusses and describes
+the process of incubator entry and offers some views about how to approach it.
+It is not an inflexible standard but
+represents a consensus condensed from previous discussions on the
+incubator general list.
+
+=== Help Wanted!
+
+Help to improve the system by posting a patch for this document to the
+incubator section of JIRA or a comment to the general list at incubator.
+
+== Understanding The Acceptance Process
+
+The acceptance process is simple in theory but complex in practice.
+
+The theory is that candidates are accepted or rejected by a vote on a mailing lists.
+Anyone can vote (and are link:participation.html#general-list[encouraged] to do so)
+but only eligable votes are binding on Apache. For candidates
+link:/incubation/Roles_and_Responsibilities.html#Sponsor[Sponsored]
+by the *Incubator* this means members of the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Incubator PMC].
+
+In practice, the process is more complex for candidates who want to give themselves
+the best chance of being accepted.
+
+Apache policy is set by the Board either directly or through it's special committees.
+The incubation PMC is responsible to the board and so it is the duty of each PMC member
+to vote against a proposal that does not adhere to this policy.
+
+link:/incubation/Incubation_Policy.html[Incubation Policy] state clearly when a .
+All policy is decided by PMC vote and so represents an active consensus. Though PMC members
+are free to vote in whatever way they choose, it is reasonable to expect PMC members
+to vote against a proposal that does not satisfy policy.
+
+However, satisfying current policy is not sufficient. Acceptance is a democractic process
+requiring positive approval by the electorate. The guides and other documentation are not
+policy. They are approved only through lazy consensus.
+
+See:
+- [links to posts and threads]
+
+== Notes On The Process
+
+=== The Proposal
+
+=== The Vote
+
+When the proposal seems finished and some sort of consensus has emerged, the
+proposal can be put to the vote.
+
+The right time is a matter for judgement. Ask the
+link:/incubator/Roles_and_Responsibilites.html#Champion[Champion] for advice
+or ask on the mailing list. It is usually best to ensure that the discussions
+and debates surrounding the proposal are complete before moving to a vote. This may
+mean move discussions which are not about the proposal to separate threads.
+
+The right duration for the vote is also a matter for judgement [link].
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/graduation-template.txt
----------------------------------------------------------------------
diff --git a/pages/guides/graduation-template.txt b/pages/guides/graduation-template.txt
new file mode 100644
index 0000000..9bf479e
--- /dev/null
+++ b/pages/guides/graduation-template.txt
@@ -0,0 +1,52 @@
+Establish the Apache <Name> Project
+
+WHEREAS, the Board of Directors deems it to be in the best
+interests of the Foundation and consistent with the
+Foundation's purpose to establish a Project Management
+Committee charged with the creation and maintenance of
+open-source software, for distribution at no charge to the
+public, related to <a clear mission statement>
+
+NOW, THEREFORE, BE IT RESOLVED, that a Project Management
+Committee (PMC), to be known as the "Apache <Name> Project", be
+and hereby is established pursuant to Bylaws of the Foundation;
+and be it further
+
+RESOLVED,that the Apache <Name> Project be and hereby is
+responsible for the creation and maintenance of software
+related to <same mission statement>.
+
+RESOLVED, that the office of "Vice President, Apache <Name>" be
+and hereby is created, the person holding such office to serve
+at the direction of the Board of Directors as the chair of the
+Apache <Name> Project, and to have primary responsibility for
+management of the projects within the scope of responsibility
+of the Apache <Name> Project; and be it further
+
+RESOLVED, that the persons listed immediately below be and
+hereby are appointed to serve as the initial members of the
+Apache <Name> Project:
+
+<< here, list out each PMC member, in the format of
+* First Last <apache email>
+>>
+
+NOW, THEREFORE, BE IT FURTHER RESOLVED, that <Elected VP> be
+appointed to the office of Vice President, Apache <Name>, to
+serve in accordance with and subject to the direction of the
+Board of Directors and the Bylaws of the Foundation until
+death, resignation, retirement, removal or disqualification,
+or until a successor is appointed; and be it further
+
+RESOLVED, that the initial Apache <Name> PMC be and hereby is
+tasked with the creation of a set of bylaws intended to
+encourage open development and increased participation in the
+Apache <Name> Project; and be it further
+
+RESOLVED, that the Apache <Name> Project be and hereby is tasked
+with the migration and rationalization of the Apache Incubator
+<Name> podling; and be it further
+
+RESOLVED, that all responsibilities pertaining to the Apache
+Incubator <Name> podling encumbered upon the Apache Incubator
+Project are hereafter discharged.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/graduation.ad
----------------------------------------------------------------------
diff --git a/pages/guides/graduation.ad b/pages/guides/graduation.ad
new file mode 100644
index 0000000..c796f02
--- /dev/null
+++ b/pages/guides/graduation.ad
@@ -0,0 +1,715 @@
+//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.
+= Guide to Successful Graduation
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+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
+link:http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator[exit policies].
+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.
+
+*This is just a guide. Policy is stated link:https://incubator.apache.org/incubation/Incubation_Policy.html[here].*
+
+Help to improve the system by posting a patch for
+this document to the incubator section of JIRA or a
+comment to the link:lists.html#general+at+incubator.apache.org[general] list at
+incubator.
+
+== What is Graduation?
+
+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 *link:http://www.apache.org/foundation/voting.html[VOTE]*. Note
+that during your stay in the incubator, you are already busy
+with the process of Graduating: by adopting Apache procedures,
+growing and fostering your community, having (civil) fights
+concerning code style (tabs versus spaces), cutting releases
+and so forth. All these acts have an influence on your
+projects graduation.
+
+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.
+
+This document is offered for guidance and education only.
+Actual policy is documented in the link:../incubation/Incubation_Policy.html[Incubation PolicyGuide] in
+link:../incubation/Incubation_Policy.html#Graduating+from+the+Incubator[this]
+section. Please post any questions about graduation
+to the link:lists.html#general+at+incubator.apache.org[general incubator list].
+
+== Whether to Graduate to Subproject or to Top Level Project
+
+Each proposal has a link:/incubation/Roles_and_Responsibilities.html#Sponsor[Sponsor].
+The identity of the Sponsor indicates the natural
+destination. For proposals sponsored by the link:/incubation/Roles_and_Responsibilities.html#board[Board] or by
+the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IncubatorPMC (IPMC)], 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.
+
+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 link:http://www.apache.org/foundation/how-it-works.html#structure[PMC].
+Graduation as a project requires the formation of the new
+project by the link:/incubation/Roles_and_Responsibilities.html#board[Board].
+
+The link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC]
+will also express a democratic opinion. For those seeking
+to graduate to a subproject this *link:http://www.apache.org/foundation/voting.html[VOTE]*
+is to approve the
+transfer. For those seeking to graduation as a top level
+project, this will be a recommendation to the link:/incubation/Roles_and_Responsibilities.html#board[Board].
+Expect IPMC-ers to ask questions about the project
+including about the choice of destination. This is part of
+the normal process.
+
+== Before You Graduate
+
+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.
+
+=== Graduation Check List
+
+The following is a short checklist giving an overview, not
+a substitute for reading the content below.
+
+* Preparations
+** Complete (and sign off) tasks documented in the link:#notes-status[status file]
+** Ensure link:#notes-names[suitable names] for project name and product names
+** Demonstrate ability to link:#releases[create Apache releases]
+** Demonstrate link:#community[community readiness]
+** Ensure link:/incubation/Roles_and_Responsibilities.html#Mentor[Mentors] and link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC] have no link:#notes-issues[remaining issues]
+* Decide upon link:#subproject-or-top-level[destination]
+* Prepare a link:#tlp-resolution[resolution] *(top level candidates only)*.
+* link:#subproject-acceptance[Subproject acceptance *VOTE*] by destination Project *(subproject candidates only)*
+* link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Incubator PMC (IPMC)]:
+** For top level candidates, this is a link:#ipmc-top-level-recommendation[recommendation *VOTE*]
+** For subproject candidates, this is a link:#subproject-graduation[graduation approval *VOTE*]
+* Final link:#notes-on-hand-over[hand-over]
+* Consider post graduation link:#project-first-steps[tasks]
+
+=== Checking the Status File
+
+The status file records and summarizes incubation-related
+information on the podling. The
+link:ppmc.html#Incubator+ASF+Board+Reports[PPMC] is
+responsible for keeping this file current. Before you are
+able to graduate, all tasks need to be completed.
+
+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 link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Incubator PMC]
+will check this
+file when they vote on the graduation of your project.
+Once all tasks are done and the listed criteria met, your
+project may be ready for graduation.
+
+The status file of the JUDDI project is link:http://incubator.apache.org/projects/juddi.html[one example].
+
+== Ensure suitable project name and product names
+
+Please read link:http://www.apache.org/foundation/marks/naming.html[detailed documentation here].
+The "Process for ensuring suitable project and product names" is mandatory for every podling which wants to
+graduate.
+
+== Creating an Apache Release
+[quote,Eric Steven Raymond, http://catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html]
+====
+Release Early, Release Often
+====
+
+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 *publish* a
+release to demonstrate that they understand how to
+accomplish such a feat. However, creating a release that
+is approved by the link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[incubator project management committee] is usually the
+simplest way to do this.
+
+If you are going to cut a release (which is highly
+recommended), then please read the link:releasemanagement.html[Incubator Release Management Guide] for hints, tips and guidelines for cutting a
+release that will get approved by the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC]
+without problems.
+
+== Creating an Open and Diverse community
+
+A major criterion for graduation is to have developed an
+open and diverse link:http://www.apache.org/foundation/glossary.html#Meritocracy[meritocratic]
+community. Time has demonstrated that these kinds of
+communities are more robust and productive than more
+closed ones.
+
+Apache projects are self-sustaining and self-governing
+communities. Long term success and health requires that
+these communities understand how to:
+
+- recruit users, developers, committers and PMCers
+- take responsible collective action
+- disagree in public on technical matters without destroying personal relationships
+- create an open, positive and inclusive atmosphere on the mailing lists
+
+Graduation tests whether (in the opinion of the link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC])
+a podling has learned enough and is responsible enough to
+sustain itself as such a community.
+
+Read more on how to successfully build an open and diverse
+community for your podling in the link:community.html[community guide].
+
+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. link:community.html[Community building] requires
+energy which could have been spent on code development but
+this cost is an important investment for the future of the
+project.
+
+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.
+
+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.
+
+Growing an open and diverse meritocratic community is not
+something that just happens: it takes work. Read the link:community.html[building a community guide] for
+guidelines, hints and tips on how you can accomplish this
+for your project.
+
+=== Other Issues
+
+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.
+
+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.
+
+== The Graduation Process
+
+=== Graduating to a Top Level Project
+
+Top level projects are created by the
+link:/incubation/Roles_and_Responsibilities.html#board[Board]. The
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Incubator Project Management Committee (IPMC)] can therefore only
+recommend to the Board that the project is ready to
+graduate to a top level project.
+
+Graduation to a top level project requires:
+
+- a charter for your project
+- a positive community graduation *link:http://www.apache.org/foundation/voting.html[VOTE]*
+- a positive IPMC recommendation *link:http://www.apache.org/foundation/voting.html[VOTE]*
+- the acceptance of the link:#tlp-resolution[resolution] by the Board
+
+This process can take a while, since it typically sparks
+some discussion inside the community and possibly in the
+IPMC.
+
+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.
+
+image:/images/graduation-timeline.png[Graduation timeline]
+
+For each event we scheduled one or two weeks. Even though
+a *link:http://www.apache.org/foundation/voting.html[VOTE]*
+is usually limited to 72 hours, you should prepare
+for discussion and possibly having to cast a revote with a
+revised proposal.
+
+=== Community Graduation Vote
+
+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 *link:http://www.apache.org/foundation/voting.html[VOTE]* (by the
+community) on the graduation proposal.
+
+This *VOTE* is not a requirement but is recommended. It
+is unlikely that link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC]members
+will vote to approve graduation unless the link:/incubation/Roles_and_Responsibilities.html#Mentor[Mentors]
+and community positively express their readiness for
+graduation. It is wise to notify the
+link:lists.html#general+at+incubator.apache.org[incubator general list] 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
+
+=== Preparing a Charter
+
+So, in this case a suitable
+link:/incubation/Roles_and_Responsibilities.html#board[Board] resolution should be
+drawn up by the community advised by the
+link:/incubation/Roles_and_Responsibilities.html#Mentor[Mentors].
+Committers can access the podling template for
+resolutions in the
+link:https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt[committers svn repository]. Also, resolutions are included in
+the Board minutes, which are posted publicly
+link:http://www.apache.org/foundation/board/calendar.html[here ] . These contain numerous examples. Good
+examples include:
+
+- Harmony (see section *E. Establish the Apache Harmony project* in the link:http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_10_25.txt[October 2006 Board minutes])
+- OFBiz (see section *B. Establish Apache Open for Business Project* in the link:http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_12_20.txt[December 2006 Board minutes])
+- Cayenne (see section *C. Establish Apache Cayenne Project* in the link:http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_12_20.txt[December 2006 Board minutes])
+
+link:/guides/graduation-template.txt[Click here for a template of this proposal to use.]
+
+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
+link:/incubation/Roles_and_Responsibilities.html#board[Board]
+resolution is the ultimate definition of the scope of
+an Apache project. So, it is important that it
+reflects the vision for the project as it appears on
+the eve of graduation.
+
+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.
+
+If you read these resolutions you also see that you
+need to appoint a link:http://www.apache.org/foundation/glossary.html#Chair[Chair]
+for your project. It is up to the
+link:ppmc.html[PPMC] to choose one
+person to act as the chair after graduation.
+
+=== The Recommendation Vote
+
+The link:#tlp-resolution[resolution] should be proposed on the general
+link:mailto:general@incubator.apache.org[incubator list] before a *link:http://www.apache.org/foundation/voting.html[VOTE]*
+is started to allow feedback. Once a consensus has been reached, a *VOTE*
+should be started on the same general incubator list by a member of the link:ppmc.html[PPMC] proposing
+that the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC]
+recommends the resolution to the link:/incubation/Roles_and_Responsibilities.html#board[Board].
+
+=== Submission of the Resolution to the Board
+
+Top level projects are created by a link:#tlp-resolution[resolution] by the
+link:/incubation/Roles_and_Responsibilities.html#board[Board].
+Once the link:#tlp-resolution[resolution] 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 link:http://www.apache.org/foundation/board/calendar.html[available].
+
+Business for the link:/incubation/Roles_and_Responsibilities.html#board[Board] should be submitted by a post
+to the *board* mailing list. Posting from
+an Apache address is recommended. Mixing public and
+private lists on a post is not recommended.
+
+The *board* list is private.
+The usual link:http://www.apache.org/foundation/how-it-works.html#management[netiquette]
+for Apache private lists should be observed. So, it is
+recommended that only the podling and
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC]
+private lists are CC'd (rather than the general incubator
+list). Please treat responses with appropriate
+confidentiality.
+
+The submission should include:
+- A clear subject (for example *Establish Foo TLP*)
+- A brief introduction
+- The name of proposed VP
+- Links to the *VOTE* threads
+- Summary of the *VOTE* results
+- The link:#tlp-resolution[resolution] text
+
+For example:
+[source]
+====
+From: <you _at_ apache dot org>
+To: <board _at_ apache dot org>
+CC: <<project>-private _at_ incubator dot apache dot org>
+Subject: proposed resolution: establish <project> TLP
+
+Dear Apache Board,
+
+<Project> is ready for graduation out of the incubator. So, please
+consider the draft resolution below at your next meeting.
+
+<thank you, best regards, personal note if you wish, etc etc>
+
+<your name>
+
+--
+References:
+
+Home: <project home page>
+Vote by project: <link to vote thread on project list>
+Vote by incubator: <link to vote thread on general list>
+
+Resolution draft:
+
+<<resolution goes here, 72 characters wide,
+indent with 4 spaces>>
+
+--
+<your e-mail sig, if you have one>
+====
+
+Please try to keep the *board* list traffic low. Do not
+submit reminders or ask whether messages have been
+received on the list. link:http://www.apache.org/foundation/members.html[Apache Members] have access to the link:/incubation/Roles_and_Responsibilities.html#board[Board]
+archives and may
+observe Board meetings. To follow the progress of a
+resolution, please ask a friendly Member or
+link:http://www.apache.org/foundation/board/[Director].
+
+=== Press Releases for new TLPs
+
+Once there is clear consensus that the recommendation will happen,
+a member of the PPMC should contact ASF Marketing & Publicity at
+*press(at)apache(dot)org* 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.
+
+== Graduating to a Subproject
+
+Subprojects are accepted by a Project Management
+Committee. The link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Incubator Project Management Committee]
+needs to approve the graduation of the podling to a
+subproject.
+
+=== Community Graduation Vote
+
+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
+*link:http://www.apache.org/foundation/voting.html[VOTE]*
+(by the community) on the graduation proposal.
+
+This *VOTE* is not a requirement but is recommended. It
+is unlikely that
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC]
+members will vote to approve graduation unless the
+link:/incubation/Roles_and_Responsibilities.html#Mentor[Mentors]
+and community positively express their readiness for
+graduation. It is wise to copy the
+link:lists.html#general+at+incubator.apache.org[incubator general list] and the
+link:/incubation/Roles_and_Responsibilities.html#Sponsor[sponsoring top level project] when the *VOTE*
+is proposed.
+
+=== Subproject Acceptance Vote
+
+
+A formal *link:http://www.apache.org/foundation/voting.html[VOTE]*
+by the Project link:http://www.apache.org/foundation/how-it-works.html#structure[PMC]
+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.
+
+=== Graduation Approval Vote
+
+To graduate as a subproject, the link:/incubation/Roles_and_Responsibilities.html#Mentor[Mentors] should start a *link:http://www.apache.org/foundation/voting.html[VOTE]*
+thread on the link:lists.html#general+at+incubator.apache.org[general list] proposing that the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC] 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.
+
+== Life After Graduation
+
+=== Handover
+
+This is the transfer of virtual resources from the care of
+the link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[IPMC]
+to the care of either the new or existing top
+level project taking charge of the graduating community.
+
+==== Graduating as Subproject
+
+This is the simple case. The
+link:/incubation/Roles_and_Responsibilities.html#Chair+of+the+Incubator+PMC[IPMC Chair] and the Chair of the project accepting the
+graduating community organize the handover between
+themselves.
+
+==== Graduating as New Top Level Project
+
+When graduating to a new project, the process is more
+complex. Creating a new project requires a
+link:http://www.apache.org/foundation/board/calendar.html[resolution]
+to be passed by the link:http://www.apache.org/foundation/board/[Board].
+Usually once this happens, members of the Board will
+inform the appropriate chairs and link:http://www.apache.org/foundation/how-it-works.html#structure[PMCs].
+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.
+
+The link:#tlp-resolution[resolution] will appoint a Chair for the new
+project. The Chair will also be appointed an
+link:http://www.apache.org/foundation/[Officer]
+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.
+
+Once appointed, the new Chair needs to:
+
+- Subscribe to the *board* mailing list
+- Subscribe to the *infrastructure* mailing list
+- Ensure that they have been added to
+link:https://people.apache.org/phonebook.html?service=pmc-chairs[the PMC chairs group (pmc-chairs) in LDAP].
+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.
+- Check out the link:https://svn.apache.org/repos/private/foundation/officers[*foundation/officers*] folder from the private repository.
+Users with member or pmc-chairs karma can do this.
+- Add yourself to the #foundation/officers/affiliations.txt# and the #foundation/officers/irs-disclosures.txt* files with the appropriate information.
+- Add your details to the foundation web site Officer list at link:http://www.apache.org/foundation/index.html[http://www.apache.org/foundation/index.html] (in SVN at link:https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/foundation/[https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/foundation/])
+- Review appropriate documentation:
+** link:http://www.apache.org/dev/pmc.html#chair[PMC Chair Duties]
+** PMC link:http://www.apache.org/dev/#pmc[documentation]
+** Jakarta link:http://wiki.apache.org/jakarta/RoleOfChair[Chair guide]
+** Incubator link:http://incubator.apache.org/guides/chair.html[Chair guide]
+** Reporting link:http://www.apache.org/foundation/board/calendar.html[calendar]
+- Work out a reporting schedule with the link:/incubation/Roles_and_Responsibilities.html#board[Board]. 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.
+- Work with the link:http://www.apache.org/dev/index.html#infra[Apache Infrastructure team]
+to set up the top level project
+infrastructure. The various infrastructure tasks that are required
+(see link:#transfer[check list])
+should be consolidated into a single issue (see link:https://issues.apache.org/jira/browse/INFRA-4069[this]
+for example). This should be created in the category
+link: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].
+- Ensure the PMC is added to the committee-info.txt file at https://svn.apache.org/repos/private/committers/board/committee-info.txt
+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.
+
+They should then be able to start assembling the new
+link:http://www.apache.org/foundation/how-it-works.html#structure[PMC].
+The starting membership is listed in the
+link:#tlp-resolution[resolution]. However, the Chair of the new project
+needs to ensure that private list is created and the
+membership subscribed.
+
+Members of the new PMC need to:
+- Subscribe to the private mailing list for the project
+- Review appropriate documentation:
+** Apache link:http://www.apache.org/dev/pmc.html[PMC Guide]
+** Related link:http://www.apache.org/dev/#pmc[documentation]
+
+Once all this is in place, resources can start to be
+handed over to the new project.
+
+Please continue to hang around the Incubator and help
+new podlings have an easier time than you did!
+
+=== First Steps Outside the Incubator
+
+Graduation is the first step in what is hopefully a long road.
+There are some issues which incubation may not cover.
+
+==== Transferring Resources
+
+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.
+
+Although the below checklist is still generally useful, *the infrastructure process has been streamlined*, see
+http://www.apache.org/dev/infra-contact#requesting-graduation . You might also want to check JIRA checklist tickets for projects that graduated in the last month or two.
+
+Checklist:
+
+- Update the Incubator status records
+** Like the rest of incubation, graduation is a process. Updating your
+status records as you progress will enable others to assist.
+** Update the podling
+link:#notes-status[status page].
+All sections should now be filled in
+including *EXIT*. Take some
+time to read carefully since this page
+forms the final public record for
+graduation.
+** Update the Incubator
+link:http://incubator.apache.org/projects/index.html[status page] to denote the project as "graduating" when you commence,
+then as "graduated" when you are finished.
+The notes link:#unincubate[below] will assist.
+* Source
+** Post an announcement to the development list
+telling everyone that the repository is about
+to be moved
+** Post an announcement containing instructions
+for developers describing how to #svn switch# their workspaces
+** Update site, wikis, *pom.xml* and
+other resources to point to the new repository
+location.
+* Websites
+** Transfer the podling website
+*** Load the website into its new home. See link:http://www.apache.org/dev/#web[infra notes].
+** Update the *incubator/site-publish/.htaccess* entry to
+redirect traffic from the old URLs to
+the new. (svn location is at *http://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess*) -
+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.
+** Post an announcement to user and
+development lists
+** When using Maven: update *pom.xml* for the location
+of the website, as well as the place
+where the site plugin will deploy the
+web site (when applicable).
+* *(Top Level Projects Only)* Add Project To link:http://www.apache.org[www.apache.org]
+** Check out https://svn.apache.org/repos/asf/infrastructure/site/trunk
+** Patch #templates/blocks/projects.mdtext#
+** Commit, and if you have karma then link:https://cms.apache.org/www/publish[publish] the updated www site
+* Mailing lists
+** When your mail lists have been moved by infrastructure,
+post an announcement to your lists.
+** When using Maven: update *pom.xml* 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.
+** 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).
+** Update website: replace links to old archives with
+links to new ones and add new links to historic
+archives from incubation.
+** 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 link:http://www.apache.org/dev/committers.html#mail-moderate[this] and
+the link:http://www.ezmlm.org/[EZMLM]
+"Moderator's and Administrator's Manual".
+** Update mail addresses including:
+*** confluence commit messages (see adminstration documentation)
+*** issue tracking messages (see administration documentation)
+*** The chair should have karma to perform these tasks.
+** Double-check that all of your lists have sufficient active link:http://www.apache.org/dev/committers.html#mailing-list-moderators[moderators].
+* Issue Tracking
+** Check that the issue tracking system used by the podling reflects the project's new status.
+*Distribution mirrors
+** After you have a release at your new home (#/dist/${project}/# area), remove any distribution artefacts from your old #/dist/incubator/${project}/#
+area. Remember from the mirror guidelines that everything is automatically added to archive.apache.org anyway.
+
+==== Final Revision of Podling Incubation Records
+
+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 *incubator/trunk/content/projects/${project}.xml* file to show the project's status.
+* Update the podling summary metadata file,
+i.e. *incubator/trunk/content/podlings.xml* 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 *podlings.xml* 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.
+
+==== New Responsibilities
+===== Oversight
+
+During the stay in the Incubator, the
+link:/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29[Incubator PMC (IPMC)]
+was responsible to the
+link:/incubation/Roles_and_Responsibilities.html#board[Board]
+for oversight. A graduated project must now take
+responsibility for its own oversight.
+
+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.
+
+Help is still available but the
+appropriate bodies (infrastructure, community, legal
+and so on) should now be approached directly.
+
+===== Security
+
+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.
+
+Volunteers need to be found from the
+link:http://www.apache.org/foundation/how-it-works.html#structure[PMC]
+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.
+
+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.
+
+===== Stay In Touch
+
+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 link:lists.html#general+at+incubator.apache.org[general] list.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/ip_clearance.ad
----------------------------------------------------------------------
diff --git a/pages/guides/ip_clearance.ad b/pages/guides/ip_clearance.ad
new file mode 100644
index 0000000..f89ae00
--- /dev/null
+++ b/pages/guides/ip_clearance.ad
@@ -0,0 +1,43 @@
+//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.
+= IP Clearance
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+== Podling IP Clearance
+
+The board has charged the Incubator project with management of IP clearance for Apache.
+Instructions are link:http://incubator.apache.org/ip-clearance/index.html[here].
+
+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 link:http://www.apache.org/foundation/how-it-works.html#hats[two hats].
+This may be a little confusing at first.
+
+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.
+
+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.
+
+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.
http://git-wip-us.apache.org/repos/asf/incubator/blob/f59ab76b/pages/guides/lists.ad
----------------------------------------------------------------------
diff --git a/pages/guides/lists.ad b/pages/guides/lists.ad
new file mode 100644
index 0000000..e84cfd0
--- /dev/null
+++ b/pages/guides/lists.ad
@@ -0,0 +1,60 @@
+//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.
+= Incubator Mailing Lists Guide
+Apache Incubator PMC
+2002-10-16
+:jbake-type: guide
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+== Incubator Mailing Lists Guide
+
+=== Archive Policy
+Please read the link:http://www.apache.org/foundation/public-archives.html[Apache Public Forum Archive Policy] before sending email to any list.
+
+=== Incubator-wide Mailing Lists
+
+==== general at incubator.apache.org
+
+This is where general and public discussion of the Incubator takes place.
+- link:mailto:general-subscribe@incubator.apache.org[Subscribe]
+- link:mailto:general-unsubscribe@incubator.apache.org[Unsubscribe]
+- link:http://mail-archives.apache.org/mod_mbox/incubator-general/[Archives]
+
+==== cvs at incubator.apache.org
+
+This is the Incubator's "commits" list, named "cvs" for historical reasons. Changes made to the link:https://svn.apache.org/viewvc/incubator/public/trunk[Incubator codebase and website] and
+the link:http://wiki.apache.org/incubator[Incubator wiki] trigger automatic notifications to
+this list. Replies go to the link:general+at+incubator.apache.org[general list].
+
+- link:mailto:cvs-subscribe@incubator.apache.org[Subscribe]
+- link:mailto:cvs-unsubscribe@incubator.apache.org[Unsubscribe]
+- link:http://mail-archives.apache.org/mod_mbox/incubator-cvs/[Archives]
+
+=== Podling Mailing Lists
+
+Each podling under incubation has its own mailing lists, which should be easily discovered via the
+podling website or via the link:/projects/index.html[podling status pages].
+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 link:http://mail-archives.apache.org[archived].
+
+=== Foundation-wide Mailing Lists
+
+Many link:http://www.apache.org/foundation/mailinglists.html[ASF-wide lists] will
+also be of interest to Incubator participants. The
+link:http://www.apache.org/foundation/mailinglists.html#foundation-legal[legal discussion],
+link:http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure[infrastructure],
+and link:http://www.apache.org/foundation/mailinglists.html#foundation-community[community]
+lists are especially germane for PPMC members and release managers trying to develop their knowledge
+and stay current.
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org