incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jerenkra...@apache.org
Subject svn commit: r375081 - in /incubator/public/trunk: site-author/faq.xml site-author/ip-clearance/index.xml site-author/ip-clearance/ip-clearance-template.xml site-publish/faq.html site-publish/ip-clearance/index.html
Date Sun, 05 Feb 2006 19:13:53 GMT
Author: jerenkrantz
Date: Sun Feb  5 11:13:51 2006
New Revision: 375081

URL: http://svn.apache.org/viewcvs?rev=375081&view=rev
Log:
Update FAQ, IP clearance index, and IP clearance template.

Modified:
    incubator/public/trunk/site-author/faq.xml
    incubator/public/trunk/site-author/ip-clearance/index.xml
    incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml
    incubator/public/trunk/site-publish/faq.html
    incubator/public/trunk/site-publish/ip-clearance/index.html

Modified: incubator/public/trunk/site-author/faq.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/faq.xml?rev=375081&r1=375080&r2=375081&view=diff
==============================================================================
--- incubator/public/trunk/site-author/faq.xml (original)
+++ incubator/public/trunk/site-author/faq.xml Sun Feb  5 11:13:51 2006
@@ -1,186 +1,159 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <document>
   <properties>
-    <title>Frequently Asked Questions
-</title>
+    <title>Frequently Asked Questions</title>
   </properties>
   <body>
     <section id="Questions">
-      <title>Questions
-</title>
+      <title>Questions</title>
       <section id="incubator">
-        <title>1. Incubator
-</title>
+        <title>1. Incubator</title>
         <section id="does_project_X_really_need_Incubation">
-          <title>1.1. Does the X Project really have to go in the Incubator to get to
-Apache?
-</title>
-          <p>Yes.
-</p>
-          <p>Code that has existed outside the asf can
-
-            <strong>only
-</strong>enter the ASF through the Incubator. There is no other option.
-
-          </p>
-          <p>The Incubator, among other thingsm is where the due-diligence of
-making sure the licence is correct, the copyright is assigned, and
-all of the initial developers submit their clas.
-</p>
+          <title>1.1. Does the X Project really have to go in the Incubator to
+                 get to Apache?</title>
+          <p>Yes.</p>
+          <p>Code that has existed outside the ASF can <strong>only</strong>
+             enter the ASF through the Incubator. There is no other option.</p>
+          <p>The Incubator, among other things, is where the due-diligence of
+             making sure the licence is correct, the <a
+             href="http://www.apache.org/licenses/#grants">copyright license</a>
+              is received, and all of the initial developers submit their <a
+             href="http://www.apache.org/licenses/#clas">CLAs</a>.</p>
+          <p>The Incubator is also the place where projects can familiarize
+             themselves with how the ASF works under the guidance of Incubator
+             PMC members (<a
+             href="incubation/Roles_and_Responsibilities.html#Mentors"
+             >mentors</a>).</p>
         </section>
         <section id="can_Incubation_be_skipped">
-          <title>1.2. I'm the mentor of this project, and I think that I'm able to do
-it by myself. The Incubator doesn't add anything, can it be skipped?
-</title>
-          <p>No.
-</p>
-          <p>Do it right, do it well, and add something in the process.
-</p>
+          <title>1.2. I'm the mentor of this project, and I think that I'm
+                 able to do it by myself. The Incubator doesn't add anything,
+                 can it be skipped?</title>
+          <p>No.</p>
+          <p>Do it right, do it well, and add something in the process.</p>
           <p>Incubation is not about handing it over to some other group and
-seeing what happens. The Incubator is simply the name of the place
-that governs your actions when you process a new project into Apache.
-It moves at the same rate you do, and achieves whatever you achieve
--- the only difference is that we have a permanent record in
-
-            <strong>one
-</strong>place that we can go back to if there are later IP problems, and
-there is a gate that must be passed through before the project is
-given the right to release software on behalf of the ASF. That gate
-will not be ignored or bypassed just because one group or another
-feels they have earned the right to bypass it; allowing that kind of
-exception destroys the potential to build a tradition of effective
-oversight, which is the reason we created incubator.
-
-          </p>
+             seeing what happens. The Incubator is simply the name of the place
+             that governs your actions when you process a new project into
+             Apache.  It moves at the same rate you do, and achieves whatever
+             you achieve -- the only difference is that we have a permanent
+             record in <strong>one</strong> place that we can go back to if
+             there are later IP problems, and there is a gate that must be
+             passed through before the project is given the right to release
+             software on behalf of the ASF.</p>
+          <p>That gate will not be ignored or bypassed just because one
+             group or another feels they have earned the right to bypass it;
+             allowing that kind of exception destroys the potential to build a
+             tradition of effective oversight, which is the reason we created
+             the incubator.</p>
         </section>
         <section id="project_XXX_makes_no_mention_of_Incubator">
-          <title>1.3. Project XXX makes no mention of the Incubator for accepting new
-projects, but the Incubator site says that all projects entering
-Apache must pass the Incubator. What do we need to do, to move to the
-Apache XXX project?
-</title>
-          <p>The incubation process, WRT responsibilities, is roughly as follows:
-</p>
+          <title>1.3. Project XXX makes no mention of the Incubator for
+                 accepting new projects, but the Incubator site says that all
+                 projects entering Apache must pass the Incubator. What do we
+                 need to do, to move to the Apache XXX project?</title>
+          <p>The incubation process, WRT responsibilities, is roughly as
+             follows:</p>
           <ol>
-            <li>Any Apache PMC (project management commitee) or the Apache board
-approves the entrance of a project at Apache. They are the Sponsor.
-</li>
-            <li>The Incubator is from that moment on responsible for the project,
-which will remain so till the Incubator votes for it to be
-"graduated" to the PMC that asked for it. If the PMC was the
-Incubator itself or the board, the project will have its own PMC.
-</li>
-            <li>Incubation complete.
-</li>
+            <li>Any Apache PMC (project management commitee), including the
+                Incubator PMC itself, will approve the entrance of a project
+                at Apache.  They are the <a
+                href="incubation/Roles_and_Responsibilities.html#Sponsor"
+                >Sponsor</a>.  (In rare cases, the Apache Board of Directors
+                will approve the entrance of a project.)</li>
+            <li>The Incubator PMC is from that moment on responsible for the
+                project.  The assigned <a
+                href="incubation/Roles_and_Responsibilities.html#Mentors"
+                >Mentors</a> (an ASF member who has volunteered to help with
+                the incubation process) will have the primary responsibility
+                for overseeing the progress of the project.  Each quarter, the
+                project will submit an update to the entire Incubator PMC as
+                to the progress in Incubation.</li>
+            <li>This will remain so until the Incubator PMC approves the
+                project to be "graduated".  After graduation, if another
+                PMC sponsored the podling, it will then be transferred to
+                the PMC that asked for incubation.  If the PMC was the
+                Incubator itself or the Board, the project must then also be
+                be approved by the Board to receive its own PMC.</li>
+            <li>At this point, Incubation is complete.</li>
           </ol>
-          <p>So, since you would like to have a place under the XXX Project, ask
-there to vote for acceptance. After that vote, you will automatically
-be under the Incubator, and incubation will take place.
-</p>
+          <p>So, since you would like to have a place under the XXX Project,
+             ask that PMC to sponsor you.  After that vote, you will
+             automatically be under the Incubator, and incubation will
+             start.</p>
         </section>
         <section id="proposed_new_codebase">
-          <title>1.4. Someone has proposed that their code/project be donated to
-project X within the ASF for continued development. What do we need
-to do to accept the code?
-</title>
-          <p>The Incubator will only accept code for incubation if a PMC (project
-management committee) or the Apache board has voted to accept it. So
-when a proposal for the donation of code occurs, the project in
-question should discuss the proposal internally, leading to a
-decision by that project's PMC on whether or not to accept the code
-(and potentially the project surrounding it) into the fold.
-</p>
-          <p>If the PMC agrees, then the incubator can be approached, and the code
-accepted for incubation. The grant needs to be recorded by following
-the procedure outlined at the
-
-            <a href="http://www.apache.org/licenses/">Software Grants
-</a>section of the ASF Licenses page.
-
-          </p>
+          <title>1.4. Someone has proposed that their code/project be donated
+                 to project X within the ASF for continued development. What
+                 do we need to do to accept the code?</title>
+          <p>The Incubator will only accept code for incubation if a PMC
+             has voted to accept it. So when a proposal for the donation of
+             code occurs, the project in question should discuss the proposal
+             (usually on their public mailing lists!), leading to a decision
+             by that project's PMC on whether or not to sponsor the code (and
+             potentially the project surrounding it).</p>
+          <p>If the PMC agrees, then the incubator can be approached, and the
+             code accepted for incubation. The grant needs to be recorded by
+             following the procedure outlined at the <a
+             href="ip-clearance/">IP Clearance forms</a>.</p>
         </section>
         <section id="whose_code">
-          <title>1.5. The code came from outside the ASF, so it's ours to do as we
-like, right?
-</title>
-          <p>Wrong, Here are some generally agreed points that you should take
-into consideration:
-</p>
+          <title>1.5. The code came from outside the ASF, so it's ours to do
+                 as we like, right?</title>
+          <p>Wrong.</p>
+          <p>Here are some generally agreed points that you should take
+             into consideration:</p>
           <ol>
-            <li>No codebase within the ASF is to be considered an exclusive location
-for a general technology within the ASF.
-</li>
-            <li>All initial codebases are just that: initial. Once the code is here,
-if people feel that the code sucks or the architecture sucks, or
-whatever else someone wants to complain about, all parties understood
-that the future direction of the architecture and code is, as is
-everything at the ASF, subject to communal will.
-</li>
-            <li>Other contributors interested in any ASF codebase, with or without
-existing codebases, are free to contribute, or to propose additional
-related projects.
-</li>
+            <li>No codebase within the ASF is to be considered an exclusive
+                location for a general technology within the ASF.</li>
+            <li>All initial codebases are just that: initial. Once the code is
+                here, if people feel that the code sucks or the architecture
+                sucks, or whatever else someone wants to complain about,
+                all parties understand that the future direction of the
+                architecture and code is, as is everything at the ASF,
+                subject to communal will.</li>
+            <li>Other contributors interested in any ASF codebase, with or
+                without existing codebases, are free to contribute, or to
+                propose additional related projects.</li>
           </ol>
         </section>
       </section>
       <section id="how_to_participate">
-        <title>2. How to participate
-</title>
+        <title>2. How to participate</title>
         <section id="site">
-          <title>2.1. How can I update the site?
-</title>
-          <p>Refer to
-
-            <a href="howtoparticipate.html#website">How to Participate
-</a>page. If you are not a committer on the Incubator project, then you
-can still send patches for the source documents.
-
-          </p>
+          <title>2.1. How can I update the site?</title>
+          <p>Refer to <a href="guides/website.html">our updating the website
+             guide</a>.  If you are not a committer on the Incubator project,
+             then you can still send patches for the source documents.</p>
         </section>
         <section id="projectstatus">
-          <title>2.2. How do I update the incubation status of a project?
-</title>
+          <title>2.2. How do I update the incubation status of a
+                 project?</title>
           <p>Look in the incubator SVN module, under
-site-author/projects/projectname.html (Note: Some projects still use
-old *.cwiki as the input format - not recommended.)
-</p>
-          <p>See the
-
-            <a href="guides/website.html">instructions
-</a>for updating the website.
-
-          </p>
+             <code>site-author/projects/projectname.html</code></p>
+          <p>After updating the source, follow the <a
+             href="guides/website.html">instructions for updating the
+             site</a>.</p>
         </section>
         <section id="why_not_issue_tracking_for_incubation_tracking">
-          <title>2.3. Why don't we use an issue tracking system to track incubation
-process?
-</title>
-          <p>AFAIK, issue trackers do not authenticate that the person entering
-the status information has the authority to do so, which is what we
-get with the Subversion source control process.
-</p>
-          <p>Note that how the actual day to day tracking is done is not relevant,
-and any means, even an issue tracker can be used.
-</p>
-          <p>Nevertheless, SVN is our only authorative and formal tracking system
-for incubation status.
-</p>
+          <title>2.3. Why don't we use an issue tracking system to track
+                 incubation process?</title>
+          <p>Issue trackers do not meet the long-term archival and tracking
+             requirements for our legal purposes and they do not authenticate
+             that the person entering the status information has the authority
+             to do so, which is what we get with our version control system.</p>
+          <p>Note that how the actual day to day tracking of the project (i.e.
+             bugs in code) is done is not the same as filing the legal forms -
+             for those issues, our normal issue trackers can be used.</p>
+          <p>Nevertheless, SVN is our only authoritative and formal tracking
+             system for incubation status.</p>
         </section>
         <section id="updating_the_project_website">
-          <title>2.4. How do I update the site of an incubating project?
-</title>
-          <p>First of all, read our
-
-            <a href="incubation/Incubation_Policy.html">Incubation Policy
-</a>.
-
-          </p>
-          <p>Refer to
-
-            <a href="howtoparticipate.html#project-website">How to Participate
-</a>page.
-
-          </p>
+          <title>2.4. How do I update the site of an incubating project?</title>
+          <p>First of all, read our <a
+             href="incubation/Incubation_Policy.html">Incubation Policy</a>.</p>
+          <p>Refer to our <a
+             href="howtoparticipate.html#project-website">How to Participate</a>
+             page.</p>
         </section>
       </section>
     </section>

Modified: incubator/public/trunk/site-author/ip-clearance/index.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/ip-clearance/index.xml?rev=375081&r1=375080&r2=375081&view=diff
==============================================================================
--- incubator/public/trunk/site-author/ip-clearance/index.xml (original)
+++ incubator/public/trunk/site-author/ip-clearance/index.xml Sun Feb  5 11:13:51 2006
@@ -1,211 +1,146 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <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>
+    <title>Intellectual property clearance</title>
   </properties>
   <body>
     <section id="Intellectual+property+clearance">
-      <title>Intellectual property clearance
-</title>
+      <title>Intellectual property clearance</title>
       <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>
+         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 and on our public mailing lists.  This is a
+         short form of the Incubation checklist, designed to allow code to be
+         imported with alacrity while still providing for oversight.</p>
+      <note><strong>This form is not for new projects.</strong>  This is for
+            projects and PMCs that have already been created and are receiving
+            a code donation into an existing codebase.  Any code that was
+            developed outside of the ASF SVN repository and our public mailing
+            lists must be processed like this, even if the external developer
+            is already an ASF committer.</note>
+      <p>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>For new situations, use the
-
-        <a href="http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml">template
-</a>and follow its instructions.
-
-      </p>
+         simply the repository of the needed information. Once a PMC directly
+         checks-in a filled-out short form, everything is done.</p>
+      <p>For new IP clearance forms, start with our XML <a
+         href="http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml">IP clearance 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>
+          <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="harmony-16-contribution-classlib-intel.html">harmony-16-contribution-classlib-intel
-</a>
+            <a href="ip-clearance/harmony-16-contribution-classlib-intel.html">harmony-16-contribution-classlib-intel</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-12-20
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-12-20</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="myfaces-tobago.html">myfaces-tobago
-</a>
+            <a href="ip-clearance/myfaces-tobago.html">myfaces-tobago</a>
           </td>
-          <td colspan="1" rowspan="1">Apache MyFaces
-</td>
-          <td colspan="1" rowspan="1">2005-12-20
-</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="harmony-14-contribution-classlib-ibm.html">harmony-14-contribution-classlib-ibm
-</a>
+            <a href="ip-clearance/harmony-14-contribution-classlib-ibm.html">harmony-14-contribution-classlib-ibm</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-11-24
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-11-24</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="geronimo-1111-trifork-initial.html">geronimo-1111-trifork-initial
+            <a href="ip-clearance/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>
+          <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="harmony-6-contribution-jvm-daniel-lydick.html">harmony-6-contribution-jvm-daniel-lydick
-</a>
+            <a href="ip-clearance/harmony-6-contribution-jvm-daniel-lydick.html">harmony-6-contribution-jvm-daniel-lydick</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-10-08
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-10-08</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="harmony-3-ccontribution-jcvm-archie-cobbs.html">harmony-3-ccontribution-jcvm-archie-cobbs
-</a>
+            <a href="ip-clearance/harmony-3-ccontribution-jcvm-archie-cobbs.html">harmony-3-ccontribution-jcvm-archie-cobbs</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-10-04
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-10-04</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="harmony-5-component-poc-david-tanzer.html">harmony-5-component-poc-david-tanzer
-</a>
+            <a href="ip-clearance/harmony-5-component-poc-david-tanzer.html">harmony-5-component-poc-david-tanzer</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-09-28
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-09-28</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="geronimo-1016-ibm-daytrader.html">geronimo-1016-ibm-daytrader
-</a>
+            <a href="ip-clearance/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>
+          <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>
+            <a href="ip-clearance/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>
+          <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>
+            <a href="ip-clearance/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>
+          <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>
+            <a href="ip-clearance/geronimo-iiop.html">geronimo-iiop</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Geronimo
-</td>
-          <td colspan="1" rowspan="1">2005-01-15
-</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>
+            <a href="ip-clearance/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>
+          <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>
+            <a href="ip-clearance/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>
+          <td colspan="1" rowspan="1">Apache Portals</td>
+          <td colspan="1" rowspan="1">2004-06-27</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="ws-sandesha.html">ws-sandesha
-</a>
+            <a href="ip-clearance/ws-sandesha.html">ws-sandesha</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Web Services
-</td>
-          <td colspan="1" rowspan="1">2004-05-02
-</td>
+          <td colspan="1" rowspan="1">Apache Web Services</td>
+          <td colspan="1" rowspan="1">2004-05-02</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="ws-wss4j.html">ws-wss4j
-</a>
+            <a href="ip-clearance/ws-wss4j.html">ws-wss4j</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Web Services
-</td>
-          <td colspan="1" rowspan="1">2004-02-24
-</td>
+          <td colspan="1" rowspan="1">Apache Web Services</td>
+          <td colspan="1" rowspan="1">2004-02-24</td>
         </tr>
       </table>
     </section>

Modified: incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml?rev=375081&r1=375080&r2=375081&view=diff
==============================================================================
--- incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml (original)
+++ incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml Sun Feb  5 11:13:51 2006
@@ -1,212 +1,155 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <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>
+    <title>XYZ Codebase Intellectual Property (IP) Clearance Status</title>
   </properties>
   <body>
     <section id="Codebase+IP+Clearance+TEMPLATE">
-      <title>Codebase IP Clearance TEMPLATE
-</title>
+      <title>Codebase IP Clearance TEMPLATE</title>
+      <pre>-----8-&lt;---- cut here -------8-&lt;---- cut here -------8-&lt;---- cut here-------8-&lt;----</pre>
       <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>
+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>
+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>
+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>
+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>
+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>
+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>
+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>
+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>
+        <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>
+      <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">
-      <title>XYZ Codebase Intellectual Property (IP) Clearance Status
-</title>
+      <title>XYZ Codebase Intellectual Property (IP) Clearance Status</title>
     </section>
     <section id="Description">
-      <title>Description
-</title>
+      <title>Description</title>
       <p>Describe the incoming codebase, including whether it is a large set
-of patches, new functional modules, etc.
-</p>
+of patches, new functional modules, etc.</p>
     </section>
     <section id="Project+info">
-      <title>Project info
-</title>
+      <title>Project info</title>
       <ul>
-        <li>Which PMC will be responsible for the code
-</li>
+        <li>Which PMC will be responsible for the code</li>
       </ul>
       <ul>
-        <li>Into which existing project/module
-</li>
+        <li>Into which existing project/module</li>
       </ul>
       <p>
-        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
-</em>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).</em>
       </p>
       <section id="Identify+the+codebase">
-        <title>Identify the codebase
-</title>
+        <title>Identify the codebase</title>
         <table>
           <tr>
-            <th>date
-</th>
-            <th>item
-</th>
+            <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>
+            <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>
         <section id="Copyright">
-          <title>Copyright
-</title>
+          <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>
+              <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>
+          <title>Verify distribution rights</title>
           <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>
+              <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
+                  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>
+          <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>
         </section>
       </section>
       <section id="Organizational+acceptance+of+responsibility+for+the+project">
         <title>Organizational acceptance of responsibility for the project
 </title>
         <ul>
-          <li>Has the receiving PMC voted to accept it?
-</li>
+          <li>Has the receiving PMC voted to accept it?</li>
         </ul>
       </section>
     </section>

Modified: incubator/public/trunk/site-publish/faq.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/faq.html?rev=375081&r1=375080&r2=375081&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/faq.html (original)
+++ incubator/public/trunk/site-publish/faq.html Sun Feb  5 11:13:51 2006
@@ -19,8 +19,7 @@
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
   <base href="http://incubator.apache.org/" />
   <link rel="stylesheet" href="/style/style.css" type="text/css" />
-      <title>Frequently Asked Questions
- - Apache Incubator</title>
+      <title>Frequently Asked Questions - Apache Incubator</title>
  </head>
  <body>        
   <table border="0" width="100%" cellspacing="0">
@@ -69,205 +68,167 @@
     <!-- CONTENT -->
     <td align="left" valign="top" class="content">
                 <h2><img src="/images/redarrow.gif" />
-   <a name="Questions">Questions
-</a>
+   <a name="Questions">Questions</a>
 </h2>
 <div class="section-content">
 <h3>
-   <a name="incubator">1. Incubator
-</a>
+   <a name="incubator">1. Incubator</a>
 </h3>
 <div class="section-content">
 <h4> 
-   <a name="does_project_X_really_need_Incubation">1.1. Does the X Project really have to go in the Incubator to get to
-Apache?
-</a> 
-</h4> 
-<div class="section-content">
-<p>Yes.
-</p>
-<p>Code that has existed outside the asf can
-
-            <strong>only
-</strong>enter the ASF through the Incubator. There is no other option.
-
-          </p>
-<p>The Incubator, among other thingsm is where the due-diligence of
-making sure the licence is correct, the copyright is assigned, and
-all of the initial developers submit their clas.
-</p>
-</div>
-<h4> 
-   <a name="can_Incubation_be_skipped">1.2. I'm the mentor of this project, and I think that I'm able to do
-it by myself. The Incubator doesn't add anything, can it be skipped?
-</a> 
-</h4> 
-<div class="section-content">
-<p>No.
-</p>
-<p>Do it right, do it well, and add something in the process.
-</p>
+   <a name="does_project_X_really_need_Incubation">1.1. Does the X Project really have to go in the Incubator to
+                 get to Apache?</a> 
+</h4> 
+<div class="section-content">
+<p>Yes.</p>
+<p>Code that has existed outside the ASF can <strong>only</strong>
+             enter the ASF through the Incubator. There is no other option.</p>
+<p>The Incubator, among other things, is where the due-diligence of
+             making sure the licence is correct, the <a href="http://www.apache.org/licenses/#grants">copyright license</a>
+              is received, and all of the initial developers submit their <a href="http://www.apache.org/licenses/#clas">CLAs</a>.</p>
+<p>The Incubator is also the place where projects can familiarize
+             themselves with how the ASF works under the guidance of Incubator
+             PMC members (<a href="incubation/Roles_and_Responsibilities.html#Mentors">mentors</a>).</p>
+</div>
+<h4> 
+   <a name="can_Incubation_be_skipped">1.2. I'm the mentor of this project, and I think that I'm
+                 able to do it by myself. The Incubator doesn't add anything,
+                 can it be skipped?</a> 
+</h4> 
+<div class="section-content">
+<p>No.</p>
+<p>Do it right, do it well, and add something in the process.</p>
 <p>Incubation is not about handing it over to some other group and
-seeing what happens. The Incubator is simply the name of the place
-that governs your actions when you process a new project into Apache.
-It moves at the same rate you do, and achieves whatever you achieve
--- the only difference is that we have a permanent record in
-
-            <strong>one
-</strong>place that we can go back to if there are later IP problems, and
-there is a gate that must be passed through before the project is
-given the right to release software on behalf of the ASF. That gate
-will not be ignored or bypassed just because one group or another
-feels they have earned the right to bypass it; allowing that kind of
-exception destroys the potential to build a tradition of effective
-oversight, which is the reason we created incubator.
-
-          </p>
-</div>
-<h4> 
-   <a name="project_XXX_makes_no_mention_of_Incubator">1.3. Project XXX makes no mention of the Incubator for accepting new
-projects, but the Incubator site says that all projects entering
-Apache must pass the Incubator. What do we need to do, to move to the
-Apache XXX project?
-</a> 
+             seeing what happens. The Incubator is simply the name of the place
+             that governs your actions when you process a new project into
+             Apache.  It moves at the same rate you do, and achieves whatever
+             you achieve -- the only difference is that we have a permanent
+             record in <strong>one</strong> place that we can go back to if
+             there are later IP problems, and there is a gate that must be
+             passed through before the project is given the right to release
+             software on behalf of the ASF.</p>
+<p>That gate will not be ignored or bypassed just because one
+             group or another feels they have earned the right to bypass it;
+             allowing that kind of exception destroys the potential to build a
+             tradition of effective oversight, which is the reason we created
+             the incubator.</p>
+</div>
+<h4> 
+   <a name="project_XXX_makes_no_mention_of_Incubator">1.3. Project XXX makes no mention of the Incubator for
+                 accepting new projects, but the Incubator site says that all
+                 projects entering Apache must pass the Incubator. What do we
+                 need to do, to move to the Apache XXX project?</a> 
 </h4> 
 <div class="section-content">
-<p>The incubation process, WRT responsibilities, is roughly as follows:
-</p>
+<p>The incubation process, WRT responsibilities, is roughly as
+             follows:</p>
 <ol>
-            <li>Any Apache PMC (project management commitee) or the Apache board
-approves the entrance of a project at Apache. They are the Sponsor.
-</li>
-            <li>The Incubator is from that moment on responsible for the project,
-which will remain so till the Incubator votes for it to be
-"graduated" to the PMC that asked for it. If the PMC was the
-Incubator itself or the board, the project will have its own PMC.
-</li>
-            <li>Incubation complete.
-</li>
+            <li>Any Apache PMC (project management commitee), including the
+                Incubator PMC itself, will approve the entrance of a project
+                at Apache.  They are the <a href="incubation/Roles_and_Responsibilities.html#Sponsor">Sponsor</a>.  (In rare cases, the Apache Board of Directors
+                will approve the entrance of a project.)</li>
+            <li>The Incubator PMC is from that moment on responsible for the
+                project.  The assigned <a href="incubation/Roles_and_Responsibilities.html#Mentors">Mentors</a> (an ASF member who has volunteered to help with
+                the incubation process) will have the primary responsibility
+                for overseeing the progress of the project.  Each quarter, the
+                project will submit an update to the entire Incubator PMC as
+                to the progress in Incubation.</li>
+            <li>This will remain so until the Incubator PMC approves the
+                project to be "graduated".  After graduation, if another
+                PMC sponsored the podling, it will then be transferred to
+                the PMC that asked for incubation.  If the PMC was the
+                Incubator itself or the Board, the project must then also be
+                be approved by the Board to receive its own PMC.</li>
+            <li>At this point, Incubation is complete.</li>
           </ol>
-<p>So, since you would like to have a place under the XXX Project, ask
-there to vote for acceptance. After that vote, you will automatically
-be under the Incubator, and incubation will take place.
-</p>
-</div>
-<h4> 
-   <a name="proposed_new_codebase">1.4. Someone has proposed that their code/project be donated to
-project X within the ASF for continued development. What do we need
-to do to accept the code?
-</a> 
-</h4> 
-<div class="section-content">
-<p>The Incubator will only accept code for incubation if a PMC (project
-management committee) or the Apache board has voted to accept it. So
-when a proposal for the donation of code occurs, the project in
-question should discuss the proposal internally, leading to a
-decision by that project's PMC on whether or not to accept the code
-(and potentially the project surrounding it) into the fold.
-</p>
-<p>If the PMC agrees, then the incubator can be approached, and the code
-accepted for incubation. The grant needs to be recorded by following
-the procedure outlined at the
-
-            <a href="http://www.apache.org/licenses/">Software Grants
-</a>section of the ASF Licenses page.
-
-          </p>
-</div>
-<h4> 
-   <a name="whose_code">1.5. The code came from outside the ASF, so it's ours to do as we
-like, right?
-</a> 
-</h4> 
-<div class="section-content">
-<p>Wrong, Here are some generally agreed points that you should take
-into consideration:
-</p>
+<p>So, since you would like to have a place under the XXX Project,
+             ask that PMC to sponsor you.  After that vote, you will
+             automatically be under the Incubator, and incubation will
+             start.</p>
+</div>
+<h4> 
+   <a name="proposed_new_codebase">1.4. Someone has proposed that their code/project be donated
+                 to project X within the ASF for continued development. What
+                 do we need to do to accept the code?</a> 
+</h4> 
+<div class="section-content">
+<p>The Incubator will only accept code for incubation if a PMC
+             has voted to accept it. So when a proposal for the donation of
+             code occurs, the project in question should discuss the proposal
+             (usually on their public mailing lists!), leading to a decision
+             by that project's PMC on whether or not to sponsor the code (and
+             potentially the project surrounding it).</p>
+<p>If the PMC agrees, then the incubator can be approached, and the
+             code accepted for incubation. The grant needs to be recorded by
+             following the procedure outlined at the <a href="ip-clearance/">IP Clearance forms</a>.</p>
+</div>
+<h4> 
+   <a name="whose_code">1.5. The code came from outside the ASF, so it's ours to do
+                 as we like, right?</a> 
+</h4> 
+<div class="section-content">
+<p>Wrong.</p>
+<p>Here are some generally agreed points that you should take
+             into consideration:</p>
 <ol>
-            <li>No codebase within the ASF is to be considered an exclusive location
-for a general technology within the ASF.
-</li>
-            <li>All initial codebases are just that: initial. Once the code is here,
-if people feel that the code sucks or the architecture sucks, or
-whatever else someone wants to complain about, all parties understood
-that the future direction of the architecture and code is, as is
-everything at the ASF, subject to communal will.
-</li>
-            <li>Other contributors interested in any ASF codebase, with or without
-existing codebases, are free to contribute, or to propose additional
-related projects.
-</li>
+            <li>No codebase within the ASF is to be considered an exclusive
+                location for a general technology within the ASF.</li>
+            <li>All initial codebases are just that: initial. Once the code is
+                here, if people feel that the code sucks or the architecture
+                sucks, or whatever else someone wants to complain about,
+                all parties understand that the future direction of the
+                architecture and code is, as is everything at the ASF,
+                subject to communal will.</li>
+            <li>Other contributors interested in any ASF codebase, with or
+                without existing codebases, are free to contribute, or to
+                propose additional related projects.</li>
           </ol>
 </div>
 </div>
 <h3>
-   <a name="how_to_participate">2. How to participate
-</a>
+   <a name="how_to_participate">2. How to participate</a>
 </h3>
 <div class="section-content">
 <h4> 
-   <a name="site">2.1. How can I update the site?
-</a> 
+   <a name="site">2.1. How can I update the site?</a> 
 </h4> 
 <div class="section-content">
-<p>Refer to
-
-            <a href="howtoparticipate.html#website">How to Participate
-</a>page. If you are not a committer on the Incubator project, then you
-can still send patches for the source documents.
-
-          </p>
+<p>Refer to <a href="guides/website.html">our updating the website
+             guide</a>.  If you are not a committer on the Incubator project,
+             then you can still send patches for the source documents.</p>
 </div>
 <h4> 
-   <a name="projectstatus">2.2. How do I update the incubation status of a project?
-</a> 
+   <a name="projectstatus">2.2. How do I update the incubation status of a
+                 project?</a> 
 </h4> 
 <div class="section-content">
 <p>Look in the incubator SVN module, under
-site-author/projects/projectname.html (Note: Some projects still use
-old *.cwiki as the input format - not recommended.)
-</p>
-<p>See the
-
-            <a href="guides/website.html">instructions
-</a>for updating the website.
-
-          </p>
-</div>
-<h4> 
-   <a name="why_not_issue_tracking_for_incubation_tracking">2.3. Why don't we use an issue tracking system to track incubation
-process?
-</a> 
-</h4> 
-<div class="section-content">
-<p>AFAIK, issue trackers do not authenticate that the person entering
-the status information has the authority to do so, which is what we
-get with the Subversion source control process.
-</p>
-<p>Note that how the actual day to day tracking is done is not relevant,
-and any means, even an issue tracker can be used.
-</p>
-<p>Nevertheless, SVN is our only authorative and formal tracking system
-for incubation status.
-</p>
-</div>
-<h4> 
-   <a name="updating_the_project_website">2.4. How do I update the site of an incubating project?
-</a> 
-</h4> 
-<div class="section-content">
-<p>First of all, read our
-
-            <a href="incubation/Incubation_Policy.html">Incubation Policy
-</a>.
-
-          </p>
-<p>Refer to
-
-            <a href="howtoparticipate.html#project-website">How to Participate
-</a>page.
-
-          </p>
+             <code>site-author/projects/projectname.html</code></p>
+<p>After updating the source, follow the <a href="guides/website.html">instructions for updating the
+             site</a>.</p>
+</div>
+<h4> 
+   <a name="why_not_issue_tracking_for_incubation_tracking">2.3. Why don't we use an issue tracking system to track
+                 incubation process?</a> 
+</h4> 
+<div class="section-content">
+<p>Issue trackers do not meet the long-term archival and tracking
+             requirements for our legal purposes and they do not authenticate
+             that the person entering the status information has the authority
+             to do so, which is what we get with our version control system.</p>
+<p>Note that how the actual day to day tracking of the project (i.e.
+             bugs in code) is done is not the same as filing the legal forms -
+             for those issues, our normal issue trackers can be used.</p>
+<p>Nevertheless, SVN is our only authoritative and formal tracking
+             system for incubation status.</p>
+</div>
+<h4> 
+   <a name="updating_the_project_website">2.4. How do I update the site of an incubating project?</a> 
+</h4> 
+<div class="section-content">
+<p>First of all, read our <a href="incubation/Incubation_Policy.html">Incubation Policy</a>.</p>
+<p>Refer to our <a href="howtoparticipate.html#project-website">How to Participate</a>
+             page.</p>
 </div>
 </div>
 </div>

Modified: incubator/public/trunk/site-publish/ip-clearance/index.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/ip-clearance/index.html?rev=375081&r1=375080&r2=375081&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/ip-clearance/index.html (original)
+++ incubator/public/trunk/site-publish/ip-clearance/index.html Sun Feb  5 11:13:51 2006
@@ -19,8 +19,7 @@
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
   <base href="http://incubator.apache.org/" />
   <link rel="stylesheet" href="/style/style.css" type="text/css" />
-      <title>Intellectual property clearance
- - Apache Incubator</title>
+      <title>Intellectual property clearance - Apache Incubator</title>
  </head>
  <body>        
   <table border="0" width="100%" cellspacing="0">
@@ -69,198 +68,144 @@
     <!-- CONTENT -->
     <td align="left" valign="top" class="content">
                 <h2><img src="/images/redarrow.gif" />
-   <a name="Intellectual+property+clearance">Intellectual property clearance
-</a>
+   <a name="Intellectual+property+clearance">Intellectual property clearance</a>
 </h2>
 <div class="section-content">
 <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>
+         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 and on our public mailing lists.  This is a
+         short form of the Incubation checklist, designed to allow code to be
+         imported with alacrity while still providing for oversight.</p>
+<div class="note">
+<note><strong>This form is not for new projects.</strong>  This is for
+            projects and PMCs that have already been created and are receiving
+            a code donation into an existing codebase.  Any code that was
+            developed outside of the ASF SVN repository and our public mailing
+            lists must be processed like this, even if the external developer
+            is already an ASF committer.</note>
+</div>
+<p>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>For new situations, use the
-
-        <a href="http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml">template
-</a>and follow its instructions.
-
-      </p>
+         simply the repository of the needed information. Once a PMC directly
+         checks-in a filled-out short form, everything is done.</p>
+<p>For new IP clearance forms, start with our XML <a href="http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml">IP clearance template</a> and
+         follow its instructions.</p>
 <table class="colortable" width="100%">
         <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>
+          <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="harmony-16-contribution-classlib-intel.html">harmony-16-contribution-classlib-intel
-</a>
+            <a href="ip-clearance/harmony-16-contribution-classlib-intel.html">harmony-16-contribution-classlib-intel</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-12-20
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-12-20</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="myfaces-tobago.html">myfaces-tobago
-</a>
+            <a href="ip-clearance/myfaces-tobago.html">myfaces-tobago</a>
           </td>
-          <td colspan="1" rowspan="1">Apache MyFaces
-</td>
-          <td colspan="1" rowspan="1">2005-12-20
-</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="harmony-14-contribution-classlib-ibm.html">harmony-14-contribution-classlib-ibm
-</a>
+            <a href="ip-clearance/harmony-14-contribution-classlib-ibm.html">harmony-14-contribution-classlib-ibm</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-11-24
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-11-24</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="geronimo-1111-trifork-initial.html">geronimo-1111-trifork-initial
+            <a href="ip-clearance/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>
+          <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="harmony-6-contribution-jvm-daniel-lydick.html">harmony-6-contribution-jvm-daniel-lydick
-</a>
+            <a href="ip-clearance/harmony-6-contribution-jvm-daniel-lydick.html">harmony-6-contribution-jvm-daniel-lydick</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-10-08
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-10-08</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="harmony-3-ccontribution-jcvm-archie-cobbs.html">harmony-3-ccontribution-jcvm-archie-cobbs
-</a>
+            <a href="ip-clearance/harmony-3-ccontribution-jcvm-archie-cobbs.html">harmony-3-ccontribution-jcvm-archie-cobbs</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-10-04
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-10-04</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="harmony-5-component-poc-david-tanzer.html">harmony-5-component-poc-david-tanzer
-</a>
+            <a href="ip-clearance/harmony-5-component-poc-david-tanzer.html">harmony-5-component-poc-david-tanzer</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Harmony / Incubator
-</td>
-          <td colspan="1" rowspan="1">2005-09-28
-</td>
+          <td colspan="1" rowspan="1">Apache Harmony / Incubator</td>
+          <td colspan="1" rowspan="1">2005-09-28</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="geronimo-1016-ibm-daytrader.html">geronimo-1016-ibm-daytrader
-</a>
+            <a href="ip-clearance/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>
+          <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>
+            <a href="ip-clearance/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>
+          <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>
+            <a href="ip-clearance/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>
+          <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>
+            <a href="ip-clearance/geronimo-iiop.html">geronimo-iiop</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Geronimo
-</td>
-          <td colspan="1" rowspan="1">2005-01-15
-</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>
+            <a href="ip-clearance/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>
+          <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>
+            <a href="ip-clearance/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>
+          <td colspan="1" rowspan="1">Apache Portals</td>
+          <td colspan="1" rowspan="1">2004-06-27</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="ws-sandesha.html">ws-sandesha
-</a>
+            <a href="ip-clearance/ws-sandesha.html">ws-sandesha</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Web Services
-</td>
-          <td colspan="1" rowspan="1">2004-05-02
-</td>
+          <td colspan="1" rowspan="1">Apache Web Services</td>
+          <td colspan="1" rowspan="1">2004-05-02</td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
-            <a href="ws-wss4j.html">ws-wss4j
-</a>
+            <a href="ip-clearance/ws-wss4j.html">ws-wss4j</a>
           </td>
-          <td colspan="1" rowspan="1">Apache Web Services
-</td>
-          <td colspan="1" rowspan="1">2004-02-24
-</td>
+          <td colspan="1" rowspan="1">Apache Web Services</td>
+          <td colspan="1" rowspan="1">2004-02-24</td>
         </tr>
       </table>
 </div>



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


Mime
View raw message