incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rlenfer...@apache.org
Subject svn commit: r1862890 - in /incubator/public/trunk/content/ip-clearance: celix-http-admin.xml index.xml
Date Wed, 10 Jul 2019 18:13:56 GMT
Author: rlenferink
Date: Wed Jul 10 18:13:56 2019
New Revision: 1862890

URL: http://svn.apache.org/viewvc?rev=1862890&view=rev
Log:
Started with IP clearance for Apache Celix HTTP admin

Added:
    incubator/public/trunk/content/ip-clearance/celix-http-admin.xml
Modified:
    incubator/public/trunk/content/ip-clearance/index.xml

Added: incubator/public/trunk/content/ip-clearance/celix-http-admin.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/celix-http-admin.xml?rev=1862890&view=auto
==============================================================================
--- incubator/public/trunk/content/ip-clearance/celix-http-admin.xml (added)
+++ incubator/public/trunk/content/ip-clearance/celix-http-admin.xml [utf-8] Wed Jul 10 18:13:56
2019
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+  <properties>
+    <title>Celix HTTP admin Intellectual Property (IP) Clearance Status</title>
+  </properties>
+  <body>
+    <section id="Celix+HTTP+admin+Intellectual+Property+%28IP%29+Clearance+Status">
+      <title>Celix HTTP admin Intellectual Property (IP) Clearance Status</title>
+    </section>
+    <section id="Description">
+      <title>Description</title>
+      <p>
+        The incoming codebase contains an HTTP admin implementation for Celix. This HTTP
admin follows the OSGi spec
+        and can be used to publish resources on a specified HTTP endpoint. The HTTP admin
supports the use of
+        websockets as well.
+      </p>
+    </section>
+    <section id="Project+info">
+      <title>Project info</title>
+      <ul>
+        <li>Which PMC will be responsible for the code: The Celix PMC</li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module: Apache Celix</li>
+      </ul>
+      <ul>
+        <li>Officer or member managing donation: Roy Lenferink</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).</em>
+      </p>
+      <section id="Identify+the+codebase">
+        <title>Identify the codebase</title>
+        <table>
+          <tr>
+            <th>date</th>
+            <th>item</th>
+          </tr>
+          <tr>
+            <td>2019-07-10</td>
+            <td>Source codebase is from <a href="https://github.com/apache/celix/pull/33/commits/1c8de37d583b250a31f8cb636641fd963361fe7e">GitHub
commit</a></td>
+          </tr>
+        </table>
+        <p>
+          Git commit SHA for donated software: 1c8de37d583b250a31f8cb636641fd963361fe7e
+        </p>
+        <section id="Copyright">
+          <title>Copyright</title>
+          <table>
+            <tr>
+              <th>date</th>
+              <th>item</th>
+            </tr>
+            <tr>
+              <td>....-..-..</td>
+              <td>Check and make sure that the papers that transfer rights to
+                  the ASF been received. It is only necessary to transfer
+                  rights for the package, the core code, and any new code
+                  produced by the project.</td>
+            </tr>
+            <tr>
+              <td>2019-07-10</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>
+            Identify name recorded for software grant: <em>the name of the grant as
recorded
+            in the foundation/officers area, in either grants.txt or cclas.txt, so that the
+            grant can be easily identified. If recorded in the grants.txt document, use the
+            "for" or title. If recorded in the cclas.txt document, use the company name
+            (field 2 without submitter name) and the "form on file" name (field 4, without
+            any people's names).</em>
+          </p>
+        </section>
+        <section id="Verify+distribution+rights">
+          <title>Verify distribution rights</title>
+            <p>
+              Corporations and individuals holding existing distribution rights:
+            </p>
+            <ul>
+            <li>
+                <em>Thales Netherlands B.V. (SGA to be submitted)</em>
+                <em>Daan Fisher (ICLA on file)</em>
+            </li>
+            </ul>
+          <table>
+            <tr>
+              <th>date</th>
+              <th>item</th>
+            </tr>
+            <tr>
+              <td>2019-07-10</td>
+              <td>Check that all active committers have a signed CLA on
+                  record.</td>
+            </tr>
+            <tr>
+              <td>2019-07-10</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>2019-07-10</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>2019-07-10</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>
+        </section>
+      </section>
+      <section id="Organizational+acceptance+of+responsibility+for+the+project">
+        <title>Organizational acceptance of responsibility for the project</title>
+        <p>
+          Related VOTEs:
+        </p>
+        <ul>
+          <li><a href="https://lists.apache.org/thread.html/8370f83e9eb8799daaef7f95402f83b2e8e7d8c25ddb1c2ad72c9865@%3Cdev.celix.apache.org%3E">dev@celix
VOTE thread</a></li>
+          <li><a href="https://lists.apache.org/thread.html/b14b2c4221d40d0b610de738f6682b24de0e3d179ac13ad0f1b5df71@%3Cdev.celix.apache.org%3E">dev@celix
RESULT thread</a></li>
+        </ul>
+      </section>
+    </section>
+  </body>
+</document>

Modified: incubator/public/trunk/content/ip-clearance/index.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/index.xml?rev=1862890&r1=1862889&r2=1862890&view=diff
==============================================================================
--- incubator/public/trunk/content/ip-clearance/index.xml [utf-8] (original)
+++ incubator/public/trunk/content/ip-clearance/index.xml [utf-8] Wed Jul 10 18:13:56 2019
@@ -48,6 +48,13 @@
         </tr>
         <tr>
           <td>
+            <a href="celix-http-admin.html">Celix HTTP admin</a>
+          </td>
+          <td>Apache Celix</td>
+          <td>2019-07-10</td>
+        </tr>
+        <tr>
+          <td>
             <a href="servicecomb-mesher.html">Apache ServiceComb Mesher</a>
           </td>
           <td>Apache ServiceComb</td>



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


Mime
View raw message