incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r370716 [2/11] - in /incubator/public/trunk/site/xdocs2: ./ guides/ incubation/ ip-clearance/ learn/ projects/ projects/agila/ projects/geronimo/
Date Fri, 20 Jan 2006 03:11:54 GMT
Added: incubator/public/trunk/site/xdocs2/incubation/Roles_and_Responsibilities.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/incubation/Roles_and_Responsibilities.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/incubation/Roles_and_Responsibilities.xml (added)
+++ incubator/public/trunk/site/xdocs2/incubation/Roles_and_Responsibilities.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,299 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Roles_and_ Responsibilities
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Roles+and+Responsibilities" name="Roles and Responsibilities">
+      <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>
+      <subsection id="Incubator+Project+Management+Committee+%28PMC%29" name="Incubator Project Management Committee (PMC)">
+        <p>(From the resolution that created the Incubator Project - see
+http://incubator.apache.org/resolution.html)
+</p>
+        <p>The Incubator PMC 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>successfully exit 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>
+      </subsection>
+      <subsection id="Chair+of+the+Incubator+PMC" name="Chair of the Incubator PMC">
+        <p>The person appointed by the Board of Directors to have primary
+responsibility for oversight of the Incubator Project, its policies,
+and policy implementation.
+</p>
+      </subsection>
+      <subsection id="Candidate" name="Candidate">
+        <p>A Candidate is a project that is 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
+it is expected that the Champion is a member of the affiliated
+project, and 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 exit
+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>
+      </subsection>
+      <subsection id="Champion" name="Champion">
+        <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>Where the Champion is not a Member of the Foundation (i.e. is an
+Officer only), the Champion shall be a member of the PMC of the
+Sponsor.
+</p>
+        <p>While the Champion has no formal responsibility within the Incubation
+process (other than to review and comment on a Candidate's proposal
+within the Sponsor), it is expected that they will play an active
+role. A lack of interest on the part of a Champion may be seen by the
+Incubator PMC as a negative indicator during the course of incubation.
+</p>
+      </subsection>
+      <subsection id="Sponsor" name="Sponsor">
+        <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>The Board of the Apache Software Foundation. In this case, it is
+expected that the candidate would become a TLP on successful
+completion of Incubation.
+</li>
+          <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 board (and the candidate will be a TLP) or another
+project.
+</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 Mentor. The Mentor is the individual
+accountable to the Incubator PMC for ensuring the incubation process
+is correctly followed. In cases where the Mentor is not fulfilling
+their responsibilities, the Sponsor (in particular its Chair) will be
+expected to remedy the situation.
+</p>
+        <subsection id="Responsibilities+of+the+Sponsor" name="Responsibilities of the Sponsor">
+          <ul>
+            <li>to provide initial approval for a Canidate to be accepted as a Podling
+</li>
+            <li>to nominate a Mentor for the incubation process
+</li>
+          </ul>
+        </subsection>
+      </subsection>
+      <subsection id="Mentor" name="Mentor">
+        <p>A Mentor is a role undertaken by a permanent member of the Apache
+Software Foundation and is chosen by the Sponsor to actively lead in
+the discharge of their duties (listed above). Upon acceptance by the
+Incubator PMC, the Mentor automatically becomes a member of the
+Incubator PMC. A Mentor has specific responsibilities towards the
+Incubator PMC, the Sponsor and towards the members of the assigned
+Podling.
+</p>
+        <subsection id="Responsibilities+towards+Podling+Members" name="Responsibilities towards Podling Members">
+          <ul>
+            <li>to ensure that Incubator PMC decisions and/or issue are dealt with in
+a timely manner and ensure that decisions or resolutions effecting
+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>
+        </subsection>
+        <subsection id="Responsibilities+towards+the+Incubator+PMC" name="Responsibilities towards the Incubator PMC">
+          <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>
+        </subsection>
+        <subsection id="Committers" name="Committers">
+          <p>The candidate shall declare an initial set of committers. On
+acceptance of a candidate project, the assigned Mentor shall be given
+access to the Podling's cvs repository for the duration of the
+incubation process. This is to allow the Mentor 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 Mentor must earn them as would any other
+potential new committer. In some cases, the Mentor 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 Mentor informed - he/she is 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 ASF Board.
+</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>
+        </subsection>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/incubation/Roles_and_Responsibilities.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/index.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/index.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/index.xml (added)
+++ incubator/public/trunk/site/xdocs2/index.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Apache Incubator Project
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/><!--
+
+    <meta content="The Apache Incubator Project" name="DC.Creator"/>-->
+
+  </properties>
+  <body>
+    <section id="What+Is+It%3F" name="What Is It?">
+      <p>The Incubator project was created in October of 2002 to provide an
+entry path to the Apache Software Foundation for projects and
+codebases wishing to become part of the Foundation's efforts. Code
+donations from external organisations and existing external projects
+wishing to move to Apache will enter through the Incubator.
+</p>
+      <p>A large part of the Incubator's effort will be devoted to providing
+documentation on how the Foundation works, and how to get things done
+within its framework. As a consequence, it is expected that the
+Incubator will also become a reference for new contributors to any of
+the Apache projects.
+</p>
+      <p>Since the Incubator project is one of the primary gateways into
+Apache involvement, a lot of the documentation about the structural
+and philosophical details of the Foundation will probably be
+prototyped and developed right here. When they seem to accurately
+reflect reality and cover the information they should, they'll
+probably be moved up to the Foundation's main Web site.
+</p>
+    </section>
+    <section id="The+Apache+Software+Foundation" name="The Apache Software Foundation">
+      <p>The Apache Software Foundation (ASF) is a non-profit (USA IRS
+501(c)(3) compliant) membership organisation. You can find out more
+about the ASF proper at the Foundation's
+
+        <a href="http://www.apache.org/foundation/">main site
+</a>.
+
+      </p>
+      <p>The main unit of participation in the ASF is the individual.
+Individuals may have one or more roles in the ASF; you can find out
+more about them
+
+        <a href="http://www.apache.org/foundation/roles.html">here
+</a>.
+
+      </p>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/apr-jlibtool.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/apr-jlibtool.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/apr-jlibtool.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/apr-jlibtool.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>apr-jlibtool
+</title>
+  </properties>
+  <body>
+    <section id="jlibtool+Codebase+IP+Clearance+Status" name="jlibtool Codebase IP Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>A C-based replacement for libtool. One C file intended to be dropped
+in to the repository. The last version I created is at:
+</p>
+      <p>http://www.apache.org/~jerenkrantz/jlibtool.c
+</p>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Which PMC will be responsible for the code
+</li>
+      </ul>
+      <p>APR
+</p>
+      <ul>
+        <li>Into which existing project/module
+</li>
+      </ul>
+      <p>apr CVS repository under the build/ directory.
+</p>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-07-08
+</td>
+            <td>If applicable, make sure that any associated name does not already
+exist and check www.nameprotect.com to be sure that the name is not
+already trademarked for an existing software product.
+</td>
+          </tr>
+        </table>
+      </subsection>
+      <subsection id="Copyright" name="Copyright">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-07-08
+</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>
+        </table>
+        <p>(A software grant was faxed by Justin to Jim on 7/8/2004.)
+</p>
+        <table>
+          <tr>
+            <td>2004-07-08
+</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>
+        <p>(The copyright and license will be updated when it is committed.)
+</p>
+      </subsection>
+      <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-07-08
+</td>
+            <td>Check that all active committers have a signed CLA on record.
+</td>
+          </tr>
+        </table>
+        <p>(Yes.)
+</p>
+        <table>
+          <tr>
+            <td>2004-07-08
+</td>
+            <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+          </tr>
+        </table>
+        <p>(No corporate CLA needed.)
+</p>
+        <table>
+          <tr>
+            <td>2004-07-08
+</td>
+            <td>Check and make sure that for all items 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>
+        </table>
+        <p>(The code was originally under the Apache 1.1 license - but will be
+relicensed to ALv2.)
+</p>
+        <table>
+          <tr>
+            <td>2004-07-08
+</td>
+            <td>Check and make sure that all items depended upon 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>
+        <p>(jlibtool has no external dependencies.)
+</p>
+      </subsection>
+    </section>
+    <section id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+      <ul>
+        <li>Has the receiving PMC voted to accept it?
+</li>
+      </ul>
+      <p>Yes, via dev@apr.
+</p>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/apr-jlibtool.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1016-ibm-daytrader.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1016-ibm-daytrader.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1016-ibm-daytrader.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1016-ibm-daytrader.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,157 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Intellectual Property (IP) Clearance Template
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Apache+Geronimo+Codebase+IP+Clearance+Status" name="Apache Geronimo Codebase IP Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>Donation of code DayTrader application
+
+        <br/>
+      </p>
+      <p>
+        <a href="http://issues.apache.org/jira/browse/GERONIMO-1016">http://issues.apache.org/jira/browse/GERONIMO-1016
+
+          <br/>
+        </a>
+      </p>
+      <br/>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Which PMC will be responsible for the code  : Apache Geronimo
+
+          <br/>
+        </li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module : regular Apache SVN
+</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2005-09-20
+
+              <br/>
+            </td>
+            <td>If applicable, make sure that any associated name does not already
+exist and check www.nameprotect.com to be sure that the name is not
+already trademarked for an existing software product.
+</td>
+          </tr>
+        </table>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-11-03
+</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>2005-09-20
+</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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-09-20
+</td>
+              <td>Check that all active committers have a signed CLA on record.
+</td>
+            </tr>
+            <tr>
+              <td>2005-09-20
+</td>
+              <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+            </tr>
+            <tr>
+              <td>2005-09-20
+</td>
+              <td>Check and make sure that for all items 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>2005-09-20
+</td>
+              <td>Check and make sure that all items depended upon 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>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </subsection>
+      </subsection>
+      <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+        <ul>
+          <li>Has the receiving PMC voted to accept it?  Yes
+</li>
+        </ul>
+        <u>
+          <a href="http://mail-archives.apache.org/mod_mbox/geronimo-dev/200509.mbox/%3c4B3CC3C8-07EA-4155-9963-649DEC6CCDB9@apache.org%3e">http://mail-archives.apache.org/mod_mbox/geronimo-dev/200509.mbox/%3c4
+3CC3C8-07EA-4155-9963-649DEC6CCDB9@apache.org%3e
+
+            <br/>
+          </a>
+          <br/>
+        </u>
+        <a href="http://mail-archives.apache.org/mod_mbox/geronimo-dev/200509.mbox/%3c4B3CC3C8-07EA-4155-9963-649DEC6CCDB9@apache.org%3e">http://mail-archives.apache.org/mod_mbox/geronimo-dev/200509.mbox/%3c4
+3CC3C8-07EA-4155-9963-649DEC6CCDB9@apache.org%3e
+
+          <br/>
+        </a>
+        <br/>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1016-ibm-daytrader.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1111-trifork-initial.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1111-trifork-initial.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1111-trifork-initial.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1111-trifork-initial.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,156 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Intellectual Property (IP) Clearance Template
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Apache+Geronimo+Codebase+IP+Clearance+Status" name="Apache Geronimo Codebase IP Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>Infrastructure code such as CORBA components, IO system and RMI
+binding.
+</p>
+      <p>
+        <a href="http://issues.apache.org/jira/browse/GERONIMO-1111">http://issues.apache.org/jira/browse/GERONIMO-1111
+
+          <br/>
+        </a>
+      </p>
+      <br/>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Which PMC will be responsible for the code  : Apache Geronimo
+
+          <br/>
+        </li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module : regular Apache SVN
+</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2005-10-27
+
+              <br/>
+            </td>
+            <td>If applicable, make sure that any associated name does not already
+exist and check www.nameprotect.com to be sure that the name is not
+already trademarked for an existing software product.
+</td>
+          </tr>
+        </table>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-10-27
+</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>2005-10-27
+</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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-10-27
+</td>
+              <td>Check that all active committers have a signed CLA on record.
+</td>
+            </tr>
+            <tr>
+              <td>2005-10-27
+</td>
+              <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+            </tr>
+            <tr>
+              <td>2005-10-27
+</td>
+              <td>Check and make sure that for all items 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>2005-10-27
+</td>
+              <td>Check and make sure that all items depended upon 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>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </subsection>
+      </subsection>
+      <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+        <ul>
+          <li>Has the receiving PMC voted to accept it?  Yes
+</li>
+        </ul>
+        <u>
+          <a href="http://mail-archives.apache.org/mod_mbox/geronimo-dev/200510.mbox/%3c1E40794F-06CA-4180-B533-70E02322F331@apache.org%3e">http://mail-archives.apache.org/mod_mbox/geronimo-dev/200510.mbox/%3c1
+40794F-06CA-4180-B533-70E02322F331@apache.org%3e
+
+            <br/>
+          </a>
+          <br/>
+        </u>
+        <a href="http://mail-archives.apache.org/mod_mbox/geronimo-dev/200510.mbox/%3c1E40794F-06CA-4180-B533-70E02322F331@apache.org%3e">http://mail-archives.apache.org/mod_mbox/geronimo-dev/200510.mbox/%3c1
+40794F-06CA-4180-B533-70E02322F331@apache.org%3e
+
+          <br/>
+        </a>
+        <br/>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1111-trifork-initial.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-762-ibm-console.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-762-ibm-console.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-762-ibm-console.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-762-ibm-console.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,154 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Intellectual Property (IP) Clearance Template
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Apache+Geronimo+Codebase+IP+Clearance+Status" name="Apache Geronimo Codebase IP Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>Donation of code for an administration console for the Apache
+Geronimo project.
+
+        <br/>
+      </p>
+      <p>
+        <a href="http://issues.apache.org/jira/browse/GERONIMO-762">http://issues.apache.org/jira/browse/GERONIMO-762
+
+          <br/>
+        </a>
+      </p>
+      <br/>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Which PMC will be responsible for the code  : Apache Geronimo
+
+          <br/>
+        </li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module : regular Apache SVN
+</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2005-07-14
+
+              <br/>
+            </td>
+            <td>If applicable, make sure that any associated name does not already
+exist and check www.nameprotect.com to be sure that the name is not
+already trademarked for an existing software product.
+</td>
+          </tr>
+        </table>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-11-03
+</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>2005-07-14
+</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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-07-14
+</td>
+              <td>Check that all active committers have a signed CLA on record.
+</td>
+            </tr>
+            <tr>
+              <td>2005-07-14
+</td>
+              <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+            </tr>
+            <tr>
+              <td>2005-07-14
+</td>
+              <td>Check and make sure that for all items 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>2005-07-14
+</td>
+              <td>Check and make sure that all items depended upon 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>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </subsection>
+      </subsection>
+      <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+        <ul>
+          <li>Has the receiving PMC voted to accept it?  Yes
+</li>
+        </ul>
+        <u>
+          <a href="http://mail-archives.apache.org/mod_mbox/geronimo-dev/200507.mbox/%3cPine.LNX.4.58.0507141258360.9306@saturn.opentools.org%3e">http://mail-archives.apache.org/mod_mbox/geronimo-dev/200507.mbox/%3cP
+ne.LNX.4.58.0507141258360.9306@saturn.opentools.org%3e
+</a>
+          <br/>
+        </u>
+        <a href="http://mail-archives.apache.org/mod_mbox/geronimo-dev/200507.mbox/%3cPine.LNX.4.58.0507141258360.9306@saturn.opentools.org%3e">http://mail-archives.apache.org/mod_mbox/geronimo-dev/200507.mbox/%3cP
+ne.LNX.4.58.0507141258360.9306@saturn.opentools.org%3e
+</a>
+        <br/>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-762-ibm-console.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-875-ibm-eclipse.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-875-ibm-eclipse.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-875-ibm-eclipse.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-875-ibm-eclipse.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,157 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Intellectual Property (IP) Clearance Template
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Apache+Geronimo+Codebase+IP+Clearance+Status" name="Apache Geronimo Codebase IP Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>Donation of code for Eclipse Geronimo Server Adapter
+
+        <br/>
+      </p>
+      <p>
+        <a href="http://issues.apache.org/jira/browse/GERONIMO-875">http://issues.apache.org/jira/browse/GERONIMO-875
+
+          <br/>
+        </a>
+      </p>
+      <br/>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Which PMC will be responsible for the code  : Apache Geronimo
+
+          <br/>
+        </li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module : regular Apache SVN
+</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2005-08-16
+
+              <br/>
+            </td>
+            <td>If applicable, make sure that any associated name does not already
+exist and check www.nameprotect.com to be sure that the name is not
+already trademarked for an existing software product.
+</td>
+          </tr>
+        </table>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-11-03
+</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>2005-08-16
+</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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-08-16
+</td>
+              <td>Check that all active committers have a signed CLA on record.
+</td>
+            </tr>
+            <tr>
+              <td>2005-08-16
+</td>
+              <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+            </tr>
+            <tr>
+              <td>2005-08-16
+</td>
+              <td>Check and make sure that for all items 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>2005-08-16
+</td>
+              <td>Check and make sure that all items depended upon 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>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </subsection>
+      </subsection>
+      <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+        <ul>
+          <li>Has the receiving PMC voted to accept it?  Yes
+</li>
+        </ul>
+        <u>
+          <a href="http://mail-archives.apache.org/mod_mbox/geronimo-dev/200508.mbox/%3cA9F96C0E-0626-4AAC-87A6-C376D3859168@apache.org%3e">http://mail-archives.apache.org/mod_mbox/geronimo-dev/200508.mbox/%3cA
+F96C0E-0626-4AAC-87A6-C376D3859168@apache.org%3e
+
+            <br/>
+          </a>
+          <br/>
+        </u>
+        <a href="http://mail-archives.apache.org/mod_mbox/geronimo-dev/200508.mbox/%3cA9F96C0E-0626-4AAC-87A6-C376D3859168@apache.org%3e">http://mail-archives.apache.org/mod_mbox/geronimo-dev/200508.mbox/%3cA
+F96C0E-0626-4AAC-87A6-C376D3859168@apache.org%3e
+
+          <br/>
+        </a>
+        <br/>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-875-ibm-eclipse.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-iiop.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-iiop.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-iiop.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-iiop.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,141 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Ip Clearance Template
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Geronimo+Corba%2FIIOP+Codebase+IP+Clearance+Status" name="Geronimo Corba/IIOP Codebase IP Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>The incoming codebase is a contribution of existing and original work
+for Apache Geronimo to begin providing the required functionality for
+IIOP and Corba support as required by the specifications implemented
+by Geronimo.  It will constitute a separate module in the Geronimo
+codebase.
+
+        <br/>
+      </p>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Apache Geronimo is the responsible PMC accepting this code, accepting
+into the main Geronimo codeline
+
+          <br/>
+        </li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2005-01-15
+</td>
+            <td>No unique name is being applied - it's an addition to existing
+Geronimo code
+
+              <br/>
+            </td>
+          </tr>
+        </table>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-01-15
+</td>
+              <td>Software grant from Sybase has been received for partial codebase,
+and ICLA from Mark DeLaFramier has been recieved for original work
+and patches
+</td>
+            </tr>
+            <tr>
+              <td>2005-01-15
+</td>
+              <td>Donated files have current-style copyright notice  "Copyright 2004
+The Apache Software Foundation or its licensors, as applicable."
+
+                <br/>
+              </td>
+            </tr>
+          </table>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-01-15
+</td>
+              <td>All committers have ICLA on file (geirm and adc)
+</td>
+            </tr>
+            <tr>
+              <td>2005-01-15
+
+                <br/>
+              </td>
+              <td>All items are under Apache license, and no new dependencies exist.
+
+                <br/>
+              </td>
+            </tr>
+            <tr>
+              <td>
+                <br/>
+              </td>
+              <td>
+                <br/>
+              </td>
+            </tr>
+            <tr>
+              <td>
+                <br/>
+              </td>
+              <td>
+                <br/>
+              </td>
+            </tr>
+          </table>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </subsection>
+      </subsection>
+      <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+        <ul>
+          <li>The Geronimo PMC has accepted this code
+
+            <br/>
+          </li>
+        </ul>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-iiop.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/index.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/index.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/index.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/index.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,141 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Intellectual property clearance
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/><!--
+
+    <meta content="The Apache Incubator Project" name="DC.Creator"/>-->
+
+  </properties>
+  <body>
+    <section id="" name="">
+      <p>One of the Incubator's roles is to ensure that proper attention is
+paid to intellectual property. From time to time, an external
+codebase is brought into the ASF that is not a separate
+
+        <a href="../projects/">incubating project
+</a>but still represents a substantial contribution that was not
+developed within the ASF's source control system. This is a short
+form of the Incubation checklist, designed to allow code to be
+imported with alacrity while still providing for oversight.
+
+      </p>
+      <p>This form is not for new projects. The intent is to simply help to
+ensure, and record, that due diligence (Software Grant, CLA, Corp
+CLA, license and dependencies) has been paid to the incoming code, so
+that it can be merged into an existing project/module.
+</p>
+      <p>The receiving PMC is responsible for doing the work. The Incubator is
+simply the repository of the needed information. Once a PMC directly
+checks-in a filled-out short form, everything is done.
+</p>
+      <p>All PMCs must handle incoming code in this way. Any code that was
+developed outside of the ASF SVN/CVS repository must be processed
+like this, even if the external developer is an ASF committer.
+</p>
+      <p>For new situations, use the
+
+        <a href="http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.html">template
+</a>and follow its instructions.
+
+      </p>
+      <table>
+        <tr>
+          <th colspan="1" rowspan="1">Clearance document
+</th>
+          <th colspan="1" rowspan="1">Receiving PMC
+</th>
+          <th colspan="1" rowspan="1">Date recorded
+</th>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
+            <a href="myfaces-tobago.html">myfaces-tobago
+</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache MyFaces
+</td>
+          <td colspan="1" rowspan="1">2005-12-20
+</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
+            <a href="geronimo-1111-trifork-initial.html">geronimo-1111-trifork-initial
+</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Geronimo
+</td>
+          <td colspan="1" rowspan="1">2005-10-27
+</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
+            <a href="geronimo-1016-ibm-daytrader.html">geronimo-1016-ibm-daytrader
+</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Geronimo
+</td>
+          <td colspan="1" rowspan="1">2005-09-20
+</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
+            <a href="geronimo-875-ibm-eclipse.html">geronimo-875-ibm-eclipse
+</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Geronimo
+</td>
+          <td colspan="1" rowspan="1">2005-08-16
+</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
+            <a href="geronimo-762-ibm-console.html">geronimo-762-ibm-console
+</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Geronimo
+</td>
+          <td colspan="1" rowspan="1">2005-07-14
+</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
+            <a href="geronimo-iiop.html">geronimo-iiop
+</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Geronimo
+</td>
+          <td colspan="1" rowspan="1">2005-01-15
+</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
+            <a href="apr-jlibtool.html">apr-jlibtool
+</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Portable Runtime (APR)
+</td>
+          <td colspan="1" rowspan="1">2004-07-08
+</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
+            <a href="portals-gluecode-jetspeed.html">portals-gluecode-jetspeed
+</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Portals
+</td>
+          <td colspan="1" rowspan="1">2004-06-27
+</td>
+        </tr>
+      </table>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/ip-clearance-template.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/ip-clearance-template.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/ip-clearance-template.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/ip-clearance-template.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,197 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>XYZ Codebase Intellectual Property (IP) Clearance Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Codebase+IP+Clearance+TEMPLATE" name="Codebase IP Clearance TEMPLATE">
+      <p>This document is the template for recording IP clearance on new
+codebases. Please store the completed document in this Incubator
+repository using a filename that reflects your project.
+</p>
+      <p>One of the Incubator's roles is to ensure that proper attention is
+paid to intellectual property. From time to time, an external
+codebase is brought into the ASF that is not a separate project, but
+still represents a substantial contribution that was not developed
+within the ASF's source control system. This is a short form of the
+Incubation checklist, designed to allow code to be imported with
+alacrity while still providing for oversight.
+</p>
+      <p>This form is not for new projects. The intent is to simply help to
+ensure, and record, that due diligence (Software Grant, CLA, Corp
+CLA, license and dependencies) has been paid to the incoming code, so
+that it can be merged into an existing project/module.
+</p>
+      <p>The receiving PMC is responsible for doing the work. The Incubator is
+simply the repository of the needed information. Once a PMC directly
+checks-in a filled-out short form, everything is done.
+</p>
+      <p>All PMCs must handle incoming code in this way. Any code that was
+developed outside of the ASF SVN repository must be processed like
+this, even if the external developer is an ASF committer.
+</p>
+      <p>What to do to set it up:
+</p>
+      <ul>
+        <li>copy this file and re-name it according to
+incubator/site-author/ip-clearance/${project-codebase}.html
+</li>
+        <li>add a row to the table at
+incubator/site-author/ip-clearance/index.html
+</li>
+        <li>make a snapshot of the source code available for review
+</li>
+      </ul>
+      <p>This file should not last long in place before it is moved to the
+successful incubation area. The sole purpose is to ensure that IP is
+cleared so that the codebase can be merged into the ASF SVN.
+</p>
+      <p>For this file:
+</p>
+      <ul>
+        <li>substitute the XYZ name with the real one
+</li>
+        <li>fill in the description
+</li>
+        <li>fill in the work items
+</li>
+        <li>remove this notice
+</li>
+        <li>set a proper "title" element for the html page
+</li>
+      </ul>
+      <p>When a work item is done, place the date in the supplied space.
+</p>
+      <p>
+        <em>On the first edit of this file, please delete this notice.
+</em>
+      </p>
+      <pre>-----8-&lt;---- cut here -------8-&lt;---- cut here -------8-&lt;---- cut here
+-------8-&lt;----
+</pre>
+    </section>
+    <section id="XYZ+Codebase+Intellectual+Property+%28IP%29+Clearance+Status" name="XYZ Codebase Intellectual Property (IP) Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>Describe the incoming codebase, including whether it is a large set
+of patches, new functional modules, etc.
+</p>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Which PMC will be responsible for the code
+</li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module
+</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>....-..-..
+</td>
+            <td>If applicable, make sure that any associated name does not already
+exist and check www.nameprotect.com to be sure that the name is not
+already trademarked for an existing software product.
+</td>
+          </tr>
+        </table>
+        <subsection id="Copyright" name="Copyright">
+          <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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>....-..-..
+</td>
+              <td>Check that all active committers have a signed CLA on record.
+</td>
+            </tr>
+            <tr>
+              <td>....-..-..
+</td>
+              <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+            </tr>
+            <tr>
+              <td>....-..-..
+</td>
+              <td>Check and make sure that for all items 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 items depended upon 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>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </subsection>
+      </subsection>
+      <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+        <ul>
+          <li>Has the receiving PMC voted to accept it?
+</li>
+        </ul>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/ip-clearance-template.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/myfaces-tobago.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/myfaces-tobago.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/myfaces-tobago.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/myfaces-tobago.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,132 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>MyFaces Tobago Codebase Intellectual Property (IP) Clearance Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="MyFaces+Tobago+Codebase+Intellectual+Property+%28IP%29+Clearance+Status" name="MyFaces Tobago Codebase Intellectual Property (IP) Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>Tobago is a JSF based web development architecture consisting of a
+well designed set of user interface components that will become part
+of MyFaces.
+</p>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Which PMC will be responsible for the code: Apache MyFaces PMC
+</li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module: Apache MyFaces
+</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>DONE
+</td>
+            <td>If applicable, make sure that any associated name does not already
+exist and check www.nameprotect.com to be sure that the name is not
+already trademarked for an existing software product.
+</td>
+          </tr>
+        </table>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>DONE-2005-10-17
+</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>DONE-2005-11-24
+</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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>DONE-2005-10-17
+</td>
+              <td>Check that all active committers have a signed CLA on record.
+</td>
+            </tr>
+            <tr>
+              <td>N/A
+</td>
+              <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+            </tr>
+            <tr>
+              <td>DONE-2005-11-24
+</td>
+              <td>Check and make sure that for all items 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>DONE-2005-11-24
+</td>
+              <td>Check and make sure that all items depended upon 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>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </subsection>
+      </subsection>
+      <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+        <ul>
+          <li>Has the receiving PMC voted to accept it? DONE-2005-07-28
+</li>
+        </ul>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/myfaces-tobago.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/ip-clearance/portals-gluecode-jetspeed.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/ip-clearance/portals-gluecode-jetspeed.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/ip-clearance/portals-gluecode-jetspeed.xml (added)
+++ incubator/public/trunk/site/xdocs2/ip-clearance/portals-gluecode-jetspeed.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,134 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>portals-gluecode-jetspeed
+</title>
+  </properties>
+  <body>
+    <section id="XYZ+Codebase+IP+Clearance+Status" name="XYZ Codebase IP Clearance Status"/>
+    <section id="Description" name="Description">
+      <p>The incoming code was contributed by Gluecode Software. It is
+contributing to the Jetspeed codebase as a patch. The patch is
+installed in the jakarta-jetspeed CVS, under the directory 'fusion'.
+Fusion is an optional feature for Jetspeed-1. It provides support for
+'JSR-168' Portlets in Jetspeed-1. This feature allows for portlets to
+be deployed in a standard Portlet Application to Jetspeed-1, and run
+inside a Java Portlet API-compliant portlet container. Fusion
+leverages Jetspeed-2 components and pipelines embedded in the
+Jetspeed-1 server. Fusion was written by a Jetspeed contributor for
+hire, David S Taylor.
+</p>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>Which PMC will be responsible for the code
+</li>
+      </ul>
+      <p>Apache Portals PMC
+</p>
+      <ul>
+        <li>Into which existing project/module
+</li>
+      </ul>
+      <p>Jetspeed (Jetspeed-1)
+</p>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <subsection id="Identify+the+codebase" name="Identify the codebase">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-06-27
+</td>
+            <td>Codebase is a patch to jetspeed CVS.
+</td>
+          </tr>
+        </table>
+      </subsection>
+      <subsection id="Copyright" name="Copyright">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Software Grant form received by Geir Magnusson Jr
+</td>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Files that have been donated have been updated to reflect the new ASF
+copyright.
+</td>
+          </tr>
+        </table>
+      </subsection>
+      <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Check that all active committers have a signed CLA on record
+</td>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Check and make sure that for all items 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>2004-06-25
+</td>
+            <td>Check and make sure that all items depended upon 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>
+        <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+      </subsection>
+    </section>
+    <section id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+      <ul>
+        <li>Has the receiving PMC voted to accept it?
+</li>
+      </ul>
+      <p>No
+</p>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/ip-clearance/portals-gluecode-jetspeed.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/learn/index.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/learn/index.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/learn/index.xml (added)
+++ incubator/public/trunk/site/xdocs2/learn/index.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Apache Incubator Project
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/><!--
+
+    <meta content="The Apache Incubator Project" name="DC.Creator"/>-->
+<!--
+
+    <meta content="Documentation which is under development." name="DC.Description"/>-->
+
+  </properties>
+  <body>
+    <section id="Prototype+Documentation+Under+Development" name="Prototype Documentation Under Development">
+      <p>Since the Incubator project is one of the primary gateways into
+Apache involvement, a lot of the documentation about the structural
+and philosophical details of the Foundation will probably be
+prototyped and developed right here. When they seem to accurately
+reflect reality and cover the information they should, they will be
+moved up to the Foundation's main Web site.
+</p>
+      <p>See the main documentation at
+
+        <a href="http://www.apache.org/dev/">http://www.apache.org/dev/
+</a>which is generally directed at all committers and PMCs, including
+those in Incubation. There is also relevant information at
+
+        <a href="http://www.apache.org/foundation/">http://www.apache.org/foundation/
+</a>especially
+
+        <a href="http://www.apache.org/foundation/how-it-works.html">ASF: How it works
+</a>.
+
+      </p>
+      <p>See
+
+        <a href="../howtoparticipate.html">Updating the Documentation
+</a>for instructions on how to submit modifications to this Incubator
+site.
+
+      </p>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/learn/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/learn/mailing-lists.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/learn/mailing-lists.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/learn/mailing-lists.xml (added)
+++ incubator/public/trunk/site/xdocs2/learn/mailing-lists.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Apache Mailing Lists
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/><!--
+
+    <meta content="The Apache Incubator Project" name="DC.Creator"/>-->
+
+  </properties>
+  <body>
+    <section id="Apache-Wide+Mailing+Lists" name="Apache-Wide Mailing Lists">
+      <p>Everything -- but
+
+        <em>everything
+</em>-- inside the Apache world occurs or is reflected in email. As some
+people say, 'If it isn't in my email, it didn't happen.' In addition
+to the
+
+        <em>per
+</em>-project and special-group mailing lists, there are a few that cross
+all boundaries:
+
+      </p>
+      <ul>
+        <li>
+          <strong>committers
+</strong>: sends important messages to all Apache committers; it's not used
+for discussions
+
+        </li>
+        <li>
+          <strong>community
+</strong>: where all Apache committers can discuss things that are about
+Apache;
+
+        </li>
+        <li>
+          <strong>infrastucture
+</strong>: where the roots and the infrastructure team discuss and work on the
+Apache infrastructure needs;
+
+        </li>
+        <li>
+          <strong>repository
+</strong>: discussions about the Apache artifact repository
+
+        </li>
+        <li>
+          <strong>party
+</strong>: where people plan about how to have fun :-)
+
+        </li>
+      </ul>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/learn/mailing-lists.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/learn/newcommitters.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/learn/newcommitters.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/learn/newcommitters.xml (added)
+++ incubator/public/trunk/site/xdocs2/learn/newcommitters.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Apache Incubator: Voting in a new committer
+</title>
+  </properties>
+  <body>
+    <section id="Voting+in+a+new+committer" name="Voting in a new committer">
+      <p>If a developer has contributed a signicant number of high-quality
+patches, is interested in continuing the contribution, has
+demonstrated the ability to work well with others under the Apache
+guidelines, it may be proposed to grant that developer
+
+        <a href="http://www.apache.org/foundation/glossary.html#CommitAccess">commit access
+</a>. See also the ASF How it Works document which explains
+
+        <a href="http://www.apache.org/foundation/how-it-works.html#roles">meritocracy
+</a>and
+
+        <a href="http://www.apache.org/foundation/how-it-works.html#roles">roles
+</a>.
+
+      </p>
+      <p>Discussion of a potential new committer should take place on the
+project's PPMC list (normally, it would take place on a project's PMC
+list). After vetting the new candidate, the vote can take place
+either on the PPMC list (with notice posted to the Incubator PMC
+list) or on the developer list (with a notice posted to the
+Incubator's general list). The latter practice of a private
+discussion followed by a public, pro-forma, vote is re-emerging as a
+Best Practice for ASF projects.
+</p>
+    </section>
+    <section id="Welcome%21" name="Welcome!">
+      <p>If the vote (only votes cast by PMC/PPMC members are binding) is
+positive, the contributor formally becomes an Apache
+
+        <a href="http://www.apache.org/foundation/glossary.html#Committer">committer
+</a>. A (P)PMC member should then follow the
+
+        <a href="http://www.apache.org/dev/pmc.html">documented procedures**
+</a>to complete the process.
+
+      </p>
+      <p>
+        <em>** Please CC both the Incubator PMC and the PPMC when sending the
+necessary e-mails to root.
+</em>
+      </p>
+      <p>Also, please direct the new committer to the
+
+        <a href="http://www.apache.org/dev/">Apache developer's pages
+</a>and to the
+
+        <a href="http://incubator.apache.org/">Apache Incubator site
+</a>for important additional information.
+
+      </p>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/learn/newcommitters.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/learn/rules-for-revolutionaries.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/learn/rules-for-revolutionaries.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/learn/rules-for-revolutionaries.xml (added)
+++ incubator/public/trunk/site/xdocs2/learn/rules-for-revolutionaries.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,133 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>Apache Archive: Rules for Revolutionaries
+</title>
+    <authors>
+      <person email="duncan@x180.com" name="James Duncan Davidson"/>
+    </authors>
+    <notice>This document is a WIP (Work In Progress).
+</notice>
+    <abstract>Archival copy of Duncan's 'Rules for Revolutionaries.'
+</abstract>
+  </properties>
+  <body>
+    <section id="rules+for+revolutionaries" name="rules for revolutionaries">
+      <note>
+        <strong>As Sent on 13 Jan 2000.
+</strong>© 1995-2002, James Duncan Davidson.
+
+        <br/>
+        <em>Note: This message was written at a specific place and time in
+response to a specific situtation. It does not address several
+important issues like what happens when revolutions do not totally
+succeed. It also doesn't address the issues of responsiblity. The
+Apache Jakarta PMC has responsiblities that aren't detailed here.
+With that said...
+</em>
+      </note>
+      <source xml:space="preserve">
+        <strong>Date:
+</strong>Thu, 13 Jan 2000 15:46:41 -0800
+
+        <strong>Subject:
+</strong>RESET: Proposal for Revolutionaries and Evolutionaries
+
+        <strong>From:
+</strong>James Duncan Davidson &lt;james.davidson@eng.sun.com&gt;
+
+        <strong>To:
+</strong>&lt;general@jakarta.apache.org&gt;
+
+        <strong>CC:
+</strong>&lt;tomcat-dev@jakarta.apache.org&gt; Ok, the logical place for this is
+general@jakarta, but I'm including tomcat-dev@jakarta so that the
+people who are there and not on general can see it. Please do not
+discuss on tomcat-dev, please only discuss on general. In a closed
+source project where you've got a set team, you make decisions about
+where the entire team goes and somebody takes the lead of deciding
+what gets done when. In the discussions about Craig's long term plan,
+this metric was applied by several of us in thoughts about where to
+go next. After pondering this for a while, it's (re)become obvious to
+me that there's no way that anybody can expect an open source
+organization to work the same way that a team in a corporate setting
+can. Ok, so this is pretty freaking obvious, but I've been watching
+people that are not from Sun and who have been doing open source for
+a while talking and proposing things that come from this line of
+thought as well. Its not just people from Sun or people from any
+particular entity. So -- in any software development project there is
+a natural tension between revolution and evolution. In a closed
+source environment, you make the call at any particular time on
+whether you are in revolutionary mode or evolutionary mode. For
+example, JSDK was in evolutionary mode for years. Then in Nov 98, We
+made a decision to go revolutionary. Of course, at the time the
+project team was composed of 1 person -- me, so it was an easy
+decision. After that revolution was over in Jan 99, Tomcat was in
+evolutionary mode getting JSP bolted in and working with J2EE. We
+(Sun folks) could do that because that was what suited the goals best
+at the time. However, Open source is chaotic. With its special magic
+comes a different reality. This is: 1) People work on their own time
+(even people paid by a company can be considered to be working on
+their own time in this situtation as each company is going to have
+different cycles and things they want) 2) People work on what they
+want to. If you are working on your own time, you are going to do
+what you want or you do something else. 3) Some people are
+evolutionaries, other are revolutionaries, and some are both at
+different times. 4) Both approaches are important and need to be
+cultured. 5) You really can't afford to alienate any part of your
+developer community. Innovation can come from anywhere. To allow this
+to happen, to allow revolutionaries to co-exist with evolutionaries,
+I'm proposing the following as official Jakarta policy: 1) Any
+committer has the right to go start a revolution. They can establish
+a branch or seperate whiteboard directory in which to go experiment
+with new code seperate from the main trunk. The only responsibility a
+committer has when they do this is to inform the developer group what
+their intent is, to keep the group updated on their progress, and
+allowing others who want to help out to do so. The committer, and the
+group of people who he/she has a attracted are free to take any
+approaches they want to free of interference. 2) When a revolution is
+ready for prime time, the committer proposes a merge to the -dev
+list. At that time, the overall community evaluates whether or not
+the code is ready to become part of, or to potentially replace the,
+trunk. Suggestions may be made, changes may be required. Once all
+issues have been taken care of and the merge is approved, the new
+code becomes the trunk. 3) A revolution branch is unversioned. It
+doesn't have any official version standing. This allows several
+parallel tracks of development to occur with the final authority of
+what eventually ends up on the trunk laying with the entire community
+of committers. 4) The trunk is the official versioned line of the
+project. All evolutionary minded people are welcome to work on it to
+improve it. Evolutionary work is important and should not stop as it
+is always unclear when any particular revolution will be ready for
+prime time or whether it will be officially accepted. What does this
+mean? In practice, this means that Craig and Hans and anybody else
+that wants to run with that revolution is welcome to do so. The only
+change is that it's not called Tomcat.next -- it's the RED branch or
+GOOGLE branch or whatever they want to call it. Whenever Craig (or
+anybody else working on that codebase) wants to bring stuff into the
+trunk, they propose it here and we evaluate it on it's merits. If
+somebody disagrees with Craig's approach (for the sake of argument
+here), they are free to create a BLUE whiteboard and work out what
+they think is a good solution. At that point, the community will have
+to evaluate both approaches. But since this is a populist society,
+with such a structure it is hoped that it becomes clear which is the
+preferred approach by the community by their participation and
+voting. Or maybe the best solution is something in the middle and the
+two parties work together to merge. Irregardless, the point is to
+allow solutions to happen without being stalled out in the formative
+stages. An important point is that no one revolution is declared to
+be the official .next until it's ready to be accepted for that. There
+is the side effect that we could potentially end up with too many
+revolutions happening, but I'd rather rely upon the natural
+inclination of developers to gravitate towards one solution to
+control this than to try to control it through any policy statement.
+When would this be official? Well, if this is well recieved, we'd
+want to word it up and make it a bylaw (with approval by the PMC --
+this is one of the areas in which the PMC has authority). Hopefully
+soon. Comments? Suggestions? James Davidson duncan@eng.sun.com Java +
+XML / Portable Code + Portable Data !try; do()
+
+      </source>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/learn/rules-for-revolutionaries.xml
------------------------------------------------------------------------------
    svn:eol-style = native



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


Mime
View raw message