incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nic...@apache.org
Subject svn commit: r662332 - in /incubator/public/trunk: site-author/ip-clearance/index.xml site-publish/ip-clearance/index.html
Date Mon, 02 Jun 2008 05:56:03 GMT
Author: niclas
Date: Sun Jun  1 22:56:03 2008
New Revision: 662332

URL: http://svn.apache.org/viewvc?rev=662332&view=rev
Log:
Update of the main IP Clearance page.

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

Modified: incubator/public/trunk/site-author/ip-clearance/index.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/index.xml?rev=662332&r1=662331&r2=662332&view=diff
==============================================================================
--- incubator/public/trunk/site-author/ip-clearance/index.xml (original)
+++ incubator/public/trunk/site-author/ip-clearance/index.xml Sun Jun  1 22:56:03 2008
@@ -27,13 +27,13 @@
       <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. These legal documents are available on the 
+         existing project/module. These legal documents are available on the
          <a href="http://www.apache.org/licenses/">ASF Licenses</a> page. </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, the Incubator PMC will need to 
+         checks-in a filled-out short form, the Incubator PMC will need to
          approve the paper work after which point the receiving PMC is free to
-         import the code. <strong>Note</strong> that only lazy concensus is 
+         import the code. <strong>Note</strong> that only lazy concensus is
          required. The <a href='ip-clearance-template.html'>IP clearance template</a>
          contains more details of this process.</p>
       <p>For new IP clearance forms, start with our XML <a
@@ -47,6 +47,13 @@
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
+            <a href="felix-pax-logging.html">Pax Logging</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Felix</td>
+          <td colspan="1" rowspan="1">2008-06-02</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
             <a href="felix-osgi-console.html">OSGi Console</a>
           </td>
           <td colspan="1" rowspan="1">Apache Felix</td>
@@ -455,7 +462,7 @@
       <section id="notes">
         <title>Additional notes</title>
         <p>
-          The software grant requires that "Licensor owns or has sufficient 
+          The software grant requires that "Licensor owns or has sufficient
           rights to contribute the software source code...". In the case where
           there are multiple entities involved that only together have sufficient
           rights (for example in the case of an existing external project with
@@ -463,14 +470,14 @@
         </p>
         <ol>
           <li>
-            All entities sign the same software grant together and submit one software 
+            All entities sign the same software grant together and submit one software
             grant form. This is preferred but obviously can complicate the process
             considerably.
           </li>
           <li>
-            The alternative is that each party sign its own software grant while 
+            The alternative is that each party sign its own software grant while
             everyone references the same contribution (designated by a URL and an MD5
-            hash over the ZIP file representing the contribution). It is recommended 
+            hash over the ZIP file representing the contribution). It is recommended
             that the software grant form is modified in order to have a line for each
             party so the completeness of the paperwork can be verified upon receipt.
           </li>

Modified: incubator/public/trunk/site-publish/ip-clearance/index.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/ip-clearance/index.html?rev=662332&r1=662331&r2=662332&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/ip-clearance/index.html (original)
+++ incubator/public/trunk/site-publish/ip-clearance/index.html Sun Jun  1 22:56:03 2008
@@ -125,13 +125,13 @@
 <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. These legal documents are available on the 
+         existing project/module. These legal documents are available on the
          <a href="http://www.apache.org/licenses/">ASF Licenses</a> page. </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, the Incubator PMC will need to 
+         checks-in a filled-out short form, the Incubator PMC will need to
          approve the paper work after which point the receiving PMC is free to
-         import the code. <strong>Note</strong> that only lazy concensus is 
+         import the code. <strong>Note</strong> that only lazy concensus is
          required. The <a href="ip-clearance-template.html">IP clearance template</a>
          contains more details of this process.</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
@@ -144,6 +144,13 @@
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
+            <a href="felix-pax-logging.html">Pax Logging</a>
+          </td>
+          <td colspan="1" rowspan="1">Apache Felix</td>
+          <td colspan="1" rowspan="1">2008-06-02</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">
             <a href="felix-osgi-console.html">OSGi Console</a>
           </td>
           <td colspan="1" rowspan="1">Apache Felix</td>
@@ -554,7 +561,7 @@
 </h3>
 <div class="section-content">
 <p>
-          The software grant requires that "Licensor owns or has sufficient 
+          The software grant requires that "Licensor owns or has sufficient
           rights to contribute the software source code...". In the case where
           there are multiple entities involved that only together have sufficient
           rights (for example in the case of an existing external project with
@@ -562,14 +569,14 @@
         </p>
 <ol>
           <li>
-            All entities sign the same software grant together and submit one software 
+            All entities sign the same software grant together and submit one software
             grant form. This is preferred but obviously can complicate the process
             considerably.
           </li>
           <li>
-            The alternative is that each party sign its own software grant while 
+            The alternative is that each party sign its own software grant while
             everyone references the same contribution (designated by a URL and an MD5
-            hash over the ZIP file representing the contribution). It is recommended 
+            hash over the ZIP file representing the contribution). It is recommended
             that the software grant form is modified in order to have a line for each
             party so the completeness of the paperwork can be verified upon receipt.
           </li>



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


Mime
View raw message