Hi all, Spark Connect Gateway is preparing its first release (0.1.0), which will include a source release and a container image. Before the release vote, I'd like to check whether it needs to go through the ASF export process for cryptographic software (https://infra.apache.org/crypto.html).
The gateway contains cryptography. Its container image ships a statically linked binary that includes rustls and ring for TLS (ring includes code derived from BoringSSL), and RustCrypto crates (rsa, p256, p384, ed25519-dalek) for JWT verification. The gateway is not listed on https://www.apache.org/licenses/exports/, and its NOTICE has no Export Control Notice. For comparison, spark-kubernetes-operator's container image also bundles cryptographic code (Tink, nimbus-jose-jwt, commons-crypto, and a JRE with the JDK's crypto providers). Its NOTICE has no Export Control Notice either. spark-connect-go and spark-connect-swift don't have one, but they only publish source releases. Questions: 1. Does the gateway need to go through the export process (an entry on the exports page, a BIS notification, and an Export Control Notice in NOTICE) before 0.1.0? Or does the PMC consider it covered by the existing Apache Spark entry? 2. If it does, who on the PMC would do it? Updating the exports page needs site-dev karma. Thanks, Liang-Chi
