Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 866C8CDFD for ; Wed, 12 Mar 2014 19:29:29 +0000 (UTC) Received: (qmail 14207 invoked by uid 500); 12 Mar 2014 19:29:15 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 13997 invoked by uid 500); 12 Mar 2014 19:29:10 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 13989 invoked by uid 99); 12 Mar 2014 19:29:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Mar 2014 19:29:09 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_DBL_REDIR X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jghoman@gmail.com designates 209.85.192.178 as permitted sender) Received: from [209.85.192.178] (HELO mail-pd0-f178.google.com) (209.85.192.178) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Mar 2014 19:29:05 +0000 Received: by mail-pd0-f178.google.com with SMTP id x10so1493846pdj.9 for ; Wed, 12 Mar 2014 12:28:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=IIqr4FTx1xuz3t2nbBvqe2BFtnNmC3O5fv8MsoX8IU0=; b=yqAck/J5qL3rSxqojpokTngLI8DgkV9cf5w3tkujBBW+pgnh3/djTLAH4UhxL8/Cpr T3OzKlPavOlrkpNN+v9IXr9UPWRdM5E8c3xxaP+8wtrt+9a2/iDg47xvb/EDJ41FA7XW 3aTHuMZmN8YFqeMisoAYn+AkUNLY3M4CKtBoWom0lZHtT+h/St7PYAw8hGgynbcKoWdJ 7ENZFq9MyfMW+gt6dSpFdNdwO5EiKmBu92bjsbjEE6L4A2LXDkL0bVA4hSo3dy7ae6Sl GJ5SZ0oLkvcbUov6ntlKU1Jwz+S3AeR9QgtrAB4/7T4I4fO/d0i2/SMLvCZBtsdM5dbw 1Icg== X-Received: by 10.66.177.168 with SMTP id cr8mr7135127pac.128.1394652523808; Wed, 12 Mar 2014 12:28:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.103.98 with HTTP; Wed, 12 Mar 2014 12:28:13 -0700 (PDT) From: Jakob Homan Date: Wed, 12 Mar 2014 12:28:13 -0700 Message-ID: Subject: Second git import from already existing podling with original CCLA blessing? To: "general@incubator.apache.org" Content-Type: multipart/alternative; boundary=047d7bdc952c444cae04f46dd8c8 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc952c444cae04f46dd8c8 Content-Type: text/plain; charset=ISO-8859-1 re: Samza We've got a second git repository we'd like to import, https://github.com/linkedin/hello-samza, which is a tutorial and quickstart on the Samza project. This was originally kept separate from the code for two reasons (a) making it stand-alone made it easier for it just be turn-key after cloning and (b) to make it faster to iterate on. However, it's turned out there's lots of interest in the hello-samza itself, which is being directed towards the podling. I started work on IP clearance to import it in, but when I talked with LI's legal department about a second CCLA (per the IP Clearance page), they were of the opinion that the original CCLA covered this repo as well: LI counsel on open source matters: "Hello-samza is ancillary to Samza and thus fits within a broadly interpreted Exhibit B to the original Samza CCLA. In other words, it's already covered, with no legal need for a new CCLA. Also worth noting that we're the donor of both Samza and hello-samza, so a key problem that would be resolved by having the separate, new CCLA (i.e. substantial donation of code by a different company) is actually a problem we do not have." This sounds reasonable to me and saves some paperwork. Are there any objections to just importing the second git repo? The Samza community has voted to incorporate the code: http://bit.ly/1lX414U -Jakob --047d7bdc952c444cae04f46dd8c8--