incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pnol...@apache.org
Subject svn commit: r1780537 - /incubator/public/trunk/content/ip-clearance/celix-publish-subscribe.xml
Date Fri, 27 Jan 2017 10:52:51 GMT
Author: pnoltes
Date: Fri Jan 27 10:52:51 2017
New Revision: 1780537

URL: http://svn.apache.org/viewvc?rev=1780537&view=rev
Log:
Adds initial ip clearence form for celix publish subscribe donation

Added:
    incubator/public/trunk/content/ip-clearance/celix-publish-subscribe.xml

Added: incubator/public/trunk/content/ip-clearance/celix-publish-subscribe.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/celix-publish-subscribe.xml?rev=1780537&view=auto
==============================================================================
--- incubator/public/trunk/content/ip-clearance/celix-publish-subscribe.xml (added)
+++ incubator/public/trunk/content/ip-clearance/celix-publish-subscribe.xml [utf-8] Fri Jan
27 10:52:51 2017
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+  <properties>
+    <title>Celix Publish Subscribe Codebase Intellectual Property (IP) Clearance Status</title>
+  </properties>
+  <body>
+    <section id="Celix+Publish+Subscribe+Codebase+Intellectual+Property+%28IP%29+Clearance+Status">
+      <title>Celix Publish Subscribe Codebase Intellectual Property (IP) Clearance
Status</title>
+    </section>
+    <section id="Description">
+      <title>Description</title>
+      <p>A distributed service oriented implementation of the publish subscribe pattern.
The design depends on 3 modules. A module for discovery, another module for serialization
and transport
+and lastly a topology manager module which control the other modules. Multiple implementation
can of the modules can be used to offer different technologies (e.g discovery using etcd or
mdns).
+     
+This donation contains: A PubSub Topology Manager implementation, A PubSub discovery implementation
using etcd, A PubSub transport/serialization implementation using UDP multicast / JSON and
an alternative PubSub transport/serialization implementation using ZeroMq / JSON.   
+     </p>
+    </section>
+    <section id="Project+info">
+      <title>Project info</title>
+      <ul>
+        <li>Which PMC will be responsible for the code</li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module</li>
+      </ul>
+      <ul>
+        <li>Officer or member managing donation:</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>2017-01-27</td>
+            <td>If applicable, make sure that any associated name does not
+                already exist and is not already trademarked for an existing software
+                product.</td>
+          </tr>
+        </table>
+        <p>
+MD5 or SHA1 sum for donated software: SHA1 sum 7a28119a6805cd82289eb41674628ea502fdccac (tarball
can be found at issue https://issues.apache.org/jira/browse/CELIX-389)
+        </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>....-..-..</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>For individuals, use the name as recorded on the committers page</em>
+</li>
+            </ul>
+          <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
+                  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>
+        </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><em>The VOTE thread accepting the donation may happen either
+before or after IP clearance. Adoption by lazy concensus is acceptable but
+not recommended.</em></li>
+        </ul>
+      </section>
+    </section>
+  </body>
+</document>



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


Mime
View raw message