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/31 17:09:02 UTC
[3/4] incubator git commit: Resyncing git mirror from svn.
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/draft-simple-release-management.xml
----------------------------------------------------------------------
diff --git a/content/guides/draft-simple-release-management.xml b/content/guides/draft-simple-release-management.xml
new file mode 100644
index 0000000..52f8a8c
--- /dev/null
+++ b/content/guides/draft-simple-release-management.xml
@@ -0,0 +1,99 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one
+ ~ or more contributor license agreements. See the NOTICE file
+ ~ distributed with this work for additional information
+ ~ regarding copyright ownership. The ASF licenses this file
+ ~ to you under the Apache License, Version 2.0 (the
+ ~ "License"); you may not use this file except in compliance
+ ~ with the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing,
+ ~ software distributed under the License is distributed on an
+ ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~ KIND, either express or implied. See the License for the
+ ~ specific language governing permissions and limitations
+ ~ under the License.
+ -->
+
+<!--
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<!DOCTYPE document
+ [
+ <!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>Apache Incubator: Release Management (DRAFT)</title>
+ </properties>
+ <body>
+ <section id='intro'>
+ <title>A Guide To Release Management During Incubation (DRAFT)</title>
+ <section id='TOC'>
+ <title>Contents</title>
+ <toc/>
+ </section>
+ <section id="status">
+ <title>Status - DRAFT</title>
+ <p>
+ This document is under active development. This is a first
+ draft intended to allow public review.
+ </p>
+ </section>
+
+ <section id="release-expectations">
+ <title>What goes into a release</title>
+ <p>
+ A podling should begin to familiarize itself with ASF policies for releases. Those policies can be found at <a href="http://www.apache.org/dev/#releases">http://www.apache.org/dev/#releases</a>.
+ </p>
+ <p>
+ It is well understood that one of the goals of incubation is to help a podling understand how to
+ build <a href="http://www.apache.org/dev/#releases">ASF compliant releases</a>. This is why its
+ mandatory to have at least 3 +1 votes from
+ <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC members</a>
+ review the releases (this should include your <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Mentor">mentors</a> but is not mandatory)
+ for accuracy in compliance with the ASF and <a href="&root-path;/incubation/Incubation_Policy.html#Releases">Incubator policies</a>.
+ The podling community, of course, needs to be fully engaged in review process as well. Anybody reviewing
+ the releases will provide the release manager and IPMC members with information about what is wrong
+ with the release. The severity of the issues and whether they are blocking or not may be discussed
+ but the ultimate guidance on where podling releases may get additional flexibility belongs to the mentors and IPMC members.
+ </p>
+ </section>
+ <section id="podling-constraints">
+ <title>Podling Constraints</title>
+ <p>
+ The <a href="&root-path;/incubation/Incubation_Policy.html#Releases">Incubator policies</a> apply two additional constraints to podlings for their releases. They are repeated here for clarity only.
+ <ul>
+ <li>Release artifacts must include <em>incubating</em> in the final file name</li>
+ <li>Release artifacts must include a <a href="&root-path;/guides/branding.html#disclaimers">disclaimer</a> within the release artifact(s) as noted</li>
+ </ul>
+ </p>
+ <p>
+ In order for a podling to receive full permission from the IPMC to execute the release, the release
+ vote must be held on the <a href="&root-path;/guides/lists.html#general+at+incubator.apache.org">incubator general list</a>
+ and pass based on the <a href="http://apache.org/foundation/voting.html#ReleaseVotes">standard Package Release voting rules</a>.
+ Only Incubator PMC votes are binding, but all are encouraged to vote.
+ </p>
+ </section>
+ </section>
+ </body>
+</document>
+
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/graduation.xml
----------------------------------------------------------------------
diff --git a/content/guides/graduation.xml b/content/guides/graduation.xml
index 78ab5d0..b985ae6 100644
--- a/content/guides/graduation.xml
+++ b/content/guides/graduation.xml
@@ -42,8 +42,8 @@
graduation.
</p>
<p>
- This is just a guide. Policy is stated
- <a href='http://incubator.apache.org/incubation/Incubation_Policy.html'>here</a>.
+ <b>This is just a guide. Policy is stated
+ <a href='https://incubator.apache.org/incubation/Incubation_Policy.html'>here</a>.</b>
</p>
<p>
Help to improve the system by posting a patch for
@@ -176,16 +176,14 @@
</li>
<li>
- Demonstrate <a href='#community'>community
- readiness</a>
+ Demonstrate <a href='#community'>community readiness</a>
</li>
<li>
Ensure <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a> and <a
href="&root-path;/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
- have no <a href='#notes-issues'>remaining
- issues</a>
+ have no <a href='#notes-issues'>remaining issues</a>
</li>
</ul>
@@ -423,8 +421,11 @@
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.
+ resolution that are not covered.
</p>
+ <p>
+ Podlings who are unsure if they are ready to graduate may want to consider completing the <a href="http://community.apache.org/apache-way/apache-project-maturity-model.html" target="_new">Apache Project Maturity Model</a>. You may find this to be a useful guide when looking at various factors in your podling's community.
+ </p>
</section>
</section>
<section id="process">
@@ -846,7 +847,7 @@ Resolution draft:
<li>Subscribe to the <code>board</code> mailing list</li>
<li>Subscribe to the <code>infrastructure</code> mailing list</li>
<li>Ensure that they have been added to
- <a href='http://people.apache.org/committers-by-project.html#pmc-chairs'
+ <a href='https://people.apache.org/phonebook.html?service=pmc-chairs'
>the PMC chairs group (pmc-chairs) in LDAP</a>.
The ASF Secretary should do this without any action on the part
of the new chair. As with above, if it has not happened within
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/lists.xml
----------------------------------------------------------------------
diff --git a/content/guides/lists.xml b/content/guides/lists.xml
index 23e5847..48a9b63 100644
--- a/content/guides/lists.xml
+++ b/content/guides/lists.xml
@@ -25,6 +25,10 @@ limitations under the License.
<atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
</properties>
<body>
+ <section id="toc">
+ <title>Contents</title>
+ <toc/>
+ </section>
<section id="mailing-lists">
<title>Incubator Mailing Lists Guide</title>
@@ -54,7 +58,7 @@ This is where general and public discussion of the Incubator takes place.
</title>
<p>
This is the Incubator's "commits" list, named "cvs" for historical reasons. Changes made to the <a
-href="http://svn.apache.org/viewvc/incubator/public/trunk">Incubator codebase and website</a> and
+href="https://svn.apache.org/viewvc/incubator/public/trunk">Incubator codebase and website</a> and
the <a href="http://wiki.apache.org/incubator">Incubator wiki</a> trigger automatic notifications to
this list. Replies go to the <a href='general+at+incubator.apache.org'>general list</a>.
</p>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/mentor.xml
----------------------------------------------------------------------
diff --git a/content/guides/mentor.xml b/content/guides/mentor.xml
index 2a8d66c..d1d398d 100644
--- a/content/guides/mentor.xml
+++ b/content/guides/mentor.xml
@@ -43,7 +43,7 @@ It is informational not normative. Policy is laid down in the
<section id="Overview">
<title>Overview</title>
<p>
- After the Podling has been accepted by the Incubator PMC, the mentor
+ After the Podling has been accepted by the Incubator PMC, one of the mentors
<a href="../incubation/Incubation_Policy.html#Setting+Up+a+New+Podling">sets up</a>
the Podling; <em>i.e.</em> adds the podling metadata, creates the initial Podling status page, and
either creates or requests that
@@ -109,129 +109,246 @@ It is informational not normative. Policy is laid down in the
committers subscribe then these may be used for discussion.
</p>
</section>
- <section id="Set+Up+Podling">
- <title>Set Up Podling</title>
+ <section id='request-required-resources'><title>Request Required Resources</title>
+ <p>
+ The proposal should include a list of required resources. All of these will
+ require active set up. Some are created by infrastructure after an appropriate
+ request, others can be set up by any IPMC members (typically mentors).
+ </p><p>
+ Mailing lists should be created first. Other resources typically
+ post information to these lists.
+ </p>
+ <section id='request-mailing-lists'><title>Request Mailing Lists</title>
+ <p>
+ Apache mailing lists require volunteer moderators. New moderators can be
+ <a href='http://www.apache.org/dev/committers.html#mailing-list-moderators'>changed later</a>
+ but at least one volunteer is required before the mailing lists can be set up.
+ Moderation is a reasonably
+ <a href='http://www.apache.org/dev/committers.html#mail-moderate'>easy task</a>
+ though moderators may want to set up
+ <a href='http://spamassassin.apache.org/'>spam filtering</a>.
+ Having at least three moderators is recommended to spread the load.
+ </p><p>
+ The proposal should contain the rest of the information that needs to be collected
+ before the mailing lists can be requested. Incubator is the responsible top level project.
+ So the domain <code>MUST</code> be <code>incubator.apache.org</code>.
+ For example:
+ </p>
+ <ul>
+ <li>dev@${podling}.incubator.apache.org</li>
+ <li>commits@${podling}.incubator.apache.org</li>
+ <li>private@${podling}.incubator.apache.org</li>
+ </ul>
+ <p>
+ For initial community building it is usually appropriate to only have
+ a "dev" list, to keep the discussions focussed. Later add a "user" list
+ if needed.
+ </p>
+ <note>
+ Commits under <code>http://svn.apache.org/repos/asf/incubator/<em>${podling}</em></code>
+ will be emailed to <code>commits@${podling}.incubator.apache.org</code>.
+ Any deviation will
+ require special configuration in the <code>asf-mailer.conf</code> file by the IPMC.
+ </note>
+ <p>
+ Mailing lists creation is a task for the <a href='#who-infra'>infrastructure team</a>. The
+ infrastructure team offers a tool that simplifies the creation of mailing lists. You can access the
+ <a href="https://infra.apache.org/officers/mlreq/incubator" target="_new">Incubator Mailing List Request Form</a>
+ to request a list. A notification will be sent to private@incubator when the lists have been created.
+ </p>
+ <p>
+ Remember to update the project status file with mailing list details. Prospective committers
+ and mentors will need to subscribe. Email them once the status file has been updated. Inform
+ any existing mailing lists or forums previously used by the project.
+ </p>
+ <p>
+ Once the <code>commits</code> list is created, the project MUST review
+ the <code>/incubator/${podling}</code> tree, since any commits made prior
+ to the list's creation will have generated no email trail.
+ </p>
+ <section id='mail-archives'><title>Mail Archives</title>
+ <p>
+ Archives at <a href='http://mail-archives.apache.org'>http://mail-archives.apache.org</a> for the public
+ mailing lists will be setup as part of the mailing list creation process. No action is
+ required by Mentors. The archives will be <a href='http://mail-archives.apache.org/mod_mbox/'>visible</a>
+ as soon as posts have been made (and moderated) to these lists.
+ </p>
+ <p>
+ You can also leverage <a href="https://lists.apache.org" target="_new">lists.apache.org</a> for
+ mailing list archives. There is a login link in the top right corner, which allows you to respond to
+ threads from within the web application.
+ </p>
+ <p>
+ Many projects are independently archived externally (for example, at
+ <a href='http://www.mail-archive.com/'>The Mail Archive</a> and
+ <a href='http://marc.info/?q=about'>MARC</a>)
+ Independent archives help to
+ increase project visibility as well as preserving a independent historic record.
+ These subscriptions are not automatically created. If desired, subscribe manually.
+ </p><p>
+ Subscriptions to news-to-mailing-list bridges (for example, <a href='http://www.nabble.com'>Nabble</a>)
+ must also be created manually. Subscribing helps accessibility and visibility but Nabble news
+ users may not be aware that they are posting to a mailing list.
+ </p>
+ </section>
+ <section id='mail-admin'><title>Mailing List Administration</title>
+ <p>
+ Apache uses <a href='http://www.ezmlm.org/'>ezmlm</a>. See the
+ <a href='http://www.ezmlm.org/man/ezmlmman.html'>manual</a> and
+ committer <a href='http://www.apache.org/dev/committers.html#mail'>mail FAQ</a>
+ for more details.
+ </p>
+ </section>
+ <section id='transition-mailing-lists'><title>Mailing List Transition</title>
+ <p>
+ Independent mailing lists and groups are perfectly acceptable but development should
+ happen on the official mailing lists at Apache. If a project has existing mailing lists,
+ forums or groups the community needs to consider their future and plan for the transition
+ to the official Apache mailing lists.
+ </p><p>
+ It may be useful to move development first to the official lists followed gradually
+ by the user resources.
+ </p>
+ <p>
+ Note that subscribers of external mailing lists will not be automatically subscribed
+ to the new Incubator project mailing lists. Instead, a note should be posted to the
+ old external mailing list asking them to subscribe to the new list. If possible, add
+ a footer to the old mailing list with some instructions.
+ </p>
+ </section>
+ <section id='request-issue-tracking'><title>Issue Tracking</title>
+ <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'
+ type (not bug or request)
+ </p>
+ <p>
+ Remember to post an email announcing that the issue tracker is available.
+ </p>
+ </section>
+ </section>
- <p>
- The most important responsibility for mentors is to set up the
- podling source repository. Podlings can choose between svn and
- git for source control.
- </p>
+ <section id="Set+Up+Podling+Source+Repository">
+ <title>Set Up Podling Source Repository</title>
- <section id="Set+Up+GIT+Repository">
- <title>Set up GIT Repository</title>
- <p>
- Setting up git for a podling is simple. You open a JIRA to
- INFRA and request it. You can either ask for a bare
- repository or for a repository imported from some
- publically-accessible existing repository; tell infra what you
- need.
- </p>
- <p>
- The Foundation's policy
- is to grant access to git repositories broadly to the incubator group,
- not narrowly podling-by-podling. So, once the repository
- exists, incubator group members gain access without further work. Once
- the podling graduates, a dedicated ldap group will be created to manage
- access and only those members will be given access.
- </p>
- </section>
- <section id="Set+Up+SVN+Repository">
- <title>Set Up SVN Repository</title>
- <p>
- If the podling chooses svn, you must create the
- repository and give read/write access to the repository
- to all the committers for the podling. This involves requesting
- new committer accounts and granting access to mentors and existing
- Apache committers.
- </p>
- <p>Setting up a podling subversion repository has two steps: Creating the SVN space
- and configuring the authorization (in both svn and git).
- </p>
- <p>
- Create the workspace in svn. This requires commit access to the
- incubator svn repository. Podlings are given their own subdirectory
- of the incubator svn repository. To create the podling subdirectory,
- the mentor executes the svn command to create a remote directory:
- <code>
- svn mkdir https://svn.apache.org/repos/asf/incubator/{podling}
- </code>
- </p>
- <p>Create the workspace authorization in asf-authorization-template.
- This requires commit access to the file
- <code>https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template</code>
- as well as commit access to the git repo <code>infrastructure-puppet</code> to update the file
- <code>modules/subversion_server/files/authorization/asf-authorization-template</code>. Please follow the procedures in the <a href="https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo">infrastructure puppet workflow</a> document.
- </p>
- <p>
- Edit the file to add the podling repository in alphabetical order, e.g.
- </p>
- <source>{podling}={mentor1},{mentor2}</source>
- <p>
- In the section listing all the projects (again in alphabetical order)
- add the podling directory and permissions, to enable the podling for its
- eventual website:
- </p>
- <source>[/incubator/{podling}]
-@{podling} = rw
-...</source>
- <p>
- Enable the podling for the Incubator website:
- </p>
- <source>[/incubator/public]
-...
-@{podling} = rw
-...</source>
- <p>
-This is a convenient time to add <a href='#Authorize+Committers'>authorization</a> for committers
-who have accounts.
- </p>
- <p>
-<a href='#who-auth-karma'>Authorization</a> karma is restricted. If no Mentor
-has this karma then post an email to IPMC private list requesting that this
-is actioned.
- </p>
- </section>
- <section id="Authorize+Committers">
- <title>Authorize Committers</title>
- <p>The process to add committers to the podling depends on whether
- the new committer is already an Apache committer and whether
- the new committer is in the list of original committers:
- </p>
- <ul>
- <li>The committer is in the list of original committers in the
- podling proposal to the incubator and is not already an Apache
- committer:
- <ul>
- <li>
- Ask developers to send their ICLA to secretary@apache.org according to
- <a href="http://apache.org/licenses/#submitting">standard procedure.</a>
- Note that ICLA forms must be signed, either by hand or by digital signature.
- </li>
- <li>
- Developers should choose an Apache id that is not already listed
- <a href="http://people.apache.org/committer-index.html">here.</a>
- </li>
- <li>
- Developers should enter their preferred Apache id on the ICLA
- and enter the podling name in the "notify" field of the ICLA.
- </li>
- </ul>
- </li>
- <li> The committer is in the list of original committers in the
- podling proposal to the incubator and is already an Apache committer, only
- <a href='#who-auth-karma'>incubator authorization</a> is required.
- </li>
- <li>The committer was voted by the PPMC and approved by the incubator
- PMC:
- </li>
- <p>
- Perform one of the above procedures depending on whether the
- committer is already an Apache committer on another project.
- </p>
- </ul>
- </section>
- </section>
+ <p>
+ The most important responsibility for mentors is to set up the
+ podling source repository. Podlings can choose between svn and
+ git for source control.
+ </p>
+
+ <section id="Set+Up+GIT+Repository">
+ <title>Set up GIT Repository</title>
+ <p>
+ Requests for new git repos are done via <a href="https://reporeq.apache.org/" target="_new">reporeq.apache.org</a>.
+ This service will initialize a new repository, setup github mirrors and enable integrations for that repository.
+ </p>
+ <p>
+ The Foundation's policy
+ is to grant access to git repositories broadly to the incubator group,
+ not narrowly podling-by-podling. So, once the repository
+ exists, incubator group members gain access without further work. Once
+ the podling graduates, a dedicated ldap group will be created to manage
+ access and only those members will be given access.
+ </p>
+ </section>
+ <section id="Set+Up+SVN+Repository">
+ <title>Set Up SVN Repository</title>
+ <p>
+ If the podling chooses svn, you must create the
+ repository and give read/write access to the repository
+ to all the committers for the podling. This involves requesting
+ new committer accounts and granting access to mentors and existing
+ Apache committers.
+ </p>
+ <p>Setting up a podling subversion repository has two steps: Creating the SVN space
+ and configuring the authorization (in both svn and git).
+ </p>
+ <p>
+ Create the workspace in svn. This requires commit access to the
+ incubator svn repository. Podlings are given their own subdirectory
+ of the incubator svn repository. To create the podling subdirectory,
+ the mentor executes the svn command to create a remote directory:
+ <code>
+ svn mkdir https://svn.apache.org/repos/asf/incubator/{podling}
+ </code>
+ </p>
+ <p>Create the workspace authorization in asf-authorization-template.
+ This requires commit access to the file
+ <code>https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template</code>
+ as well as commit access to the git repo <code>infrastructure-puppet</code> to update the file
+ <code>modules/subversion_server/files/authorization/asf-authorization-template</code>. Please follow the procedures in the <a href="https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo">infrastructure puppet workflow</a> document.
+ </p>
+ <p>
+ Edit the file to add the podling repository in alphabetical order, e.g.
+ </p>
+ <source>{podling}={mentor1},{mentor2}</source>
+ <p>
+ In the section listing all the projects (again in alphabetical order)
+ add the podling directory and permissions, to enable the podling for its
+ eventual website:
+ </p>
+ <source>[/incubator/{podling}]
+ @{podling} = rw
+ ...</source>
+ <p>
+ Enable the podling for the Incubator website:
+ </p>
+ <source>[/incubator/public]
+ ...
+ @{podling} = rw
+ ...</source>
+ <p>
+ This is a convenient time to add <a href='#Authorize+Committers'>authorization</a> for committers
+ who have accounts.
+ </p>
+ <p>
+ <a href='#who-auth-karma'>Authorization</a> karma is restricted. If no Mentor
+ has this karma then post an email to IPMC private list requesting that this
+ is actioned.
+ </p>
+ </section>
+ <section id="Authorize+Committers">
+ <title>Authorize Committers</title>
+ <p>The process to add committers to the podling depends on whether
+ the new committer is already an Apache committer and whether
+ the new committer is in the list of original committers:
+ </p>
+ <ul>
+ <li>The committer is in the list of original committers in the
+ podling proposal to the incubator and is not already an Apache
+ committer:
+ <ul>
+ <li>
+ Ask developers to send their ICLA to secretary@apache.org according to
+ <a href="http://apache.org/licenses/#submitting">standard procedure.</a>
+ Note that ICLA forms must be signed, either by hand or by digital signature.
+ </li>
+ <li>
+ Developers should choose an Apache id that is not already listed
+ <a href="http://people.apache.org/committer-index.html">here.</a>
+ </li>
+ <li>
+ Developers should enter their preferred Apache id on the ICLA
+ and enter the podling name in the "notify" field of the ICLA.
+ </li>
+ </ul>
+ </li>
+ <li> The committer is in the list of original committers in the
+ podling proposal to the incubator and is already an Apache committer, only
+ <a href='#who-auth-karma'>incubator authorization</a> is required.
+ </li>
+ <li>The committer was voted by the PPMC and approved by the incubator
+ PMC:
+ </li>
+ <p>
+ Perform one of the above procedures depending on whether the
+ committer is already an Apache committer on another project.
+ </p>
+ </ul>
+ </section>
+ </section>
<section id='bootstrap'><title>[DRAFT] Podling Bootstrap</title>
<p>
@@ -547,123 +664,6 @@ please ask the infrastructure team politely.
</section>
</section>
</section>
-
- <section id='request-required-resources'><title>Request Required Resources</title>
- <p>
- The proposal should include a list of required resources. All of these will
- require active set up. Some are created by infrastructure after an appropriate
- request, others can be set up by any IPMC members (typically mentors).
- </p><p>
- Mailing lists should be created first. Other resources typically
- post information to these lists.
- </p>
- <section id='request-mailing-lists'><title>Request Mailing Lists</title>
- <p>
- Apache mailing lists require volunteer moderators. New moderators can be
- <a href='http://www.apache.org/dev/committers.html#mailing-list-moderators'>changed later</a>
- but at least one volunteer is required before the mailing lists can be set up.
- Moderation is a reasonably
- <a href='http://www.apache.org/dev/committers.html#mail-moderate'>easy task</a>
- though moderators may want to set up
- <a href='http://spamassassin.apache.org/'>spam filtering</a>.
- Having at least three moderators is recommended to spread the load.
- </p><p>
- The proposal should contain the rest of the information that needs to be collected
- before the mailing lists can be requested. Incubator is the responsible top level project.
- So the domain <code>MUST</code> be <code>incubator.apache.org</code>.
- For example:
- </p>
- <ul>
- <li>dev@${podling}.incubator.apache.org</li>
- <li>commits@${podling}.incubator.apache.org</li>
- <li>private@${podling}.incubator.apache.org</li>
- </ul>
- <p>
- For initial community building it is usually appropriate to only have
- a "dev" list, to keep the discussions focussed. Later add a "user" list
- if needed.
- </p>
- <note>
-Commits under <code>http://svn.apache.org/repos/asf/incubator/<em>${podling}</em></code>
-will be emailed to <code>commits@${podling}.incubator.apache.org</code>.
-Any deviation will
-require special configuration in the <code>asf-mailer.conf</code> file by the IPMC.
- </note>
- <p>
- Mailing lists creation is a task for the <a href='#who-infra'>infrastructure team</a>. The
- infrastructure team offers a tool that simplifies the creation of mailing lists - please
- visit the <a href='https://infra.apache.org/'>infrastructure site</a> for the latest link.
- Note that there is an incubator-specific link at the bottom of the initial form. A notification
- will be sent to private@incubator when the lists have been created.
- </p>
- <p>
- Remember to update the project status file with mailing list details. Prospective committers
- and mentors will need to subscribe. Email them once the status file has been updated. Inform
- any existing mailing lists or forums previously used by the project.
- </p>
- <p>
- Once the <code>commits</code> list is created, the project MUST review
- the <code>/incubator/${podling}</code> tree, since any commits made prior
- to the list's creation will have generated no email trail.
- </p>
- <section id='mail-archives'><title>Mail Archives</title>
- <p>
-Archives at <a href='http://mail-archives.apache.org'>http://mail-archives.apache.org</a> for the public
-mailing lists will be setup as part of the mailing list creation process. No action is
-required by Mentors. The archives will be <a href='http://mail-archives.apache.org/mod_mbox/'>visible</a>
-as soon as posts have been made (and moderated) to these lists.
- </p>
- <p>
-Many projects are independently archived externally (for example, at
-<a href='http://www.mail-archive.com/'>The Mail Archive</a> and
-<a href='http://marc.info/?q=about'>MARC</a>)
-Independent archives help to
-increase project visibility as well as preserving a independent historic record.
-These subscriptions are not automatically created. If desired, subscribe manually.
- </p><p>
-Subscriptions to news-to-mailing-list bridges (for example, <a href='http://www.nabble.com'>Nabble</a>)
-must also be created manually. Subscribing helps accessibility and visibility but Nabble news
-users may not be aware that they are posting to a mailing list.
- </p>
- </section>
- <section id='mail-admin'><title>Mailing List Administration</title>
- <p>
-Apache uses <a href='http://www.ezmlm.org/'>ezmlm</a>. See the
-<a href='http://www.ezmlm.org/man/ezmlmman.html'>manual</a> and
-committer <a href='http://www.apache.org/dev/committers.html#mail'>mail FAQ</a>
-for more details.
- </p>
- </section>
- <section id='transition-mailing-lists'><title>Mailing List Transition</title>
- <p>
-Independent mailing lists and groups are perfectly acceptable but development should
-happen on the official mailing lists at Apache. If a project has existing mailing lists,
-forums or groups the community needs to consider their future and plan for the transition
-to the official Apache mailing lists.
- </p><p>
-It may be useful to move development first to the official lists followed gradually
-by the user resources.
- </p>
- <p>
- Note that subscribers of external mailing lists will not be automatically subscribed
- to the new Incubator project mailing lists. Instead, a note should be posted to the
- old external mailing list asking them to subscribe to the new list. If possible, add
- a footer to the old mailing list with some instructions.
- </p>
- </section>
- <section id='request-issue-tracking'><title>Issue Tracking</title>
- <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'
- type (not bug or request)
- </p>
- <p>
-Remember to post an email announcing that the issue tracker is available.
- </p>
- </section>
- </section>
-
<section id='orientation'><title>Orientating New Committers: Understanding Apache</title>
<p>
When a committer is elected by a typical top level project, the nominator
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/pmc.xml
----------------------------------------------------------------------
diff --git a/content/guides/pmc.xml b/content/guides/pmc.xml
index 2b26613..3257d87 100644
--- a/content/guides/pmc.xml
+++ b/content/guides/pmc.xml
@@ -14,7 +14,7 @@ limitations under the License.
-->
<document>
<properties>
- <title>PMC</title>
+ <title>Incubator PMC 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>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/ppmc.xml
----------------------------------------------------------------------
diff --git a/content/guides/ppmc.xml b/content/guides/ppmc.xml
index 9f3c7b7..0aee1b8 100644
--- a/content/guides/ppmc.xml
+++ b/content/guides/ppmc.xml
@@ -224,11 +224,8 @@ limitations under the License.
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. The [VOTE] message should be forwarded
- to the IPMC (<a href="mailto:private@incubator.apache.org">
- private@incubator.apache.org</a>) to notify them that the
- vote is underway. Do not CC or BCC the IPMC on this thread. Instead,
- forward the initial VOTE email.</p>
+ [VOTE] Joe Bob PPMC membership.
+ </p>
<p>If the vote is successful, the proposer
should send a message to the PPMC private alias, with
the subject line of [VOTE][RESULT] Joe Bob PPMC membership. The
@@ -285,5 +282,17 @@ limitations under the License.
they may want to drop a mail on the general incubator mailing list to try
to recruit a new mentor.</p>
</section>
+ <section id="PPMC+binding+votes">
+ <title>PPMC and Binding Votes</title>
+ <p>
+ The only time when a PPMC member's vote is binding is for the addition of
+ new PPMC members and committers. Release votes are only binding to IPMC
+ members.
+ </p>
+ <p>
+ The binding status of a person's vote is not related to the mailing list
+ that the vote is occurring on.
+ </p>
+ </section>
</body>
</document>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/proposal.xml
----------------------------------------------------------------------
diff --git a/content/guides/proposal.xml b/content/guides/proposal.xml
index f9a66f4..3bcfa4c 100644
--- a/content/guides/proposal.xml
+++ b/content/guides/proposal.xml
@@ -128,7 +128,7 @@ Use the template as a guide but do not feel constrained
by it. Adopt what works and change what doesn't. That's fine - in fact, it's expected.
</p>
<p>
-Be sure to add your pproposal to <a href='http://wiki.apache.org/incubator/ProjectProposals'>this list</a>.
+Be sure to add your proposal to <a href='http://wiki.apache.org/incubator/ProjectProposals'>this list</a>.
</p>
</section>
<section id='name'><title>Project Name</title>
@@ -1000,7 +1000,7 @@ a person already associated with Apache who leads the proposal process. It is co
<a href='#template-mentors'>Mentor</a>.
</p>
<p>
-A Champion should be found before the proposal is formally submitted.
+A Champion should be found while the proposal is still being formulated. Their role is to help formulate the proposal and work with you to resolve comments and questions put forth by the IPMC while reviewing the proposal.
</p>
</note>
</section>
@@ -1011,24 +1011,9 @@ Lists <a href="&root-path;/incubation/Incubation_Policy.html#Mentor">eligible</a
individuals nominated as <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>
[<a href="&root-path;/incubation/Incubation_Policy.html#Mentor">definition</a>] for the candidate.
</p>
- <p>
-It is common for additional Mentors to <a href='participation.html#mentors'>volunteer</a> their services
-during the development of the proposal. The number of Mentors for a Podling is limited only by the
-energy and interest of those eligible to Mentor. Three Mentors gives a quorum and allows
-a Podling more autonomy. The current consensus is that three or more Mentors makes the
-incubation process run more smoothly.
- </p>
- <p>
-Note that since Mentors are appointed by the
-<a href="&root-path;/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">
-Incubator PMC</a>
-at the end of the acceptance process, they have no formal role until the proposal is accepted.
-But informal enthusiasm from nominee Mentors is taken as a good sign.
- </p>
- <p>
-There is no restriction on the number of informal mentors (note the small <em>m</em>)
-that a Podling may have. These can be very useful but have no formal role in the process.
- </p>
+<p>
+ <a href='participation.html#mentors'>Three Mentors</a> gives a quorum and allows a Podling more autonomy from the <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator PMC</a>, so the current consensus is that three Mentors is a good number. Any experienced Apache community member can provide informal mentorship anyway, what's important is to make sure the podling has enough regularly available mentors to progress smoothly. There is no restriction on the number of mentors, formal or informal, a Podling may have.
+</p>
</note>
</section>
<section id='template-sponsoring-entity'><title>Sponsoring Entity</title>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/releasemanagement.xml
----------------------------------------------------------------------
diff --git a/content/guides/releasemanagement.xml b/content/guides/releasemanagement.xml
index 7aa7f25..9794620 100644
--- a/content/guides/releasemanagement.xml
+++ b/content/guides/releasemanagement.xml
@@ -1775,7 +1775,7 @@ example</a>.
<p>
Be careful to check the voters against the appropriate list. Binding votes are cast by people on the
appropriate committee. The list of Incubator PMC members is
-<a href='http://people.apache.org/committers-by-project.html#incubator-pmc'>available</a>.
+<a href='https://people.apache.org/phonebook.html?pmc=incubator'>available</a>.
</p>
<p>
The result post should list each voter and the vote cast. Non binding votes may be listed. If they are
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/guides/website.xml
----------------------------------------------------------------------
diff --git a/content/guides/website.xml b/content/guides/website.xml
index 44d459b..a23a88e 100644
--- a/content/guides/website.xml
+++ b/content/guides/website.xml
@@ -24,7 +24,7 @@ limitations under the License.
<p>The Incubator website is generated by the Apache CMS, but it
is still using the Anakia-based page generation mechanism that was
used before,
- triggered by a <a href="http://svn.apache.org/repos/asf/incubator/public/trunk/build_cms.sh">CMS external build script</a>.
+ triggered by a <a href="https://svn.apache.org/repos/asf/incubator/public/trunk/build_cms.sh">CMS external build script</a>.
</p>
<p>
This means that you can edit the content either directly in svn
@@ -34,8 +34,8 @@ 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.
@@ -64,7 +64,7 @@ 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,
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/incubation/Incubation_Policy.xml
----------------------------------------------------------------------
diff --git a/content/incubation/Incubation_Policy.xml b/content/incubation/Incubation_Policy.xml
index f1d5a89..0deabdc 100644
--- a/content/incubation/Incubation_Policy.xml
+++ b/content/incubation/Incubation_Policy.xml
@@ -811,12 +811,10 @@ This role and its responsibilities are discussed
<title>Mentor
</title>
<p>A Podling has one or more Mentors, one of which MUST be an Apache Member.
-Mentors are chosen by the Sponsor to actively monitor the
-podling, guide the podling in
+Mentors are responsible for actively monitoring 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
+and report its status to the Sponsor and the Incubator PMC. All Mentors must
+be members of the Incubator PMC. A Mentor has
<a href="Roles_and_Responsibilities.html#Mentor">responsibilities</a>
toward the Incubator PMC, the Sponsor, and the community of the assigned
Podling.
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/podlings.xml
----------------------------------------------------------------------
diff --git a/content/podlings.xml b/content/podlings.xml
index dc96873..a6efc38 100644
--- a/content/podlings.xml
+++ b/content/podlings.xml
@@ -268,9 +268,9 @@ and a set of useful extensions for this specification.</description>
<mentor username="matzew">Matthias Wessendorf</mentor>
</mentors>
</podling>
- <podling name="Beam" status="current" resource="beam" sponsor="Incubator" startdate="2016-02-01">
+ <podling name="Beam" status="graduated" resource="beam" sponsor="Incubator" startdate="2016-02-01" enddate="2016-12-21">
<description>Apache Beam is an open source, unified model and set of language-specific SDKs for defining and executing data processing workflows, and also data ingestion and integration flows, supporting Enterprise Integration Patterns (EIPs) and Domain Specific Languages (DSLs). Dataflow pipelines simplify the mechanics of large-scale batch and streaming data processing and can run on a number of runtimes like Apache Flink, Apache Spark, and Google Cloud Dataflow (a cloud service). Beam also brings DSL in different languages, allowing users to easily implement their data integration processes.</description>
- <reporting group="2"/>
+ <resolution tlp="true"/>
<champion availid="jbonofre">Jean-Baptiste Onofre</champion>
<mentors>
<mentor username="jbonofre">Jean-Baptiste Onofre</mentor>
@@ -487,9 +487,9 @@ and a set of useful extensions for this specification.</description>
<mentor username="mnour">Mohammad Nour El-Din</mentor>
</mentors>
</podling>
- <podling name="CommonsRDF" status="current" resource="commonsrdf" sponsor="Incubator" startdate="2015-03-06">
+ <podling name="CommonsRDF" status="graduated" resource="commonsrdf" sponsor="Incubator" startdate="2015-03-06" enddate="2016-11-28">
<description>Commons RDF is a set of interfaces and classes for RDF 1.1 concepts and behaviours. The commons-rdf-api module defines interfaces and testing harness. The commons-rdf-simple module provides a basic reference implementation to exercise the test harness and clarify API contracts.</description>
- <reporting group="3" />
+ <resolution url="https://commons.apache.org/proper/rdf"/>
<champion availid="lewismc">Lewis John McGibbney</champion>
<mentors>
<mentor username="johndament">John D Ament</mentor>
@@ -573,7 +573,7 @@ and a set of useful extensions for this specification.</description>
</podling>
<podling name="DataFu" status="current" resource="datafu" sponsor="Incubator" startdate="2014-01-05">
<description>DataFu provides a collection of Hadoop MapReduce jobs and functions in higher level languages based on it to perform data analysis. It provides functions for common statistics tasks (e.g. quantiles, sampling), PageRank, stream sessionization, and set and bag operations. DataFu also provides Hadoop jobs for incremental data processing in MapReduce.</description>
- <reporting group="1" monthly="true">November</reporting>
+ <reporting group="1"/>
<champion availid="jghoman">Jakob Homan</champion>
<mentors>
<mentor username="hashutosh">Ashutosh Chauhan</mentor>
@@ -873,7 +873,7 @@ and a set of useful extensions for this specification.</description>
<mentors>
<mentor username="ptgoetz">P. Taylor Goetz</mentor>
<mentor username="elserj">Josh Elser</mentor>
- <mentor username="busbey">Sean Busbey</mentor>
+ <mentor username="drew">Drew Farris</mentor>
</mentors>
</podling>
<podling name="Graffito" status="retired" resource="graffito" sponsor="Portals" startdate="2004-09-20" enddate="2007-07-11">
@@ -882,6 +882,16 @@ and a set of useful extensions for this specification.</description>
<mentor username="raphael">Raphael Luta</mentor>
</mentors>
</podling>
+ <podling name="Griffin" status="current" resource="griffin" sponsor="Incubator" startdate="2016-12-05">
+ <description>Griffin is a open source Data Quality solution for distributed data systems at any scale in both streaming or batch data context</description>
+ <reporting group="3"/>
+ <champion availid="hsaputra">Henry Saputra</champion>
+ <mentors>
+ <mentor username="kaspersor">Kasper S�rensen</mentor>
+ <mentor username="umamahesh">Uma Maheswara Rao Gangumalla</mentor>
+ <mentor username="lresende">Luciano Resende</mentor>
+ </mentors>
+ </podling>
<podling name="Guacamole" status="current" resource="guacamole" sponsor="Incubator" startdate="2016-02-10">
<description>Guacamole is an enterprise-grade, protocol-agnostic, remote desktop gateway. Combined with cloud hosting, Guacamole provides an excellent alternative to traditional desktops. Guacamole aims to make cloud-hosted desktop access preferable to traditional, local access.</description>
<reporting group="2"/>
@@ -894,9 +904,9 @@ and a set of useful extensions for this specification.</description>
<mentor username="gtrasuk">Greg Trasuk</mentor>
</mentors>
</podling>
- <podling name="Geode" status="current" resource="geode" sponsor="Incubator" startdate="2015-04-27">
+ <podling name="Geode" status="graduated" resource="geode" sponsor="Incubator" startdate="2015-04-27" enddate="2016-11-16">
<description>Geode is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures.</description>
- <reporting group="1" />
+ <resolution tlp="true"/>
<champion availid="rvs">Roman Shaposhnik</champion>
<mentors>
<mentor username="cos">Konstantin Boudnik</mentor>
@@ -1030,6 +1040,7 @@ and a set of useful extensions for this specification.</description>
<mentor username="rxin">Reynold Xin</mentor>
<mentor username="weimer">Markus Weimer</mentor>
<mentor username="meng">Xiangrui Meng</mentor>
+ <mentor username="daijy">Daniel Dai</mentor>
</mentors>
</podling>
<podling name="HTrace" status="current" resource="htrace" sponsor="Incubator" startdate="2014-11-11">
@@ -1801,6 +1812,16 @@ and a set of useful extensions for this specification.</description>
<mentor username="matzew">Matthias Wessendorf</mentor>
</mentors>
</podling>
+ <podling name="OpenWhisk" status="current" resource="openwhisk" sponsor="Incubator" startdate="2016-11-23">
+ <description>distributed Serverless computing platform</description>
+ <reporting group="3" monthly="true">December, January, February</reporting>
+ <champion availid="rubys">Sam Ruby</champion>
+ <mentors>
+ <mentor username="fmeschbe">Felix Meschberger</mentor>
+ <mentor username="isabel">Isabel Drost-Fromm</mentor>
+ <mentor username="wikier">Sergio Fern�ndez</mentor>
+ </mentors>
+ </podling>
<podling name="Parquet" status="graduated" resource="parquet" sponsor="Incubator" startdate="2014-05-20" enddate="2015-04-22">
<description>Parquet is a columnar storage format for Hadoop.</description>
<resolution tlp="true"/>
@@ -2001,6 +2022,18 @@ and a set of useful extensions for this specification.</description>
<mentor username="jukka">Jukka Zitting</mentor>
</mentors>
</podling>
+ <podling name="RocketMQ" status="current" resource="rocketmq" sponsor="Incubator" startdate="2016-11-21">
+ <description>RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to use message-oriented middleware, especially for processing large amounts of streaming data.</description>
+ <reporting group="1" monthly="true">January, February</reporting>
+ <champion availid="bsnyder">Bruce Snyder</champion>
+ <mentors>
+ <mentor username="bsnyder">Bruce Snyder</mentor>
+ <mentor username="brianm">Brian McCallister</mentor>
+ <mentor username="ningjiang">Willem Ning Jiang</mentor>
+ <mentor username="lukehan">Luke Han</mentor>
+ <mentor username="jmclean">Justin McLean</mentor>
+ </mentors>
+ </podling>
<podling name="Roller" status="graduated" resource="roller" sponsor="Incubator" startdate="2005-06-20" enddate="2007-02-21">
<description>Roller blog server</description>
<resolution tlp="true"/>
@@ -2016,8 +2049,8 @@ and a set of useful extensions for this specification.</description>
<mentors>
<mentor username="elserj">Josh Elser</mentor>
<mentor username="edwardyoon">Edward J. Yoon</mentor>
- <mentor username="busbey">Sean Busbey</mentor>
<mentor username="venkatesh">Venkatesh Seetharam</mentor>
+ <mentor username="billie">Billie Rinaldi</mentor>
</mentors>
</podling>
<podling name="S2Graph" status="current" resource="s2graph" sponsor="Incubator" startdate="2015-11-29">
@@ -2386,9 +2419,10 @@ and a set of useful extensions for this specification.</description>
<mentor username="andy">Andy Seaborne</mentor>
<!--Retired <mentor username="mattmann">Chris Mattmann</mentor>-->
<mentor username="djd">Daniel J Debrunner</mentor>
- <mentor username="suresh">Suresh Srinivas</mentor>
- <mentor username="smarru">Suresh Marru</mentor>
<mentor username="mpierce">Marlon Pierce </mentor>
+ <mentor username="stain">Stian Soiland-Reyes</mentor>
+ <mentor username="smarru">Suresh Marru</mentor>
+ <mentor username="suresh">Suresh Srinivas</mentor>
</mentors>
</podling>
<podling name="Tephra" status="current" resource="tephra" sponsor="Incubator" startdate="2016-03-07">
@@ -2399,7 +2433,6 @@ top of Apache HBase and other storage engines.</description>
<mentors>
<mentor username="gates">Alan Gates</mentor>
<mentor username="apurtell">Andrew Purtell</mentor>
- <mentor username="hsaputra">Henry Saputra</mentor>
<mentor username="jamestaylor">James Taylor</mentor>
<mentor username="larsh">Lars Hofhansl</mentor>
</mentors>
@@ -2619,6 +2652,17 @@ top of Apache HBase and other storage engines.</description>
<mentor username="husted">Ted Husted</mentor>
</mentors>
</podling>
+ <podling name="Weex" status="current" resource="weex" sponsor="Incubator" startdate="2016-11-30">
+ <description>Weex is a framework for building Mobile cross-platform high performance UI.</description>
+ <reporting group="1" monthly="true">January, February, March</reporting>
+ <champion availid="edwardyoon">Edward J. Yoon</champion>
+ <mentors>
+ <mentor username="lukehan">Luke Han</mentor>
+ <mentor username="ningjiang">Willem Jiang</mentor>
+ <mentor username="sewen">Stephan Ewen</mentor>
+ <mentor username="niclas">Niclas Hedhman</mentor>
+ </mentors>
+ </podling>
<podling name="Whirr" status="graduated" resource="whirr" sponsor="Incubator" startdate="2010-05-11" enddate="2011-08-17">
<description>Whirr provides code for running a variety of software services on cloud infrastructure.</description>
<resolution tlp="true"/>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/airflow.xml
----------------------------------------------------------------------
diff --git a/content/projects/airflow.xml b/content/projects/airflow.xml
index b2acc4b..390a5d0 100644
--- a/content/projects/airflow.xml
+++ b/content/projects/airflow.xml
@@ -149,6 +149,11 @@
<td>Sumit Maheshwari</td>
</tr>
<tr>
+ <td>.</td>
+ <td>alexvanboxel</td>
+ <td>Alex Van Boxel</td>
+ </tr>
+ <tr>
<td>Extra</td>
<td>.</td>
<td>.</td>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/ariatosca.xml
----------------------------------------------------------------------
diff --git a/content/projects/ariatosca.xml b/content/projects/ariatosca.xml
index ab4acf1..4c3cafd 100644
--- a/content/projects/ariatosca.xml
+++ b/content/projects/ariatosca.xml
@@ -155,7 +155,9 @@
<section id="Incubation+status+reports">
<title>Incubation status reports</title>
<ul>
- <li>none yet</li>
+ <li>September 2016</li>
+ <li>October 2016</li>
+ <li>November 2016</li>
</ul>
</section>
<section id="Incubation+work+items">
@@ -224,7 +226,7 @@
<td>Ask infrastructure to set up wiki (Confluence, Moin).</td>
</tr>
<tr>
- <td>....-..-..</td>
+ <td>2016-10-12</td>
<td>Migrate the project to our infrastructure.</td>
</tr>
</table>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/beam.xml
----------------------------------------------------------------------
diff --git a/content/projects/beam.xml b/content/projects/beam.xml
index 8165e78..cfa37d4 100644
--- a/content/projects/beam.xml
+++ b/content/projects/beam.xml
@@ -9,18 +9,22 @@
<title>Beam Project Incubation Status</title>
<p>This page tracks the project status, incubator-wise. For more general
project status, look on the project website.</p>
+ <p><strong>THIS WEBSITE IS NO LONGER MAINTAINED!</strong></p>
+ <p><span class='graduated'>The Beam project graduated on 2016-12-21.</span></p>
</section>
<section id="Description">
<title>Description</title>
- <p>Apache Beam is an open source, unified model and set of language-specific SDKs for defining and executing data processing workflows, and also data ingestion and integration flows, supporting Enterprise Integration Patterns (EIPs) and Domain Specific Languages (DSLs). Dataflow pipelines simplify the mechanics of large-scale batch and streaming data processing and can run on a number of runtimes like Apache Flink, Apache Spark, and Google Cloud Dataflow (a cloud service). Beam also brings DSL in different languages, allowing users to easily implement their data integration processes.</p>
+ <p>Apache Beam is a unified programming model for both batch and streaming data processing, enabling efficient execution across diverse distributed execution engines and providing extensibility points for connecting to different technologies and user communities.</p>
</section>
<section id="News">
<title>News</title>
<ul>
<li>2016-02-01 Project enters incubation.</li>
<li>2016-02-02 JIRA, mailing lists, git, website space created.</li>
- <li>2016-06-15 Apache Beam 0.1.0-incubating released</li>
- <li>2016-08-09 Apache Beam 0.2.0-incubating released</li>
+ <li>2016-06-15 Apache Beam 0.1.0-incubating released.</li>
+ <li>2016-08-09 Apache Beam 0.2.0-incubating released.</li>
+ <li>2016-10-31 Apache Beam 0.3.0-incubating released.</li>
+ <li>2016-12-21 Apache Beam graduation resolution enacted by the ASF Board.</li>
</ul>
</section>
<section id="Project+info">
@@ -88,7 +92,7 @@
<td>Jean-Baptiste Onofr�</td>
</tr>
<tr>
- <td>Committers</td>
+ <td>PPMC / committers</td>
<td>aljoscha</td>
<td>Aljoscha Krettek</td>
</tr>
@@ -165,7 +169,7 @@
<tr>
<td>.</td>
<td>tomwhite</td>
- <td>Tom White</td>
+ <td>Thomas White</td>
</tr>
<tr>
<td>.</td>
@@ -177,6 +181,21 @@
<td>robertwb</td>
<td>Robert Bradshaw</td>
</tr>
+ <tr>
+ <td>Committers</td>
+ <td>jesseanderson</td>
+ <td>Jesse Anderson</td>
+ </tr>
+ <tr>
+ <td>.</td>
+ <td>tgroh</td>
+ <td>Thomas Groh</td>
+ </tr>
+ <tr>
+ <td>.</td>
+ <td>thw</td>
+ <td>Thomas Weise</td>
+ </tr>
</table>
</section>
<section id="Incubation+work+items">
@@ -212,12 +231,6 @@
<td>If request from outside Apache to enter an existing Apache project,
then post a message to that project for them to decide on acceptance.</td>
</tr>
- <tr>
- <td></td>
- <td>If request from anywhere to become a stand-alone PMC, then assess the
- fit with the ASF, and create the lists and modules under the
- incubator address/module names if accepted.</td>
- </tr>
</table>
</section>
<section id="Infrastructure">
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/carbondata.xml
----------------------------------------------------------------------
diff --git a/content/projects/carbondata.xml b/content/projects/carbondata.xml
index d89c4dd..dbcd06c 100644
--- a/content/projects/carbondata.xml
+++ b/content/projects/carbondata.xml
@@ -18,7 +18,12 @@
<title>News</title>
<ul>
<li>2016-06-02 Project enters incubation.</li>
- <li>2016-08-27 First Apache CarbonData 0.1.0-incubating release!</li>
+ <li>2016-06-05 JIRA, mailing liss, git created.</li>
+ <li>2016-07-16 Add two new committers: Ravindra, Venkata Ramana.</li>
+ <li>2016-08-27 First Apache CarbonData 0.1.0-incubating released.</li>
+ <li>2016-10-10 Apache CarbonData 0.1.1-incubating released.</li>
+ <li>2016-10-24 Add one new committer: Kumar Vishal.</li>
+ <li>2016-11-20 Apache CarbonData 0.2.0-incubating released.</li>
</ul>
</section>
<section id="Project+info">
@@ -30,7 +35,14 @@
<th>reference</th>
</tr>
<tr>
- <td>Website</td>
+ <td>Website</td>
+ <td>www</td>
+ <td id="www">
+ <a href="http://carbondata.incubator.apache.org">http://carbondata.incubator.apache.org</a>
+ </td>
+ </tr>
+ <tr>
+ <td>Wiki</td>
<td>wiki</td>
<td>
<a href="https://cwiki.apache.org/confluence/display/CARBONDATA">https://cwiki.apache.org/confluence/display/CARBONDATA</a>
@@ -86,7 +98,7 @@
<td>Uma Maheswara Rao G</td>
</tr>
<tr>
- <td>Committers</td>
+ <td>PPMC/Committers</td>
<td>chenliang613</td>
<td>Liang Chen</td>
</tr>
@@ -107,7 +119,7 @@
</tr>
<tr>
<td>.</td>
- <td></td>
+ <td>jihongma</td>
<td>Jenny MA</td>
</tr>
<tr>
@@ -126,7 +138,7 @@
<td>Jarray Qiuheng</td>
</tr>
<tr>
- <td>.</td>
+ <td>Committers</td>
<td>ravipesala</td>
<td>Ravindra Pesala</td>
</tr>
@@ -135,6 +147,11 @@
<td>gvramana</td>
<td>Venkata Gollamudi</td>
</tr>
+ <tr>
+ <td>.</td>
+ <td>kumarvishal09</td>
+ <td>Kumar Vishal</td>
+ </tr>
</table>
</section>
<section id="Incubation+work+items">
@@ -160,22 +177,16 @@
trademarked for an existing software product.</td>
</tr>
<tr>
- <td></td>
+ <td>2016-06-02</td>
<td>If request from an existing Apache project to adopt an external
package, then ask the Apache project for the SVN module and mail
address names.</td>
</tr>
<tr>
- <td></td>
+ <td>2016-06-02</td>
<td>If request from outside Apache to enter an existing Apache project,
then post a message to that project for them to decide on acceptance.</td>
</tr>
- <tr>
- <td></td>
- <td>If request from anywhere to become a stand-alone PMC, then assess the
- fit with the ASF, and create the lists and modules under the
- incubator address/module names if accepted.</td>
- </tr>
</table>
</section>
<section id="Infrastructure">
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/commonsrdf.xml
----------------------------------------------------------------------
diff --git a/content/projects/commonsrdf.xml b/content/projects/commonsrdf.xml
index 38b80c4..00f727f 100644
--- a/content/projects/commonsrdf.xml
+++ b/content/projects/commonsrdf.xml
@@ -10,6 +10,7 @@
<title>CommonsRDF Project Incubation Status</title>
<p>This page tracks the project status, incubator-wise. For more general
project status, look on the project website.</p>
+ <p><span class='graduated'>The CommonsRDF project graduated on 2016-11-28</span></p>
</section>
<section id="Description">
<title>Description</title>
@@ -23,21 +24,18 @@
<title>News</title>
<ul>
<li>2015-03-06 Project enters incubation.</li>
- <li>2015-05-17 CommonsRDF 0.1-incubating released</li>
+ <li>2015-05-17 CommonsRDF 0.1.0-incubating released</li>
+ <li>2016-05-24 CommonsRDF 0.2.0-incubating released</li>
+ <li>2016-11-15 CommonsRDF 0.3.0-incubating released</li>
+ <li>2016-11-28 CommonsRDF graduated as a sub-project of Apache Commons</li>
</ul>
</section>
<section id="Project+info">
<title>Project info</title>
<ul>
- <li>TODO: link to the page(s) that tell how to participate (Website,Mailing
- lists,Bug tracking,Source code)</li>
+ <li>The podling site is at <a href="http://commonsrdf.incubator.apache.org/">commonsrdf.incubator.apache.org</a>.</li>
+ <li><a href="https://github.com/apache/incubator-commonsrdf/blob/ab7afbfe5f883f095c2da9ea6532019040836f45/MATURITY.md">Project Maturity Assessment</a></li>
</ul>
- <ul>
- <li>TODO: link to the project status file (Committers,non-incubation action
- items,project resources, etc)</li>
- </ul>
- <p>If the project website and code repository are not yet setup, use the
- following table:</p>
<table>
<tr>
<th>item</th>
@@ -158,6 +156,8 @@
<li><a href="http://wiki.apache.org/incubator/September2015">September2015</a></li>
<li><a href="http://wiki.apache.org/incubator/December2015">December2015</a></li>
<li><a href="http://wiki.apache.org/incubator/March2016">March2016</a></li>
+ <li><a href="http://wiki.apache.org/incubator/June2016">June2016</a></li>
+ <li><a href="http://wiki.apache.org/incubator/September2016">September2016</a></li>
</ul>
</section>
<section id="Incubation+work+items">
@@ -349,23 +349,38 @@
<title>Collaborative Development</title>
<ul>
<li>Have all of the active long-term volunteers been identified and
- acknowledged as committers on the project?
+ acknowledged as committers on the project?
+ <strong>Yes, see
+ <a href="https://commons.apache.org/proper/commons-rdf/team-list.html">project team</a></strong>
</li>
<li>Are there three or more independent committers? (The legal definition
of independent is long and boring, but basically it means that there
is no binding relationship between the individuals, such as a shared
employer, that is capable of overriding their free will as
- individuals, directly or indirectly.)</li>
- <li>Are project decisions being made in public by the committers?</li>
+ individuals, directly or indirectly.)
+ <strong>Yes, the committers are not affiliated outside ASF</strong>
+ </li>
+ <li>Are project decisions being made in public by the committers?
+ <strong>Yes, decisions made on
+ <a href="https://lists.apache.org/list.html?dev@commonsrdf.apache.org">dev@commonsrdf</a>
+ (now <a href="https://lists.apache.org/list.html?dev@commons.apache.org">dev@commons</a>)
+ </strong>
+ </li>
<li>Are the decision-making guidelines published and agreed to by all of
- the committers?</li>
+ the committers?
+ <strong>Follows
+ <a href="https://wiki.apache.org/commons/CommonsEtiquette">Apache Commons decision-making process</a>
+ </strong>
+ </li>
</ul>
</section>
<section id="Licensing+awareness">
<title>Licensing awareness</title>
<ul>
<li>Are all licensing, trademark, credit issues being taken care of and
- acknowleged by all committers?</li>
+ acknowleged by all committers?
+ <strong>Yes, see <a href="https://github.com/apache/incubator-commonsrdf/blob/ab7afbfe5f883f095c2da9ea6532019040836f45/MATURITY.md">Project Maturity Assessment</a></strong>
+ </li>
</ul>
</section>
<section id="Project+Specific">
@@ -383,7 +398,9 @@
<section id="Organizational+acceptance+of+responsibility+for+the+project">
<title>Organizational acceptance of responsibility for the project</title>
<ul>
- <li>If graduating to an existing PMC, has the PMC voted to accept it?</li>
+ <li>If graduating to an existing PMC, has the PMC voted to accept it?
+ <strong>Yes, <a href="https://lists.apache.org/thread.html/e5817369e5e713183efcac0ba54d1a7dac6a69e718b32d94b7fbe535@%3Cdev.commons.apache.org%3E">accepted by Commons PMC</a></strong>
+ </li>
<li>If graduating to a new PMC, has the board voted to accept it?</li>
</ul>
</section>
@@ -391,7 +408,9 @@
<title>Incubator sign-off</title>
<ul>
<li>Has the Incubator decided that the project has accomplished all of
- the above tasks?</li>
+ the above tasks?
+ <strong>Graduation was <a href="https://lists.apache.org/thread.html/64ddd50681f6ea6e9fb8c3e5b2b01644d1367ddc39cf2ecb48956b45@%3Cdev.commonsrdf.apache.org%3E">accepted by Incubator PMC</a></strong>
+ </li>
</ul>
</section>
</section>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/eagle.xml
----------------------------------------------------------------------
diff --git a/content/projects/eagle.xml b/content/projects/eagle.xml
index 5f7a7ee..ce9fdb4 100644
--- a/content/projects/eagle.xml
+++ b/content/projects/eagle.xml
@@ -21,6 +21,7 @@
<section id="News">
<title>News</title>
<ul>
+ <li>2016-11-15 Add one new committer: Jijun Tang. </li>
<li>2016-10-12 start graduation discussion and steps. </li>
<li>2016-09-05 Add one new committer: Jinhu Wu. </li>
<li>2016-07-21 Apache Eagle 0.4.0-incubating released.</li>
@@ -188,17 +189,17 @@
<td>Jinhu Wu</td>
</tr>
<tr>
- <td>Extra</td>
- <td>.</td>
<td>.</td>
+ <td>jjtang</td>
+ <td>Jijun Tang</td>
</tr>
</table>
</section>
<section id="Incubation+status+reports">
<title>Incubation status reports</title>
<ul>
- <li><a href="https://wiki.apache.org/incubator/July2016">July 2016</a></li>
- <li><a href="https://wiki.apache.org/incubator/June2016">June 2016</a></li>
+ <li><a href="https://wiki.apache.org/incubator/November2016">November 2016</a></li>
+ <li><a href="https://wiki.apache.org/incubator/August2016">August 2016</a></li>
<li><a href="https://wiki.apache.org/incubator/May2016">May 2016</a></li>
<li><a href="https://wiki.apache.org/incubator/February2016">February 2016</a></li>
<li><a href="https://wiki.apache.org/incubator/January2016">January 2016</a></li>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/geode.xml
----------------------------------------------------------------------
diff --git a/content/projects/geode.xml b/content/projects/geode.xml
index f06c097..3877929 100644
--- a/content/projects/geode.xml
+++ b/content/projects/geode.xml
@@ -9,6 +9,8 @@
<title>Geode Project Incubation Status</title>
<p>This page tracks the project status, incubator-wise. For more general
project status, look on the project website.</p>
+ <p><strong>THIS WEBSITE IS NO LONGER MAINTAINED!</strong></p>
+ <p><span class='graduated'>The Geode project graduated on 2016-11-16</span></p>
</section>
<section id="Description">
<title>Description</title>
@@ -35,6 +37,7 @@
<li>2015-09-29 Software Grant Agreement (SGA) from Pivotal for Apache Geode (incubating) documentation.</li>
<li>2016-10-25 Apache Geode 1.0.0-incubating release.</li>
<li>2016-10-25 Apache Geode graduation discussion started.</li>
+ <li>2016-11-16 Apache Geode graduation resolution passed by ASF Board</li>
</ul>
</section>
<section id="Project+info">
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/gossip.xml
----------------------------------------------------------------------
diff --git a/content/projects/gossip.xml b/content/projects/gossip.xml
index f86b0c9..7d9c4c0 100644
--- a/content/projects/gossip.xml
+++ b/content/projects/gossip.xml
@@ -79,13 +79,13 @@
</tr>
<tr>
<td>.</td>
- <td>busbey</td>
- <td>Sean Busbey</td>
+ <td>elserj</td>
+ <td>Josh Elser</td>
</tr>
<tr>
<td>.</td>
- <td>elserj</td>
- <td>Josh Elser</td>
+ <td>drew</td>
+ <td>Drew Farris</td>
</tr>
<tr>
<td>Committers</td>
http://git-wip-us.apache.org/repos/asf/incubator/blob/e1a75080/content/projects/griffin.xml
----------------------------------------------------------------------
diff --git a/content/projects/griffin.xml b/content/projects/griffin.xml
new file mode 100644
index 0000000..9bce0d7
--- /dev/null
+++ b/content/projects/griffin.xml
@@ -0,0 +1,353 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+
+ <title>Griffin Incubation Status Template</title>
+ <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+ </properties>
+ <body>
+ <section id="Griffin+Project+Incubation+Status">
+ <title>Griffin Project Incubation Status</title>
+ <p>This page tracks the project status, incubator-wise. For more general
+ project status, look on the project website.</p>
+ </section>
+ <section id="Description">
+ <title>Description</title>
+ <p>The Griffin is a open source Data Quality solution for distributed data systems at any scale in both streaming or batch data context.</p>
+ </section>
+ <section id="News">
+ <title>News</title>
+ <ul>
+ <li>2016-12-05 Project enters incubation.</li>
+ </ul>
+ </section>
+ <section id="Project+info">
+ <title>Project info</title>
+ <ul>
+ <li>link to the main website</li>
+ </ul>
+ <ul>
+ <li>link to the page(s) that tell how to participate (Website,Mailing
+ lists,Bug tracking,Source code)</li>
+ </ul>
+ <ul>
+ <li>link to the project status file (Committers,non-incubation action
+ items,project resources, etc)</li>
+ </ul>
+ <p>If the project website and code repository are not yet setup, use the
+ following table:</p>
+ <table>
+ <tr>
+ <th>item</th>
+ <th>type</th>
+ <th>reference</th>
+ </tr>
+ <tr>
+ <td>Website</td>
+ <td>www</td>
+ <td id="www">
+ <a href="http://Griffin.incubator.apache.org/">http://griffin.incubator.apache.org/</a>
+ </td>
+ </tr>
+ <tr>
+ <td>.</td>
+ <td>wiki</td>
+ <td>.</td>
+ </tr>
+ <tr>
+ <td>Mailing list</td>
+ <td>dev</td>
+ <td id="mail-dev"><code>dev</code><code>@</code><code>griffin.incubator.apache.org</code></td>
+ </tr>
+ <tr>
+ <td>.</td>
+ <td>commits</td>
+ <td id="mail-commits"><code>commits</code><code>@</code><code>griffin.incubator.apache.org</code></td>
+ </tr>
+ <tr>
+ <td>Bug tracking</td>
+ <td>.</td>
+ <td id="tracker">
+ [ provide expected link ]
+ </td>
+ </tr>
+ <tr>
+ <td>Source code</td>
+ <td>GIT</td>
+ <td id="git">
+ <a href="git://git.apache.org/incubator-griffin.git">git://git.apache.org/incubator-griffin.git</a>
+ </td>
+ </tr>
+ <tr>
+ <td>Mentors</td>
+ <td>hsaputra</td>
+ <td>Henry Saputra</td>
+ </tr>
+ <tr>
+ <td>.</td>
+ <td>kaspersor</td>
+ <td>Kasper S�rensen</td>
+ </tr>
+ <tr>
+ <td>.</td>
+ <td>umamahesh</td>
+ <td>Uma Maheswara Rao Gangumalla</td>
+ </tr>
+ <tr>
+ <td>.</td>
+ <td>lresende</td>
+ <td>Luciano Resende</td>
+ </tr>
+ <tr>
+ <td>Committers</td>
+ <td>.</td>
+ <td>.</td>
+ </tr>
+ <tr>
+ <td>Extra</td>
+ <td>.</td>
+ <td>.</td>
+ </tr>
+ </table>
+ </section>
+ <section id="Incubation+status+reports">
+ <title>Incubation status reports</title>
+ <ul>
+ <li>none yet</li>
+ </ul>
+ </section>
+ <section id="Incubation+work+items">
+ <title>Incubation work items</title>
+ <section id="Project+Setup">
+ <title>Project Setup</title>
+ <p>This is the first phase on incubation, needed to start the project at Apache.</p>
+ <p>
+ <em>Item assignment is shown by the Apache id.</em>
+ <em>Completed tasks are shown by the completion date (YYYY-MM-dd).</em>
+ </p>
+ <section id="Identify+the+project+to+be+incubated">
+ <title>Identify the project to be incubated</title>
+ <table>
+ <tr>
+ <th>date</th>
+ <th>item</th>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Make sure that the requested project name does not already exist. <a href="http://www.apache.org/foundation/marks/naming.html">Please follow
+ the guide to ensure a suitable project/product name.</a></td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>If request from an existing Apache project to adopt an external
+ package, then ask the Apache project for the SVN module and mail
+ address names.</td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>If request from outside Apache to enter an existing Apache project,
+ then post a message to that project for them to decide on acceptance.</td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>If request from anywhere to become a stand-alone PMC, then assess the
+ fit with the ASF, and create the lists and modules under the
+ incubator address/module names if accepted.</td>
+ </tr>
+ </table>
+ </section>
+ <section id="Infrastructure">
+ <title>Infrastructure</title>
+ <table>
+ <tr>
+ <th>date</th>
+ <th>item</th>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Ask infrastructure to set up and archive mailing lists.</td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Ask infrastructure to create source repository modules
+ and grant the committers karma.</td>
+ <!-- Use https://infrahelp.apache.org/ -->
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Ask infrastructure to set up issue tracker (JIRA, Bugzilla).</td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Ask infrastructure to set up wiki (Confluence, Moin).</td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Migrate the project to our infrastructure.</td>
+ </tr>
+ </table>
+ </section>
+ <section id="Interim+responsibility">
+ <title>Mentor-related responsibility/oversight</title>
+ <table>
+ <tr>
+ <th>date</th>
+ <th>item</th>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Subscribe all Mentors on the pmc and general lists.</td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Give all Mentors access to the incubator SVN repository.
+ (to be done by the Incubator PMC chair or an Incubator PMC
+ Member wih karma for the authorizations file)</td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Tell Mentors to track progress in the file
+ 'incubator/projects/{project.name}.html'</td>
+ </tr>
+ </table>
+ </section>
+ <section id="Copyright">
+ <title>Copyright</title>
+ <table>
+ <tr>
+ <th>date</th>
+ <th>item</th>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Check and make sure that the papers that transfer rights to the ASF
+ been received. It is only necessary to transfer rights for the
+ package, the core code, and any new code produced by the project.
+ </td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Check and make sure that the files that have been donated have been
+ updated to reflect the new ASF copyright.</td>
+ </tr>
+ </table>
+ </section>
+ <section id="Verify+distribution+rights">
+ <title>Verify distribution rights</title>
+ <table>
+ <tr>
+ <th>date</th>
+ <th>item</th>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Check and make sure that for all code included with the distribution
+ that is not under the Apache license, we have the right to combine
+ with Apache-licensed code and redistribute.
+ </td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Check and make sure that all source code distributed by the project
+ is covered by one or more of the following approved licenses: Apache,
+ BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially
+ the same terms.</td>
+ </tr>
+ </table>
+ </section>
+ <section id="Establish+a+list+of+active+committers">
+ <title>Establish a list of active committers</title>
+ <table>
+ <tr>
+ <th>date</th>
+ <th>item</th>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Check that all active committers have submitted a contributors
+ agreement.</td>
+ <!-- check http://people.apache.org/committer-index.html -->
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Add all active committers in the relevant section above.</td>
+ </tr>
+ <tr>
+ <td>....-..-..</td>
+ <td>Ask root for the creation of committers' accounts in
+ LDAP.</td>
+ <!-- this may happen automatically as their ICLAs are filed.
+ If you are using git source control, ensure that all
+ committers are members of the 'incubator' group. -->
+ </tr>
+ </table>
+ </section>
+ <section id="Project+specific">
+ <title>Project specific</title>
+ <p>
+ <em>Add project specific tasks here.</em>
+ </p>
+ </section>
+ </section>
+ <section id="Incubation">
+ <title>Incubation</title>
+ <p>These action items have to be checked for during the whole incubation process.</p>
+ <p>
+ <em>These items are not to be signed as done during incubation, as they
+ may change during incubation.</em>
+ <em>They are to be looked into and described in the status reports and
+ completed in the request for incubation signoff.</em>
+ </p>
+ <section id="Collaborative+Development">
+ <title>Collaborative Development</title>
+ <ul>
+ <li>Have all of the active long-term volunteers been identified and
+ acknowledged as committers on the project?
+ </li>
+ <li>Are there three or more independent committers? (The legal definition
+ of independent is long and boring, but basically it means that there
+ is no binding relationship between the individuals, such as a shared
+ employer, that is capable of overriding their free will as
+ individuals, directly or indirectly.)</li>
+ <li>Are project decisions being made in public by the committers?</li>
+ <li>Are the decision-making guidelines published and agreed to by all of
+ the committers?</li>
+ </ul>
+ </section>
+ <section id="Licensing+awareness">
+ <title>Licensing awareness</title>
+ <ul>
+ <li>Are all licensing, trademark, credit issues being taken care of and
+ acknowleged by all committers?</li>
+ </ul>
+ </section>
+ <section id="Project+Specific">
+ <title>Project Specific</title>
+ <p>
+ <em>Add project specific tasks here.</em>
+ </p>
+ </section>
+ </section>
+ <section id="Exit">
+ <title>Exit</title>
+ <p>
+ <em>Things to check for before voting the project out.</em>
+ </p>
+ <section id="Organizational+acceptance+of+responsibility+for+the+project">
+ <title>Organizational acceptance of responsibility for the project</title>
+ <ul>
+ <li>If graduating to an existing PMC, has the PMC voted to accept it?</li>
+ <li>If graduating to a new PMC, has the board voted to accept it?</li>
+ </ul>
+ </section>
+ <section id="Incubator+sign-off">
+ <title>Incubator sign-off</title>
+ <ul>
+ <li>Has the Incubator decided that the project has accomplished all of
+ the above tasks?</li>
+ </ul>
+ </section>
+ </section>
+ </section>
+ </body>
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org