You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by jo...@apache.org on 2016/12/26 15:02:26 UTC
svn commit: r1776060 - in
/incubator/public/branches/policy-rewrite-cleanup-122016/content: guides/
incubation/ stylesheets/
Author: johndament
Date: Mon Dec 26 15:02:26 2016
New Revision: 1776060
URL: http://svn.apache.org/viewvc?rev=1776060&view=rev
Log:
Updating incubator policy removing a lot of redundant information.
Removed:
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/committer.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/pmc.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/release-java.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/release.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/release_manifest.txt
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/releasemanagement.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/releasing-eclipse-update-site.xml
Modified:
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/branding.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/index.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/mentor.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/ppmc.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/sites.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/website.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Roles_and_Responsibilities.xml
incubator/public/branches/policy-rewrite-cleanup-122016/content/stylesheets/project.xml
Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/branding.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/branding.xml?rev=1776060&r1=1776059&r2=1776060&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/branding.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/branding.xml [utf-8] Mon Dec 26 15:02:26 2016
@@ -39,7 +39,7 @@ limitations under the License.
<p><b>Podling is in proposal/or pre-code-drop process</b>: 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
- Incubation, public mailing lists are announced, and code has been
+ Incubation, public mailing lists have been created, and code has been
submitted into our repositories.</p>
<p><b>Podling has been approved for incubation, podling has launched
Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/index.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/index.xml?rev=1776060&r1=1776059&r2=1776060&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/index.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/index.xml [utf-8] Mon Dec 26 15:02:26 2016
@@ -47,10 +47,8 @@ is normative and <code>MUST</code> be fo
</section>
<section id="podling_guides"><title>Podling Guides</title>
<ul>
- <li><a href="committer.html">Podling Committers</a></li>
<li><a href="ppmc.html">Podling PMC (PPMC)</a></li>
<li><a href="mentor.html">Podling Mentor</a></li>
- <li><a href="releasemanagement.html">Podling Releases</a></li>
<li><a href="branding.html">Podling Branding</a></li>
<li><a href="sites.html">Podling Websites</a></li>
<li><a href="names.html">A Suitable Name Search</a></li>
@@ -109,7 +107,7 @@ for full Apache projects. See
practices documented in these guides. The aim of this process is to improve
quality by ensuring that decisions are fully considered and to allow established
practices to evolve. Subjective quality is one factor taken to account by
- <a href='http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
+ <a href='&root-path;/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
members during votes.
</li>
</ul>
Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/mentor.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/mentor.xml?rev=1776060&r1=1776059&r2=1776060&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/mentor.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/mentor.xml [utf-8] Mon Dec 26 15:02:26 2016
@@ -53,6 +53,10 @@ It is informational not normative. Polic
</section>
<section id="Sending+in+an+Incubation+Report">
<title>Add to Incubation Summary file</title>
+ <p>Copy the <a href="../projects/incubation-status-template.html">incubation status template</a> to
+ content/projects/${project}.xml and add an entry to the
+ content/podlings.xml file. See
+ the full <a href="../guides/website.html">instructions</a> for updating the website.</p>
<p>
Add the podling to the podling summary file in
the "incubator" SVN at <code>content/podlings.xml</code>
@@ -75,10 +79,8 @@ It is informational not normative. Polic
and the list of months removed as well.
</p>
<p>
- The first report might be
- very short. However it is better that the Incubator PMC can help to
- guide through the early setup stages.
- For more details see the
+ The first report might be very short. However it is better that the Incubator PMC can help to
+ guide through the early setup stages. For more details see the
<a href="ppmc.html#Incubator+ASF+Board+Reports">PPMC Guide</a>.
</p>
</section>
@@ -220,7 +222,7 @@ It is informational not normative. Polic
<p>
If any Mentor has project-creation karma (in the issue tracking system to be used)
then they should execute.
- If no Mentor has the required karma then file an INFRA issue using the 'new jira project'
+ If no Mentor has the required karma then file an INFRA issue using the <a href="https://issues.apache.org/jira/servicedesk/customer/portal/1/create/6">'new jira project'</a>
type (not bug or request)
</p>
<p>
Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/ppmc.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/ppmc.xml?rev=1776060&r1=1776059&r2=1776060&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/ppmc.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/ppmc.xml [utf-8] Mon Dec 26 15:02:26 2016
@@ -218,13 +218,15 @@ limitations under the License.
in the PPMC. The PPMC should take an active role in watching
committers develop into community participants, identify those who
are participating at a community level, not just a technical one,
- and approach them with an offer of PPMC membership.</p>
+ and approach them with an offer of PPMC membership.</p>
<p>Any member of the PPMC can propose a new member of the PPMC. The
proposal should be discussed in private on the PPMC private alias,
with a subject line of [DISCUSS] Joe Bob PPMC membership. If there
is consensus that the proposed member is suitable, then there should
be a formal vote in the PPMC private alias, with the subject line of
- [VOTE] Joe Bob PPMC membership.
+ [VOTE] Joe Bob PPMC membership. If the podling is following the path of all committers
+ are also on the PPMC, they should explicitly state that the vote is for both
+ committer and PPMC member.
</p>
<p>If the vote is successful, the proposer
should send a message to the PPMC private alias, with
@@ -236,7 +238,7 @@ limitations under the License.
private@incubator.apache.org</a>) with a reference to
the vote result's message id of the following form:
</p><p>to: private@incubator.apache.org
- </p><p>subject: New member of Frizzle PPMC Joe Bob
+ </p><p>subject: [NOTICE] Joe Bob for Frizzle PPMC
</p><p>body: Joe Bob has been voted as a new member of the Frizzle PPMC.
</p><p>the vote thread is at:
</p><p>msgid: 23985678912386778989056789659048357@sponsoring.member.org
Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/sites.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/sites.xml?rev=1776060&r1=1776059&r2=1776060&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/sites.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/sites.xml [utf-8] Mon Dec 26 15:02:26 2016
@@ -14,185 +14,204 @@ limitations under the License.
-->
<!DOCTYPE document
-[
-<!ENTITY root-path '..'> <!-- The path to the incubator root -->
-]>
+ [
+ <!ENTITY root-path '..'> <!-- The path to the incubator root -->
+ ]>
<document>
- <properties>
- <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
- <title>Podling Web Site Guide</title>
- </properties>
- <body>
-
- <section>
- <title>Abstract</title>
- <p>
-Podlings need to build a community in Apache in order to be accepted
-as part of the Apache Software Foundation. One of the tools used to build
-a community is the web site.
- </p>
- </section>
-
- <section>
- <title>Podling Website Requirements</title>
- <p>
-Podlings are, by definition, not yet fully accepted as part of the
-Apache Software Foundation. Therefore, they are subject to additional
-constraints on their websites. These policies MUST be adhered to
-before Graduation is considered unless prior approval is obtained from
-the Incubator PMC.
- </p>
- <ul>
- <li>
-The published site for each podling must conform to the guidelines in
-<a href="&root-path;/guides/branding.html">Podling Branding/Publicity</a>.
- </li>
- <li>
-The sources for every podling site sources should be maintained in the podling's site SVN or git directory
- </li>
- <li>
-The published site for each podling should conform to this URL space:
-<code>http://podlingname.incubator.apache.org/</code>
- </li>
- <li>
-The staging site for each podling should conform to this URL space:
-<code>http://podlingname.staging.apache.org/</code>
- </li>
- <li>
-Every podling should maintain an incubation status file under:
-<code>http://incubator.apache.org/projects/podlingname.html</code>
- </li>
- <li>
-Eventual extra incubation documents should be filed under:
-<code>http://incubator.apache.org/projects/podlingname/**</code>
- </li>
- <li>
-The website lives in the following directory on people.apache.org:
- <code>/www/podlingname.apache.org/content/</code>
- </li>
- </ul>
- </section>
-
- <section>
- <title>Creating the Podling Website</title>
+ <properties>
+ <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org
+ Archives
+ </atom>
+ <title>Podling Web Site Guide</title>
+ </properties>
+ <body>
+
<section>
- <title>Creating A Good Podling Site</title>
+ <title>Abstract</title>
<p>
- Apache Project Web Sites typically include several standard pages.
- Each page is formatted with a navigation bar on the left and a project
- standard header that includes the Incubator graphic.
+ Podlings need to build a community in Apache in order to be accepted
+ as part of the Apache Software Foundation. One of the tools used to build
+ a community is the web site.
</p>
+ </section>
+
+ <section>
+ <title>Podling Website Requirements</title>
<p>
- The Web Site can be established during incubation, and migrated
- after incubation to a permanent place in the TLP home.
+ Podlings are, by definition, not yet fully accepted as part of the
+ Apache Software Foundation. Therefore, they are subject to additional
+ constraints on their websites. These policies MUST be adhered to
+ before Graduation is considered unless prior approval is obtained from
+ the Incubator PMC.
</p>
<ul>
<li>
- Project Home Page: the primary entry point to the site; contains
- project description, news, invitation to join the project.
- </li><li>
- License Page: usually, the Apache License 2.0
- </li><li>
- Downloads: many projects in incubation will release code,
- and this page describes them and has links to the download pages
- that redirect to Apache Mirror sites.
- </li><li>
- Documentation: this page describes the project documentation,
- including javadoc for Java projects; guides, tutorials, and links to
- external documentation.
- </li><li>
- Committers: a list of current committers on the project.
- </li><li>
- Mailing Lists: there are several mailing lists that the
- community might be interested in, and this page contains mailto: links
- that allow easy subscription (and unsubscription) to any of them.
- </li><li>
- FAQ: frequently asked questions are answered here.
- </li><li>
- Road Map: if the project has a vision of future community
- or development activities, the road map is published here.
- </li><li>
- Source Code: links to the browsable source repository and
- svn commands to check out the sources.
- </li><li>
- Coding Standards: the coding standards for submitted code
- by the community, along with a description of how strict the project
- intends to be.
- </li><li>
- Issue Tracking: links to the JIRA or other issue tracking
- tool, possibly including frequently used filters for issue lists.
- </li><li>
- Dependencies: other projects that this project depends on.
- </li><li>
- favicon: the project's icon in a format suitable for a browser's address bar. If absent, an Apache Feather will be displayed.
- </li></ul>
- </section>
-
- <section id="Tool">
- <title>Web Site Generation Tool</title>
- <p>
- The choice of tool used to generate the web site is left to
- the podling. If you already have a tool that you are comfortable
- with, you can continue to use it. If you do not, consider using
- the <a href="http://www.apache.org/dev/cmsref.html">Apache CMS</a>.
- </p>
- <p>
- Regardless of which tool you use, the web site should be maintained
- in the svn repository, and include the site generation tool as a binary
- file. This simplifies the process of site generation and enables changes
- to the site to be made by any committer. The generated site should also
- be checked into svn. This allows the generated site to be relocated
- to any part of the Apache site after incubation is complete.
- </p>
- <p>
- Since the site is independent of the code, it should exist high in
- the svn repository, e.g. parallel to the trunk of the source tree.
- </p>
+ The published site for each podling must conform to the guidelines in
+ <a href="&root-path;/guides/branding.html">Podling Branding/Publicity</a>.
+ </li>
+ <li>
+ The sources for every podling site sources should be maintained in the podling's site SVN or git
+ directory
+ </li>
+ <li>
+ The published site for each podling should conform to this URL space:
+ <code>http://podlingname.incubator.apache.org/</code>
+ </li>
+ <li>
+ The staging site (if using CMS) for each podling should conform to this URL space:
+ <code>http://podlingname.staging.apache.org/</code>
+ </li>
+ <li>
+ Every podling should maintain an incubation status file under:
+ <code>http://incubator.apache.org/projects/podlingname.html</code>
+ </li>
+ <li>
+ Eventual extra incubation documents should be filed under:
+ <code>http://incubator.apache.org/projects/podlingname/**</code>
+ </li>
+ </ul>
</section>
-
- <section><title>Publishing The Website</title>
- <p>
- <b>THIS IS VERY OUTDATED AND NEEDS FIXING</b><br/>
-The website is published by checking out the content from SVN into
-the directory <code>/www/incubator.apache.org/content/podlingname</code>
-(old way) or <code>/www/podlingname.apache.org</code> (new way) on
-<code>people.apache.org</code>. The particular SVN module used to
-store the website is a matter for the podling but it should be in SVN.
- </p>
- <p>
-People using Maven, Forrest, or any other tool still have
-to address the SVN publishing requirement that the
-infrastructure team has laid out. If that is done, then we
-just run "svn update" in that directory to load the site from
-SVN.
- </p>
- <p>
-The Mentors MUST add the information to the podling
-incubation status file, to describe the SVN module and the
-directory which holds the published site.
- </p>
+
+ <section>
+ <title>Creating the Podling Website</title>
+ <section>
+ <title>Creating A Good Podling Site</title>
+ <p>
+ Apache Project Web Sites typically include several standard pages.
+ Each page is formatted with a navigation bar on the left and a project
+ standard header that includes the Incubator graphic.
+ </p>
+ <p>
+ The Web Site can be established during incubation, and migrated
+ after incubation to a permanent place in the TLP home.
+ </p>
+ <ul>
+ <li>
+ Project Home Page: the primary entry point to the site; contains
+ project description, news, invitation to join the project.
+ </li>
+ <li>
+ License Page: usually, the Apache License 2.0
+ </li>
+ <li>
+ Downloads: many projects in incubation will release code,
+ and this page describes them and has links to the download pages
+ that redirect to Apache Mirror sites.
+ </li>
+ <li>
+ Documentation: this page describes the project documentation,
+ including javadoc for Java projects; guides, tutorials, and links to
+ external documentation.
+ </li>
+ <li>
+ Committers: a list of current committers on the project.
+ </li>
+ <li>
+ Mailing Lists: there are several mailing lists that the
+ community might be interested in, and this page contains mailto: links
+ that allow easy subscription (and unsubscription) to any of them.
+ </li>
+ <li>
+ FAQ: frequently asked questions are answered here.
+ </li>
+ <li>
+ Road Map: if the project has a vision of future community
+ or development activities, the road map is published here.
+ </li>
+ <li>
+ Source Code: links to the browsable source repository and
+ svn commands to check out the sources.
+ </li>
+ <li>
+ Coding Standards: the coding standards for submitted code
+ by the community, along with a description of how strict the project
+ intends to be.
+ </li>
+ <li>
+ Issue Tracking: links to the JIRA or other issue tracking
+ tool, possibly including frequently used filters for issue lists.
+ </li>
+ <li>
+ Dependencies: other projects that this project depends on.
+ </li>
+ <li>
+ favicon: the project's icon in a format suitable for a browser's address bar. If absent, an
+ Apache Feather will be displayed.
+ </li>
+ </ul>
+ </section>
+
+ <section id="Tool">
+ <title>Web Site Generation Tool</title>
+ <p>
+ The choice of tool used to generate the web site is left to
+ the podling. If you already have a tool that you are comfortable
+ with, you can continue to use it. If you do not, consider using
+ the <a href="http://www.apache.org/dev/cmsref.html">Apache CMS</a>.
+ </p>
+ <p>
+ Regardless of which tool you use, the web site should be maintained
+ in the svn repository, and include the site generation tool as a binary
+ file. This simplifies the process of site generation and enables changes
+ to the site to be made by any committer. The generated site should also
+ be checked into svn. This allows the generated site to be relocated
+ to any part of the Apache site after incubation is complete.
+ </p>
+ <p>
+ Since the site is independent of the code, it should exist high in
+ the svn repository, e.g. parallel to the trunk of the source tree.
+ </p>
+ </section>
+
+ <section>
+ <title>Publishing The Website</title>
+ <p>
+ <b>THIS IS VERY OUTDATED AND NEEDS FIXING</b>
+ <br/>
+ The website is published by checking out the content from SVN into
+ the directory
+ <code>/www/incubator.apache.org/content/podlingname</code>
+ (old way) or <code>/www/podlingname.apache.org</code> (new way) on
+ <code>people.apache.org</code>. The particular SVN module used to
+ store the website is a matter for the podling but it should be in SVN.
+ </p>
+ <p>
+ People using Maven, Forrest, or any other tool still have
+ to address the SVN publishing requirement that the
+ infrastructure team has laid out. If that is done, then we
+ just run "svn update" in that directory to load the site from
+ SVN.
+ </p>
+ <p>
+ The Mentors MUST add the information to the podling
+ incubation status file, to describe the SVN module and the
+ directory which holds the published site.
+ </p>
+ </section>
+
+ <section id='create-website-using-wiki'>
+ <title>Using A Wiki To Create Documentation</title>
+ <p>
+ Podlings may use a wiki to create documentation (including the website) providing that follow the
+ <a href='http://cwiki.apache.org/'>guidelines</a>. In particular, care must be taken to
+ ensure that access to the wiki used to create documentation that may be included in the project
+ release is restricted to only those with filed <a href='http://www.apache.org/licenses/'>individual
+ CLAs</a>. The PPMC MUST review all changes and ensure that
+ trust is not abused.
+ </p>
+ </section>
</section>
-
- <section id='create-website-using-wiki'><title>Using A Wiki To Create Documentation</title>
- <p>
- Podlings may use a wiki to create documentation (including the website) providing that follow the
- <a href='http://cwiki.apache.org/CWIKI/'>guidelines</a>. In particular, care must be taken to
- ensure that access to the wiki used to create documentation that may be included in the project
- release is restricted to only those with filed <a href='http://www.apache.org/licenses/'>individual CLAs</a>. The PPMC MUST review all changes and ensure that
- trust is not abused.
- </p>
+
+ <section>
+ <title>Main Incubator Website</title>
+
+ <p>Please read the
+ <a href="website.html">Incubator Website guide</a>
+ for more information about how the general Incubator site is laid out
+ and how to edit/regenerate the top-level documentation and a project's
+ status file.
+ </p>
</section>
- </section>
-
- <section>
- <title>Main Incubator Website</title>
-
- <p>Please read the <a href="website.html">Incubator Website guide</a>
- for more information about how the general Incubator site is laid out
- and how to edit/regenerate the top-level documentation and a project's
- status file.
- </p>
- </section>
- </body>
+ </body>
</document>
Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/website.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/website.xml?rev=1776060&r1=1776059&r2=1776060&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/website.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/guides/website.xml [utf-8] Mon Dec 26 15:02:26 2016
@@ -34,13 +34,11 @@ limitations under the License.
</p>
<p>The source to the Incubator website lives at:</p>
- <note><a href="http://svn.apache.org/repos/asf/incubator/public/trunk">
- http://svn.apache.org/repos/asf/incubator/public/trunk</a></note>
+ <note><a href="https://svn.apache.org/repos/asf/incubator/public/trunk">
+ https://svn.apache.org/repos/asf/incubator/public/trunk</a></note>
- <p>The production documents are kept in the "infra" SVN repository
- at https://svn.apache.org/repos/infra/websites/production/incubator.
- That directory is then managed by svnpubsub on the server
- to re-create the live website.</p>
+ <p>The incubator website is built using <a href="https://cms.apache.org">CMS</a>. After changes are made,
+ you must publish the website.</p>
</section>
<section id="Edit+the+content">
@@ -64,11 +62,9 @@ limitations under the License.
<section id="Checkout+the+Incubator+SVN">
<title>Checkout the Incubator SVN site</title>
<code>
-svn co http://svn.apache.org/repos/asf/incubator/public/trunk incubator<br />
+svn co https://svn.apache.org/repos/asf/incubator/public/trunk incubator<br />
cd incubator
</code>
- <note>If you are a committer and intending to commit your changes,
- please ensure you use https instead of http.</note>
</section>
<section id="Edit+the+source+documents">
<title>Edit the source documents</title>
@@ -78,62 +74,6 @@ cd incubator
<title>Add a new document</title>
<p>Add new documents in the content directories, then do 'svn add'.</p>
</section>
- <section id="Edit+your+project+status+page">
- <title>Edit your project status page</title>
- <p>The sources for the status pages are in
- <code>content/projects/*.xml</code></p>
- <section id='create-status-page'><title>Create Status Page</title>
- <ol>
- <li>
- Copy from the template
- <code>content/projects/incubation-status-template.xml</code> to
- <code>content/projects/${project}.xml</code> then <code>'svn add'</code>
- </li>
- <li>
- The copied template contains customization instructions. Follow them.
- </li>
- <li>
- Go through the template actions. Delete any which are not
- relevant and mark as completed any actions which are already
- done.
- </li>
- <li>
- Add an entry with status "current" to the podlings summary file at
- <code>content/podlings.xml</code> and ensure that the
- list of mentors is up-to-date.
- </li>
- <li>
- Do <code>'svn update'</code> to be sure you are up-to-date.
- </li>
- <li>
- Regenerate the documentation by running <code>'ant'</code> or <code>'build'</code> from the top-level.
- See more detail about this process in the following section. Note that
- there will be many output changes because a new entry has been added to
- the right-hand menu which is replicated on every page. The results wil
- be built to the <pre>target/site</pre> directory by default- please look them over,
- but do not add this directory nor its contents to svn!
- </li>
- <li>
- <code>svn commit</code> all of the source changes with a good message.
- </li>
- <li>
- Review your changes via the
- "<a href="lists.html#cvs+at+incubator.apache.org">commits</a>"
- mail list.
- </li>
- <li>
- Wait a minute or two for the CMS to build your changes, then publish them
- by visiting the <a href="https://cms.apache.org/incubator/publish">Publish site</a>
- page.
- See other <a href="http://www.apache.org/dev/project-site.html">notes</a>
- about this step.
- </li>
- </ol>
- <note>This status page is to be kept up to date regularly. This is NOT the same as the 'status report' which is a
- board report entry in the incubator wiki. You still need to follow your monthly/quarterly status reports
- </note>
- </section>
- </section>
</section>
<section id="Generating+the+top-level+website">
<title>Generating the top-level website</title>
@@ -142,13 +82,16 @@ cd incubator
<a href="lists.html#general+at+incubator.apache.org">general</a> list.</note>
<p>In the top-level "incubator" SVN directory, do 'ant'
to render the HTML files into the <pre>target/site</pre> directory.
+ You should review those changes before committing.
(If you don't have ant installed, you can run build.sh or build.bat
instead.) If the site built without errors, then do the usual
SVN stuff: 'svn status' 'svn add' 'svn diff' 'svn commit'.</p>
<p>
Review your changes via the
"<a href="lists.html#cvs+at+incubator.apache.org">commits</a>"
- mail list.
+ mailing list. This list will also have buildbot output from running
+ staging builds of the website. If you want to view your changes, you can go to
+ <a href="http://incubator.staging.apache.org">incubator.staging.apache.org</a>.
</p>
<p>To update the website, visit <a href="https://cms.apache.org/incubator/publish">Publish site</a>
and fill out the form. Don't forget to give the CMS build system time to build your changes!
Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Roles_and_Responsibilities.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Roles_and_Responsibilities.xml?rev=1776060&r1=1776059&r2=1776060&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Roles_and_Responsibilities.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Roles_and_Responsibilities.xml [utf-8] Mon Dec 26 15:02:26 2016
@@ -14,367 +14,387 @@ limitations under the License.
-->
<!DOCTYPE document
-[
-<!ENTITY root-path '..'> <!-- The path to the incubator root -->
-]>
+ [
+ <!ENTITY root-path '..'> <!-- The path to the incubator root -->
+ ]>
<document>
- <properties><!--
+ <properties><!--
<meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
-<!--
+ <!--
- <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+ <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
- <title>Roles_and_ Responsibilities
-</title>
- <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
- <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
- </properties>
- <body>
- <section id="Roles+and+Responsibilities">
- <title>Roles and Responsibilities
-</title>
- <p>This document describes the roles (including Sponsor, Contributor,
-Mentor) and provides an overview of the responsibilities of the
-different parties involved in an incubation process.
-</p>
- <section id='TOC'><title>Contents</title><toc/></section>
- <section id='board'><title>The Board</title>
- <p>
-The <a href='http://www.apache.org/foundation/board/'>Board Of Directors</a> of the
-<a href='http://www.apache.org/foundation/'>Apache Software Foundation</a> manages
-the organizational affairs of the Foundation.
-The board is elected by the
-<a href='http://www.apache.org/foundation/members.html'>Apache Members</a>.
- </p>
- <p>
-The Board delegates responsibility for incubation to the
-<a href='#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>.
- </p>
- <p>
-<a href='http://www.apache.org/foundation/board/'>Directors</a> are often active in the
-Incubator.
-<a href='http://www.apache.org/foundation/how-it-works.html#hats'>Conventionally</a>,
-unless indicated otherwise, individuals speak personally. So, a Director speaking
-without their Board hat is not stating policy but expressing a personal opinion.
- </p>
- <p>See also:
- </p>
- <ul>
- <li><a href='http://www.apache.org/foundation/how-it-works.html#management'>How Apache Works</a></li>
- </ul>
- </section>
- <section id="Incubator+Project+Management+Committee+%28PMC%29">
- <title>Incubator Project Management Committee (IPMC)
-</title>
-<p>The Incubator PMC
-[<a href="&root-path;/incubation/Incubation_Policy.html#Incubator+Project+Management+Committee+%28PMC%29">definition</a>]
-is responsible for:
-</p>
- <ul>
- <li>acceptance and oversight of candidate projects submitted or proposed
-to become part of the Foundation;
-</li>
- <li>providing guidance and ensuring that sub-projects under it's purview
-develop products according to the Foundation's philosophy and
-guidelines for collaborative development;
-</li>
- <li>providing a repository for the storage of incubation history and
-information;
-</li>
- <li>assisting a Podling's Mentor in discharging her/his duties;
-</li>
- <li>regularly evaluating projects under its purview for the purposes of
-recommending to the Sponsor whether the project should:
-</li>
- <li style="list-style: none">
- <ul>
- <li>graduate from incubation;
-</li>
- <li>continue to receive guidance and support within the Incubator; or
-</li>
- <li>be terminated.
-</li>
- </ul>
- </li>
- </ul>
- <p>To enable effective management of the process of incubation from the
-point of view of the PMC and from the point of view of members of a
-project under incubation, a set of policies and procedures are
-described below that identify roles and responsibilities of
-participants throughout the incubation lifecycle.
-</p>
- <p>A project going through the Incubator will therefore be required to
-regularly report to the Incubator PMC. This will help the PMC in its
-role of reviewing the status of a project under incubation.
-</p>
- <p>Finally, the Incubator PMC is the ASF body with the greatest level of
-expertise and experience in the Incubation process. They provide a
-store of knowledge that can be called on by the Mentor or a Podling
-during (or even after) the incubation process. In cases where an
-Incubation is particularly large, or where the Incubator PMC
-otherwise feels the Mentor needs additional assistance, the Incubator
-PMC may choose to provide an experienced Mentor to assist the main
-Mentor in discharging their duty.
-</p>
- <p>Individuals may be nominated to join the IPMC after a vote which
-passes with more than 3/4 of those voting. Additionally, any Member of the
-Apache Software Foundation may join the IPMC by request.
-</p>
- <p>See also:
- </p>
- <ul>
- <li><a href='http://www.apache.org/foundation/how-it-works.html#management'>How Apache Works</a></li>
- </ul>
- </section>
- <section id="Chair+of+the+Incubator+PMC">
- <title>Chair of the Incubator PMC
-</title>
- <p>The person appointed by the <a href='#board'>Board</a> to have primary
-responsibility for oversight of the Incubator Project, its policies,
-and policy implementation.
-</p>
- </section>
- <section id="Candidate">
- <title>Candidate
-</title>
- <p>A Candidate [<a href='Incubation_Policy.html#Candidate'>definition</a>]
-is a project proposed for incubation. A Candidate
-shall meet the following minimum criteria:
-</p>
- <ul>
- <li>affiliated with a named *Champion* (an ASF Member or Officer; see
-below)
-</li>
- </ul>
- <p>Optionally, a candidate may:
-</p>
- <ul>
- <li>declare an affiliation with an existing Apache Project in which case
-the project will become the *Sponsor*;
-</li>
- <li>specify requirements that may be anticipated during incubation; and/or
-</li>
- <li>provide a summary of the project relationship/dependencies (existing
-or planned with existing Apache Projects/Products).
-</li>
- </ul>
- <p>Naturally, projects will need more than this in order to graduate from
-incubation status.
-</p>
- <p>A candidate project compliant with the above criteria may be proposed
-by the Champion to the Sponsor for acceptance as a Podling.
-Acceptance of a candidate shall be subject to the formal voting
-method of the Sponsor. Should that vote be accepted, the Sponsor will
-request that the Incubator PMC accept the candidate as a Podling
-under incubation. The Sponsor shall assign a Mentor, who shall be
-granted membership of the Incubator PMC for the duration of the
-incubation process.
-</p>
- </section>
- <section id="Champion">
- <title>Champion</title>
- <p>
- A candidate project shall be sponsored by an
- <a href="http://www.apache.org/foundation/index.html">Officer</a> or
- <a href="http://www.apache.org/foundation/members.html">Member</a>
- of the Foundation. The Champion assists the candidate on their
- initial submission to a Sponsor. While private conversations are not
- generally encouraged within the Apache community, the Champion's
- relationship with the Candidate should allow for this in order to
- educate the Candidate about the Apache Way and prepare the project
- for the questions and issues likely to be raised by the community.
- </p>
- <p>
- Before incubation begins, the Champion is expected to:
- <ul>
- <li>help with any process/ASF related hurdles before the Candidate enters incubation</li>
- <li>help find the right people in the ASF to speak with</li>
- <li>help to find Mentors</li>
- <li>drive the process of entering the Incubator, leading to a vote to accept the proposed podling</li>
- </ul>
- </p>
- </section>
- <section id="Sponsor">
- <title>Sponsor</title>
- <p>
- The Sponsor [<a href="&root-path;/incubation/Incubator_Policy.html#Sponsor">definition</a>]
- is the entity within the ASF that makes the determination
- that a candidate would make a worthy addition to the ASF, and agrees
- to take on the candidate in question (or in the case of the Incubator
- PMC, assist it in finding a home) should it complete the incubation
- process.
- </p>
- <p>A Sponsor will be one of:</p>
- <ul>
- <li>
- A Top Level Project within the ASF. In this case, the project in
- question has agreed that the candidate is a good fit for their
- project, and will take on the candidate as a sub-project upon
- successful completion of Incubation.
- </li>
- <li>
- The Incubator PMC. In this case, the Incubator PMC agrees that the
- project in question will make a good addition to the ASF, but there
- is no clear "owner" of the candidate should it successfully complete
- incubation. An incubation exit requirement for such candidates will
- be the identification (and successfuly lobbying) of an "owner" entity
- - either the <a href='#board'>Board</a> (and the candidate will be a TLP) or another
- project. In most cases, the Incubator PMC is the correct Sponsor (Candidates should discuss this
- with their Champion).
- </li>
- </ul>
- <p>
- Note that a Sponsor is more than just a final resting place for a
- candidate that successfully completes incubation. The Sponsor, by
- taking on a candidate, is indicating that they believe the candidate
- will make a worthy addition to the ASF, and takes responsibility for
- assisting the podling through the Incubation process. The Sponsor is
- therefore expected to be actively involved in the incubation process
- and assist where necessary, giving the podling the best possible
- chance of success. In addition, an entity that is a Top Level Project
- should be involved in the Candidate's incubation in order to educate
- the Candidate about practices that are specific to that TLP and about
- other relevant projects within the TLP.
- </p>
- <p>
- However, while the Sponsor is expected to be actively involved, it is
- formally representated by the Mentors. The Mentors are the individuals
- accountable to the Incubator PMC for ensuring the incubation process
- is correctly followed. In cases where the Mentors are not fulfilling
- their responsibilities, the Sponsor (in particular its Chair) will be
- expected to remedy the situation.
- </p>
- <section id="Responsibilities+of+the+Sponsor">
- <title>Responsibilities of the Sponsor
-</title>
- <ul>
- <li>to provide initial approval for a Canidate to be accepted as a Podling
-</li>
- <li>to nominate Mentors for the incubation process
-</li>
- </ul>
+ <title>Roles and Responsibilities
+ </title>
+ <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org
+ Archives
+ </atom>
+ <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+ </properties>
+ <body>
+ <section id="Roles+and+Responsibilities">
+ <title>Roles and Responsibilities
+ </title>
+ <p>This document describes the roles (including Sponsor, Contributor,
+ Mentor) and provides an overview of the responsibilities of the
+ different parties involved in an incubation process.
+ </p>
+ <section id='TOC'>
+ <title>Contents</title>
+ <toc/>
+ </section>
+ <section id='board'>
+ <title>The Board</title>
+ <p>
+ The <a href='http://www.apache.org/foundation/board/'>Board Of Directors</a> of the
+ <a href='http://www.apache.org/foundation/'>Apache Software Foundation</a>
+ manages
+ the organizational affairs of the Foundation.
+ The board is elected by the
+ <a href='http://www.apache.org/foundation/members.html'>Apache Members</a>.
+ </p>
+ <p>
+ The Board delegates responsibility for incubation to the
+ <a href='#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>.
+ </p>
+ <p>
+ <a href='http://www.apache.org/foundation/board/'>Directors</a>
+ are often active in the
+ Incubator.
+ <a href='http://www.apache.org/foundation/how-it-works.html#hats'>Conventionally</a>,
+ unless indicated otherwise, individuals speak personally. So, a Director speaking
+ without their Board hat is not stating policy but expressing a personal opinion.
+ </p>
+ <p>See also:
+ </p>
+ <ul>
+ <li>
+ <a href='http://www.apache.org/foundation/how-it-works.html#management'>How Apache Works</a>
+ </li>
+ </ul>
+ </section>
+ <section id="Incubator+Project+Management+Committee+%28PMC%29">
+ <title>Incubator Project Management Committee (IPMC)
+ </title>
+ <p>The Incubator PMC is responsible for:
+ </p>
+ <ul>
+ <li>
+ The Project Management Committee is responsible to the Board for administering
+ the Incubator Project in the manner specified in the founding
+ <a href='http://incubator.apache.org/official/resolution.html'>resolution</a>.
+ </li>
+ <li>acceptance and oversight of candidate projects submitted or proposed
+ to become part of the Foundation;
+ </li>
+ <li>providing guidance and ensuring that sub-projects under it's purview
+ develop products according to the Foundation's philosophy and
+ guidelines for collaborative development;
+ </li>
+ <li>providing a repository for the storage of incubation history and
+ information;
+ </li>
+ <li>assisting a Podling's Mentor in discharging her/his duties;
+ </li>
+ <li>regularly evaluating projects under its purview for the purposes of
+ recommending to the Sponsor whether the project should:
+ </li>
+ <li style="list-style: none">
+ <ul>
+ <li>graduate from incubation;
+ </li>
+ <li>continue to receive guidance and support within the Incubator; or
+ </li>
+ <li>be terminated.
+ </li>
+ </ul>
+ </li>
+ </ul>
+ <p>To enable effective management of the process of incubation from the
+ point of view of the PMC and from the point of view of members of a
+ project under incubation, a set of policies and procedures are
+ described below that identify roles and responsibilities of
+ participants throughout the incubation lifecycle.
+ </p>
+ <p>A project going through the Incubator will therefore be required to
+ regularly report to the Incubator PMC. This will help the PMC in its
+ role of reviewing the status of a project under incubation.
+ </p>
+ <p>Finally, the Incubator PMC is the ASF body with the greatest level of
+ expertise and experience in the Incubation process. They provide a
+ store of knowledge that can be called on by the Mentor or a Podling
+ during (or even after) the incubation process. In cases where an
+ Incubation is particularly large, or where the Incubator PMC
+ otherwise feels the Mentor needs additional assistance, the Incubator
+ PMC may choose to provide an experienced Mentor to assist the main
+ Mentor in discharging their duty.
+ </p>
+ <p>Individuals may be nominated to join the IPMC after a vote which
+ passes with more than 3/4 of those voting. Additionally, any Member of the
+ Apache Software Foundation may join the IPMC by request.
+ </p>
+ <p>See also:
+ </p>
+ <ul>
+ <li>
+ <a href='http://www.apache.org/foundation/how-it-works.html#management'>How Apache Works</a>
+ </li>
+ </ul>
+ </section>
+ <section id="Chair+of+the+Incubator+PMC">
+ <title>Chair of the Incubator PMC
+ </title>
+ <p>The person appointed by the <a href='#board'>Board</a> to have primary
+ responsibility for oversight of the Incubator Project, its policies,
+ and policy implementation.
+ </p>
+ </section>
+ <section id="Candidate">
+ <title>Candidate
+ </title>
+ <p>A Candidate is a project proposed for incubation. A Candidate
+ shall meet the following minimum criteria:
+ </p>
+ <ul>
+ <li>affiliated with a named *Champion* (an ASF Member or Officer; see
+ below)
+ </li>
+ </ul>
+ <p>Optionally, a candidate may:
+ </p>
+ <ul>
+ <li>declare an affiliation with an existing Apache Project in which case
+ the project will become the *Sponsor*;
+ </li>
+ <li>specify requirements that may be anticipated during incubation; and/or
+ </li>
+ <li>provide a summary of the project relationship/dependencies (existing
+ or planned with existing Apache Projects/Products).
+ </li>
+ </ul>
+ <p>Naturally, projects will need more than this in order to graduate from
+ incubation status.
+ </p>
+ <p>A candidate project compliant with the above criteria may be proposed
+ by the Champion to the Sponsor for acceptance as a Podling.
+ Acceptance of a candidate shall be subject to the formal voting
+ method of the Sponsor. Should that vote be accepted, the Sponsor will
+ request that the Incubator PMC accept the candidate as a Podling
+ under incubation. The Sponsor shall assign a Mentor, who shall be
+ granted membership of the Incubator PMC for the duration of the
+ incubation process.
+ </p>
+ </section>
+ <section id="Champion">
+ <title>Champion</title>
+ <p>
+ A candidate project shall be sponsored by an
+ <a href="http://www.apache.org/foundation/index.html">Officer</a>
+ or
+ <a href="http://www.apache.org/foundation/members.html">Member</a>
+ of the Foundation. The Champion assists the candidate on their
+ initial submission to a Sponsor. While private conversations are not
+ generally encouraged within the Apache community, the Champion's
+ relationship with the Candidate should allow for this in order to
+ educate the Candidate about the Apache Way and prepare the project
+ for the questions and issues likely to be raised by the community.
+ </p>
+ <p>
+ Before incubation begins, the Champion is expected to:
+ <ul>
+ <li>help with any process/ASF related hurdles before the Candidate enters incubation</li>
+ <li>help find the right people in the ASF to speak with</li>
+ <li>help to find Mentors</li>
+ <li>drive the process of entering the Incubator, leading to a vote to accept the proposed
+ podling
+ </li>
+ </ul>
+ </p>
+ <p>
+ While the role of the champion is intended to be prior to incubation, it is normal for your champion
+ to move on and become one of your mentors (though it is not required).
+ </p>
+ </section>
+ <section id="Sponsor">
+ <title>Sponsor</title>
+ <p>
+ The Sponsor is the entity within the ASF that makes the determination
+ that a candidate would make a worthy addition to the ASF, and agrees
+ to take on the candidate in question (or in the case of the Incubator
+ PMC, assist it in finding a home) should it complete the incubation
+ process.
+ </p>
+ <p>A Sponsor will be one of:</p>
+ <ul>
+ <li>
+ A Top Level Project within the ASF. In this case, the project in
+ question has agreed that the candidate is a good fit for their
+ project, and will take on the candidate as a sub-project upon
+ successful completion of Incubation.
+ </li>
+ <li>
+ The Incubator PMC. In this case, the Incubator PMC agrees that the
+ project in question will make a good addition to the ASF, but there
+ is no clear "owner" of the candidate should it successfully complete
+ incubation. An incubation exit requirement for such candidates will
+ be the identification (and successfuly lobbying) of an "owner" entity
+ - either the <a href='#board'>Board</a> (and the candidate will be a TLP) or another
+ project. In most cases, the Incubator PMC is the correct Sponsor (Candidates should discuss this
+ with their Champion).
+ </li>
+ </ul>
+ <p>
+ Note that a Sponsor is more than just a final resting place for a
+ candidate that successfully completes incubation. The Sponsor, by
+ taking on a candidate, is indicating that they believe the candidate
+ will make a worthy addition to the ASF, and takes responsibility for
+ assisting the podling through the Incubation process. The Sponsor is
+ therefore expected to be actively involved in the incubation process
+ and assist where necessary, giving the podling the best possible
+ chance of success. In addition, an entity that is a Top Level Project
+ should be involved in the Candidate's incubation in order to educate
+ the Candidate about practices that are specific to that TLP and about
+ other relevant projects within the TLP.
+ </p>
+ <p>
+ However, while the Sponsor is expected to be actively involved, it is
+ formally representated by the Mentors. The Mentors are the individuals
+ accountable to the Incubator PMC for ensuring the incubation process
+ is correctly followed. In cases where the Mentors are not fulfilling
+ their responsibilities, the Sponsor (in particular its Chair) will be
+ expected to remedy the situation.
+ </p>
+ <section id="Responsibilities+of+the+Sponsor">
+ <title>Responsibilities of the Sponsor
+ </title>
+ <ul>
+ <li>to provide initial approval for a Canidate to be accepted as a Podling
+ </li>
+ <li>to nominate Mentors for the incubation process
+ </li>
+ </ul>
+ </section>
+ </section>
+ <section id="Mentor">
+ <title>Mentor
+ </title>
+ <p>Mentors are chosen by the Sponsor and the Champion to actively monitor the
+ podling, guide the podling in
+ <a href="http://apache.org/foundation/how-it-works.html">the Apache Way</a>,
+ and report its status
+ to the Sponsor and the Incubator PMC. All Mentors must be members of the
+ Incubator PMC. A Mentor has the following responsibilities
+ toward the Incubator PMC, the Sponsor, and the community of the assigned
+ Podling.
+ </p>
+ <section id="Responsibilities+toward+Podling+Community">
+ <title>Responsibilities toward Podling Community
+ </title>
+ <ul>
+ <li>to ensure that Incubator PMC decisions and/or issue are dealt with in
+ a timely manner and ensure that decisions or resolutions affecting
+ the Podling are communicated promptly and expeditiously;
+ </li>
+ <li>to represent the interests of the Podling on the Incubator PMC;
+ </li>
+ <li>to liaise between the ASF Secretary and the Podling on matters
+ concerning CLA submission and acknowledgments;
+ </li>
+ <li>to liaise between the ASF Infrastructure team and the Podling on
+ matters concerning infrastructure support (mailing lists, CVS
+ establishment, account establishment, etc.);
+ </li>
+ <li>to assist the Podling on matters concerning the resolution of license
+ transfers, copyright assignments, and/or software grants where
+ applicable; and
+ </li>
+ <li>to provide where and as appropriate, guidance on matters concerning
+ Apache policies and practices - including the establishment of its
+ internal steering committee.
+ </li>
+ </ul>
+ </section>
+ <section id="Responsibilities+toward+the+Incubator+PMC">
+ <title>Responsibilities toward the Incubator PMC
+ </title>
+ <ul>
+ <li>monitoring the Podling through the incubation process;
+ </li>
+ <li>evaluating the compliance of the Podling with Incubator PMC policies
+ and procedures;
+ </li>
+ <li>assessment of the Podling status with respect to continuation/exit
+ strategy;
+ </li>
+ <li>to notify the Incubator PMC and Sponsor of the completion of
+ administrative actions; and
+ </li>
+ <li>to provide updates to the Incubator PMC and Sponsor on the status of
+ license grants (where and as appropriate) and other relevant legal
+ information pertaining to the Podling.
+ </li>
+ </ul>
+ </section>
+ <section id="Responsibilities+toward+the+Sponsor">
+ <title>Responsibilities toward the Sponsor</title>
+ <ul>
+ <li>provide status to the Sponsor as to the progress
+ of the podling
+ </li>
+ </ul>
+ </section>
+ </section>
+ <section id="Committers">
+ <title>Committers
+ </title>
+ <p>The candidate shall declare an initial set of committers. On
+ acceptance of a candidate project, the assigned Mentors shall be given
+ access to the Podling's repository for the duration of the
+ incubation process. This is to allow the Mentors to perform their
+ incubation duties, and is for administrative purposes only. To be
+ given full committer privileges, such as the right to add new code to
+ the repository, the Mentors must earn them as would any other
+ potential new committer. In some cases, the Mentors may be part of the
+ initial set of declared committers, but this is not a requirement of
+ the Incubation process.
+ </p>
+ <p>
+ Committers should also be aware of <a href="https://www.apache.org/dev/new-committers-guide.html">The Guide for New Committers</a>.
+ </p>
+ <p>In association with its Mentor and Champion, a Podling community is
+ largely free to get on with the stuff they want to do (code,
+ architecture, product, solutions, etc.) with minimal disruption
+ related to the incubator process.
+ </p>
+ <p>However, you need to make sure of a number of things:
+ </p>
+ <ul>
+ <li>keep your Mentors informed - they are reporting to the PMC and
+ generally speaking "no news is bad news". Of course, conducting
+ business on the project's mailing lists is one important way to do
+ this.
+ </li>
+ <li>actively seek and recruit committers to your project - preferably
+ linking you with existing Apache communities
+ </li>
+ <li>make sure your decision making process is visible and accountable
+ </li>
+ </ul>
+ <p>These activities are not unique to projects in the Incubator. For
+ example, existing Apache Projects have regular reports made by their
+ PMC Chair to the <a href='#board'>Board</a>.
+ </p>
+ <p>During the incubation, the committers will be expected to show how,
+ as a group, they are upholding the ideals of the Apache community. In
+ particular, as the Podling evolves it is anticipated that the Podling
+ will establish procedures for the introduction of new committers
+ through a process consistent with established Apache practices. If
+ you are aiming for TLP status you may also want to start on drafting
+ the policy and procedures you aim to put in place once accepted.
+ </p>
+ </section>
</section>
- </section>
- <section id="Mentor">
- <title>Mentor
-</title>
- <p>Mentors are chosen by the Sponsor to actively monitor the
-podling, guide the podling in
-<a href="http://apache.org/foundation/how-it-works.html">the Apache Way</a>,
-and report its status
-to the Sponsor and the Incubator PMC. All Mentors must be members of the
-Incubator PMC. A Mentor has the following responsibilities
-toward the Incubator PMC, the Sponsor, and the community of the assigned
-Podling.
-</p>
- <section id="Responsibilities+toward+Podling+Community">
- <title>Responsibilities toward Podling Community
-</title>
- <ul>
- <li>to ensure that Incubator PMC decisions and/or issue are dealt with in
-a timely manner and ensure that decisions or resolutions affecting
-the Podling are communicated promptly and expeditiously;
-</li>
- <li>to represent the interests of the Podling on the Incubator PMC;
-</li>
- <li>to liaise between the ASF Secretary and the Podling on matters
-concerning CLA submission and acknowledgments;
-</li>
- <li>to liaise between the ASF Infrastructure team and the Podling on
-matters concerning infrastructure support (mailing lists, CVS
-establishment, account establishment, etc.);
-</li>
- <li>to assist the Podling on matters concerning the resolution of license
-transfers, copyright assignments, and/or software grants where
-applicable; and
-</li>
- <li>to provide where and as appropriate, guidance on matters concerning
-Apache policies and practices - including the establishment of its
-internal steering committee.
-</li>
- </ul>
- </section>
- <section id="Responsibilities+toward+the+Incubator+PMC">
- <title>Responsibilities toward the Incubator PMC
-</title>
- <ul>
- <li>monitoring the Podling through the incubation process;
-</li>
- <li>evaluating the compliance of the Podling with Incubator PMC policies
-and procedures;
-</li>
- <li>assessment of the Podling status with respect to continuation/exit
-strategy;
-</li>
- <li>to notify the Incubator PMC and Sponsor of the completion of
-administrative actions; and
-</li>
- <li>to provide updates to the Incubator PMC and Sponsor on the status of
-license grants (where and as appropriate) and other relevant legal
-information pertaining to the Podling.
-</li>
- </ul>
- </section>
- <section id="Responsibilities+toward+the+Sponsor">
- <title>Responsibilities toward the Sponsor</title>
- <ul>
- <li>provide status to the Sponsor as to the progress
-of the podling
-</li>
- </ul>
- </section>
- </section>
- <section id="Committers">
- <title>Committers
-</title>
- <p>The candidate shall declare an initial set of committers. On
-acceptance of a candidate project, the assigned Mentors shall be given
-access to the Podling's repository for the duration of the
-incubation process. This is to allow the Mentors to perform their
-incubation duties, and is for administrative purposes only. To be
-given full committer privileges, such as the right to add new code to
-the repository, the Mentors must earn them as would any other
-potential new committer. In some cases, the Mentors may be part of the
-initial set of declared committers, but this is not a requirement of
-the Incubation process.
-</p>
- <p>In association with its Mentor and Champion, a Podling community is
-largely free to get on with the stuff they want to do (code,
-architecture, product, solutions, etc.) with minimal disruption
-related to the incubator process.
-</p>
- <p>However, you need to make sure of a number of things:
-</p>
- <ul>
- <li>keep your Mentors informed - they are reporting to the PMC and
-generally speaking "no news is bad news". Of course, conducting
-business on the project's mailing lists is one important way to do
-this.
-</li>
- <li>make sure your Champion is continuously in-the-loop and has the
-latest and greatest information about your project
-</li>
- <li>actively seek and recruit committers to your project - preferably
-linking you with existing Apache communities
-</li>
- <li>make sure your decision making process is visible and accountable
-</li>
- </ul>
- <p>These activities are not unique to projects in the Incubator. For
-example, existing Apache Projects have regular reports made by their
-PMC Chair to the <a href='#board'>Board</a>.
-</p>
- <p>During the incubation, the committers will be expected to show how,
-as a group, they are upholding the ideals of the Apache community. In
-particular, as the Podling evolves it is anticipated that the Podling
-will establish procedures for the introduction of new committers
-through a process consistent with established Apache practices. If
-you are aiming for TLP status you may also want to start on drafting
-the policy and procedures you aim to put in place once accepted.
-</p>
- </section>
- </section>
- </body>
+ </body>
</document>
Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/stylesheets/project.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/stylesheets/project.xml?rev=1776060&r1=1776059&r2=1776060&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/stylesheets/project.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/stylesheets/project.xml [utf-8] Mon Dec 26 15:02:26 2016
@@ -51,10 +51,8 @@ limitations under the License.
</projects>
<projects><title>Podling Guides</title>
- <li><a href="/guides/committer.html">Podling Committers</a></li>
<li><a href="/guides/ppmc.html">Podling PMC (PPMC)</a></li>
<li><a href="/guides/mentor.html">Podling Mentor</a></li>
- <li><a href="/guides/releasemanagement.html">Podling Releases</a></li>
<li><a href="/guides/branding.html">Podling Branding/Publicity</a></li>
<li><a href="/guides/sites.html">Podling Websites</a></li>
<li><a href="/guides/graduation.html">Graduation</a></li>
@@ -63,8 +61,6 @@ limitations under the License.
<projects><title>Other Guides</title>
<li><a href="/guides/participation.html">Participation</a></li>
- <li><a href="/faq.html">General FAQ</a></li>
- <li><a href="/guides/pmc.html">Incubator PMC (IPMC)</a></li>
<li><a href="/guides/chair.html">IPMC Chair</a></li>
<li><a href="/guides/lists.html">Mailing Lists</a></li>
<li><a href="/guides/website.html">Incubator Website</a></li>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org