[ 
https://issues.apache.org/jira/browse/SPARK-61599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

L. C. Hsieh resolved SPARK-61599.
---------------------------------
    Fix Version/s: connect-gateway-0.1.0
       Resolution: Fixed

Issue resolved by pull request 64
[https://github.com/apache/spark-connect-gateway/pull/64]

> Remove the Export Control Notice copied from Apache Spark from NOTICE and 
> NOTICE-binary
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-61599
>                 URL: https://issues.apache.org/jira/browse/SPARK-61599
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Connect
>    Affects Versions: connect-gateway-0.1.0
>            Reporter: L. C. Hsieh
>            Assignee: L. C. Hsieh
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: connect-gateway-0.1.0
>
>
> NOTICE was copied from apache/spark when the code was imported. It brought
> along Spark's Export Control Notice, which says that BIS has classified the
> software as ECCN 5D002.C.1 and that it is eligible for License Exception TSU.
> That statement has not been made true for the gateway. The gateway has not
> gone through the ASF export process (https://infra.apache.org/crypto.html):
> it is not listed on https://www.apache.org/licenses/exports/, and BIS has not
> been notified for it.
> This removes the notice from NOTICE and NOTICE-binary, which matches
> spark-kubernetes-operator: its container image also bundles cryptographic
> code, and its NOTICE carries no Export Control Notice of its own.
> Whether the gateway needs to go through the export process is a separate
> question for the PMC, discussed on dev@. If the answer is yes, the notice
> comes back once that process is done.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to