You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by ni...@apache.org on 2023/10/17 08:07:12 UTC
svn commit: r1913042 - /incubator/public/trunk/content/ip-clearance/kyuubi-pyhive.xml
Author: ningjiang
Date: Tue Oct 17 08:07:12 2023
New Revision: 1913042
URL: http://svn.apache.org/viewvc?rev=1913042&view=rev
Log:
Added the file of kyuubi-pyhive.xml
Added:
incubator/public/trunk/content/ip-clearance/kyuubi-pyhive.xml
Added: incubator/public/trunk/content/ip-clearance/kyuubi-pyhive.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/kyuubi-pyhive.xml?rev=1913042&view=auto
==============================================================================
--- incubator/public/trunk/content/ip-clearance/kyuubi-pyhive.xml (added)
+++ incubator/public/trunk/content/ip-clearance/kyuubi-pyhive.xml [utf-8] Tue Oct 17 08:07:12 2023
@@ -0,0 +1,136 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <title>Kyuubi PyHive Codebase Intellectual Property (IP) Clearance Status</title>
+ </properties>
+ <body>
+ <section id="Kyuubi+PyHive+Codebase+IP+Clearance">
+ <title>Kyuubi PyHive Codebase IP Clearance</title>
+ </section>
+ <section id="Description">
+ <title>Description</title>
+ <p>PyHive is a popular Python library that allows users to use DB-API and SQLAlchemy interfaces to access Presto, Hive, and Trino.</p>
+ </section>
+ <section id="Project+info">
+ <title>Project info</title>
+ <ul>
+ <li>The Apache Kyuubi PMC will be responsible for the code.</li>
+ </ul>
+ <ul>
+ <li>The code will be imported into the existing Apache Kyuubi project main repo, https://github.com/apache/kyuubi</li>
+ </ul>
+ <ul>
+ <li>Officer or member managing donation: Willem Jiang (Apache Kyuubi PMC member)</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>
+ <tr>
+ <td>2023-10-17</td>
+ <td>Trademark and Google Search found no use of name as software product.</td>
+ </tr>
+ </table>
+ <p>
+ Origin:
+ <a href="https://github.com/dropbox/PyHive">https://github.com/dropbox/PyHive</a>
+ as at commit ID d4ae481675ac5588ba9101596fa26f22ef0e77c4.
+ </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>2023-10-17</td>
+ <td>Check that all active committers have a signed CLA on record.</td>
+ </tr>
+ <tr>
+ <td>2023-10-17</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>2023-10-17</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>2023-10-17</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