From dev-return-23770-archive-asf-public=cust-asf.ponee.io@spark.apache.org Thu Jan 11 20:40:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id C288D180656 for ; Thu, 11 Jan 2018 20:40:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B21D9160C23; Thu, 11 Jan 2018 19:40:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D1115160C13 for ; Thu, 11 Jan 2018 20:40:04 +0100 (CET) Received: (qmail 87431 invoked by uid 500); 11 Jan 2018 19:40:03 -0000 Mailing-List: contact dev-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@spark.apache.org Received: (qmail 87419 invoked by uid 99); 11 Jan 2018 19:40:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jan 2018 19:40:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 5ECF6C4531 for ; Thu, 11 Jan 2018 19:40:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.211 X-Spam-Level: *** X-Spam-Status: No, score=3.211 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id R7ScIy1rh29W for ; Thu, 11 Jan 2018 19:40:01 +0000 (UTC) Received: from mail-pg0-f43.google.com (mail-pg0-f43.google.com [74.125.83.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 101835F3CC for ; Thu, 11 Jan 2018 19:40:01 +0000 (UTC) Received: by mail-pg0-f43.google.com with SMTP id z20so2858242pgv.6 for ; Thu, 11 Jan 2018 11:40:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=FpSn+5xavpYDKqHWQ7KBxWy/Cugpi9bykXKPflUY7zU=; b=mJ62e9WOfYzjpgKympRmY4wEpz99Fqwz2hp1OP9A/MD6iHUuYiofXpKwrTCeNvWOJy IpspIgQI9jF5YGJ6T7TPh5XpTwdQ5+NNWu+Zy960Mnvko/9+ozReU1E+J4/vE+H4yXAh +Uir2SooQMCTglTAzxm5I3XLvLrcFUphyC0kks3wS4JN9wPyU3XiadCUi62sOHUlcFwc 813Ie9Gn43a0Mo1gRFKoUqjN1Bbiv1RYJ9Kl3pn5eTUXJBxae2J9jH2KXjSz3wwRwjYc rBzTEVtHrTclYTOo3+/4fJV1j/n/DWnnQGgmQjcSxZ1vRs7YBKjdk2hHwcsbRHFpgh93 fnEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=FpSn+5xavpYDKqHWQ7KBxWy/Cugpi9bykXKPflUY7zU=; b=ek6KJulEZ1ZLdbXMQbrUuJDr/Bs6AFFH200zq5VG3XK8I4w71+++a8BRl2Tsa4y9wj bLmeWAyywg7VqCPVU4Z8qzzimbpFeXXST0+ZZ3OkgItaFpTDS8seK8T8hN6MhOJ1AhRI 8ivaL+UzqbTgDrCHadVI6ucfB71awIhMR6Wv+zaKrZXJdEd+90UoaX9PeXvvrKkT7tSA 640dmS+z5PzutSJ/3Q+fLql0XtMaYnOL6Se1SSHzgRmrb4KqU2Y1H2ZtOk2k20O1V8p5 iQ7rOBi/r8LreJcKlr3iHIRzZw2NW5aG+BIGlJZY7+DEbC84UtdqTiB2dsTFO2OAbMDn 7DjQ== X-Gm-Message-State: AKwxytel1MbgTRqs9x5o10XZesCrdSZ4g9qm6yfFNOwQN5RxFOUlMJK2 BBguqxOAw1b9ufEeydtTSPI= X-Google-Smtp-Source: ACJfBouwhVQuKNjqD8Ut+9VS3qyrg0cnY3vEvYfcVatgRsKHu9Tcr21k/d3oK6y207lkIglUH7omig== X-Received: by 10.98.222.198 with SMTP id h189mr6434979pfg.150.1515699593924; Thu, 11 Jan 2018 11:39:53 -0800 (PST) Received: from ?IPv6:2601:646:8080:69b0:6d23:d51a:88d1:11f6? ([2601:646:8080:69b0:6d23:d51a:88d1:11f6]) by smtp.gmail.com with ESMTPSA id d20sm3773782pfe.166.2018.01.11.11.39.52 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 11 Jan 2018 11:39:52 -0800 (PST) Subject: Re: Publishing container images for Apache Spark Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_B056387B-2F49-4445-AEAB-50F37E94DF84" From: Craig Russell In-Reply-To: Date: Thu, 11 Jan 2018 11:39:51 -0800 Cc: dev Message-Id: <3B91231D-AC3D-4BD0-A5E9-3F1266CF6582@gmail.com> References: To: legal-discuss@apache.org X-Mailer: Apple Mail (2.3124) --Apple-Mail=_B056387B-2F49-4445-AEAB-50F37E94DF84 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, I think your summary is spot on. I don't see further issues. Craig > On Jan 11, 2018, at 9:18 AM, Erik Erlandson = wrote: >=20 > Dear ASF Legal Affairs Committee, >=20 > The Apache Spark development community has begun some discussions = about = publishing container images for Spark as part of its release process. = These discussions were spurred by the upstream adoption of a new = Kubernetes scheduling back-end, which by nature operates via container = images running Spark inside a Kubernetes cluster. >=20 > The current state of thinking on this topic is influenced by the = LEGAL-270 Jira which = can be summarized as: > * A container image has the same legal status as other derived = distributions > * As such, it is legally sound to publish a container image as long as = that image corresponds to an official project release > * An image that is regularly built from non-release code (e.g. a = 'spark:latest' image built from the head of master branch) would not be = legally approved > * The image should not contain any code or binaries that carry GPL = licenses, or other licenses considered incompatible with ASF. >=20 > We are reaching out to you to get your additional input on what = requirements the community should meet to engineer Apache Spark = container images that meet ASF legal guidelines. >=20 > The original dev@spark thread is here: > = http://apache-spark-developers-list.1001551.n3.nabble.com/Publishing-offic= ial-docker-images-for-KubernetesSchedulerBackend-td22928.html = >=20 > LEGAL-270: > https://issues.apache.org/jira/browse/LEGAL-270 = >=20 Craig L Russell Secretary, Apache Software Foundation clr@apache.org http://db.apache.org/jdo = --Apple-Mail=_B056387B-2F49-4445-AEAB-50F37E94DF84 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi,

I = think your summary is spot on. I don't see further issues.

Craig

On Jan 11, 2018, at 9:18 AM, Erik Erlandson <eerlands@redhat.com>= wrote:

Dear ASF Legal Affairs = Committee,

The Apache Spark = development community has begun some discussions about publishing container images for Spark = as part of its release process.  These discussions were spurred by = the upstream adoption of a new Kubernetes scheduling back-end, which by = nature operates via container images running Spark inside a Kubernetes = cluster.
The current state of thinking on this = topic is influenced by the LEGAL-270 Jira which can be summarized as:
* A container image has the same legal status as other = derived distributions
* As such, it is legally = sound to publish a container image as long as that image corresponds to = an official project release
* An image that is = regularly built from non-release code (e.g. a 'spark:latest' image built = from the head of master branch) would not be legally approved
* The image should not contain any code or binaries that = carry GPL licenses, or other licenses considered incompatible with = ASF.

We are reaching out to you to get your additional input on = what requirements the community should meet to engineer Apache Spark = container images that meet ASF legal guidelines.

The original dev@spark thread is = here:
http://apache-spark-developers-list.1001551.n3.nabble.com/Publi= shing-official-docker-images-for-KubernetesSchedulerBackend-td22928.html

LEGAL-270:
https://issues.apache.org/jira/browse/LEGAL-270


Craig L Russell
Secretary, Apache Software = Foundation
clr@apache.org http://db.apache.org/jdo

= --Apple-Mail=_B056387B-2F49-4445-AEAB-50F37E94DF84--