Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 315E9E896 for ; Tue, 5 Feb 2013 21:37:39 +0000 (UTC) Received: (qmail 64693 invoked by uid 500); 5 Feb 2013 21:37:38 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 64658 invoked by uid 500); 5 Feb 2013 21:37:38 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 64649 invoked by uid 99); 5 Feb 2013 21:37:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 21:37:38 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of donal.lafferty@citrix.com designates 46.33.159.39 as permitted sender) Received: from [46.33.159.39] (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 21:37:33 +0000 X-IronPort-AV: E=Sophos;i="4.84,609,1355097600"; d="scan'208";a="1174084" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Feb 2013 21:37:13 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Tue, 5 Feb 2013 21:37:12 +0000 From: Donal Lafferty To: "cloudstack-dev@incubator.apache.org" , "'aemneina@gmail.com'" Date: Tue, 5 Feb 2013 21:37:11 +0000 Subject: RE: Redistributing 3rd party code licensed under Apache License 2.0 Thread-Topic: Redistributing 3rd party code licensed under Apache License 2.0 Thread-Index: Ac4D4mEVJYReko9CTTyk6VdPSTLUAAAAoJhQ Message-ID: <81A73678E76EA642801C8F2E4823AD2101418307076B@LONPMAILBOX01.citrite.net> References: <0A6C7CDA-9530-4260-9DF5-8A713118FF5A@gmail.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org To be clear, the 3rd party dependency is now limited to code written by Clo= ud.com, now owned by Citrix Systems. The background is that in 2010, Chiradeep wrote hyperv.py for the Diablo re= lease of OpenStack. The source is clearly copyrighted Cloud.com (see https= ://github.com/openstack/nova/blob/stable/diablo/nova/virt/hyperv.py). The = contributors license doesn't assign the copyright (see https://rackspace.ec= hosign.com/public/hostedForm?formid=3DXFNNZV3W23XE7N), rather it provides a= perpetual license. The code in this file was updated to remove dependenci= es on OpenStack and allow it to understand CloudStack commands, so it canno= t be reused unmodified. Since the code is going away after this release, a rewrite would have a ver= y short lifetime. Citrix has already donated a chunk of cloud.com IP to Apache CloudStack. C= an I not use the process for this file? DL > -----Original Message----- > From: Ahmad Emneina [mailto:aemneina@gmail.com] > Sent: 05 February 2013 20:49 > To: cloudstack-dev@incubator.apache.org > Subject: Re: Redistributing 3rd party code licensed under Apache License = 2.0 >=20 > +1 for write new apache code as per spec. since thats what will > +eventually > have to happen. >=20 >=20 > On Tue, Feb 5, 2013 at 12:47 PM, Sebastien Goasguen > wrote: >=20 > > > > On Feb 5, 2013, at 8:46 PM, Chip Childers > > wrote: > > > > > On Thu, Jan 31, 2013 at 4:56 PM, Chiradeep Vittal > > > wrote: > > >> I'd like Donal to offer up an alternative implementation if > > >> possible. Is this the long-term supportable implementation? Or is > > >> it just a hack to > > get > > >> things moving? > > > > > > OK - the thread on legal-discuss@a.o seems to have wound down. For > > > those interested, you can read it at [1]. > > > > > > The tl;dr version is: > > > > > > This isn't a legal problem, but it's a community issue. We have the > > > legal "right" to use that code, based on it's stated license. We do > > > NOT have the right to change the copyright headers, only to add our > > > own for the specific files where there were material changes. > > > > > > The community issue is more important though (and by community, we > > > are talking about the broader OSS community). The suggestion is > > > that we either (1) ask for permission before including this code in > > > our repo, or (2) find a way to use it as a dependent library. > > > > > > Given it's source (and what Donal has told me offline), I think we > > > are better off having this written as pure Apache code. If that's > > > not a possibility, then asking to include the code is important. > > > And further, we need to determine if we are going to "fork it" or > > > "maintain an upstream relationship" with the source. > > > > > > Thoughts? > > > > +1 to re-write as pure Apache code > > > > > > > > > > -chip > > > > > > [1] http://markmail.org/thread/ajmuxmxfdrcurswp > > > > > >> On 1/31/13 10:16 AM, "David Nalley" wrote: > > >> > > >>> On Thu, Jan 31, 2013 at 1:11 PM, Donal Lafferty > > >>> wrote: > > >>>> As a non-committer, developing in the Apache repository was never > > >>>> an option. > > >>>> > > >>>> Would Citrix want the Hyper-V driver it bought with Cloud.com? > > >>>> > > >>>> Is there a NOTICE-based means of including Apache Licence 2.0 > > >>>> code in the repository that originated with the OpenStack project? > > >>>> > > >>>> Should I put the driver in the 'extras' folder? > > >>>> > > >>>> I'm not sure what procedures are available. > > >>>> > > >>> > > >>> So, quite honestly, we don't know either. We've sought out advice > > >>> from mentors and they've pointed us to legal-discuss, and that > > >>> conversation is happening there now. Lets not get too concerned > > >>> until we find out what the folks who do know say and we can figure = a > path from there. > > >>> > > >>> --David > > >> > > >> > > > >