Okay, so the context for adding the phase 1 Hyper-V plugin to the actual release was to smooth the way for newbies. Adding features to the community code can be tricky for non-committers. Recall that last week I posted details on how to submit a multi-commit patch for review :)
With that in mind, here are the latest issues: 1. The IP concerns were a bit of a surprise, because IP expectations are not covered in the Design Doc template. Would anyone object if I updated https://cwiki.apache.org/CLOUDSTACK/design-document-template.html with a heading on 'IP Clearance' and a summary of Chip's comments (with references to orginal mailing list discussions)? 2. The Hyper-V patch includes fixes to cores CloudStack. Is the submission process for these fixes a) raise a defect, b) submit patch? 3. Feedback on the submission isn't captured in the Review Board submissions. Any objections to adding the points that David Nalley raises to the Review Board entry, and closing it? 4. Finally, where is the best place for 3rd party plugins? This point was raised in relation to the API client for C#. Any preferences for leaving 3rd party material stay in the developer's repo, or the 'extras' repo? DL > -----Original Message----- > From: David Nalley [mailto:da...@gnsa.us] > Sent: 05 February 2013 21:46 > To: Donal Lafferty > Cc: cloudstack-dev@incubator.apache.org; aemne...@gmail.com > Subject: Re: Redistributing 3rd party code licensed under Apache License 2.0 > > On Tue, Feb 5, 2013 at 4:37 PM, Donal Lafferty <donal.laffe...@citrix.com> > wrote: > > To be clear, the 3rd party dependency is now limited to code written by > Cloud.com, now owned by Citrix Systems. > > > > The background is that in 2010, Chiradeep wrote hyperv.py for the Diablo > release of OpenStack. The source is clearly copyrighted Cloud.com (see > https://github.com/openstack/nova/blob/stable/diablo/nova/virt/hyperv.p > y). The contributors license doesn't assign the copyright (see > https://rackspace.echosign.com/public/hostedForm?formid=XFNNZV3W23X > E7N), rather it provides a perpetual license. The code in this file was > updated > to remove dependencies on OpenStack and allow it to understand > CloudStack commands, so it cannot be reused unmodified. > > > > Since the code is going away after this release, a rewrite would have a very > short lifetime. > > > > Citrix has already donated a chunk of cloud.com IP to Apache CloudStack. > Can I not use the process for this file? > > > > > > DL > > > > So again, there is nothing legally wrong with it, but as Chip identified there > are community issues - and a number of people, including Chiradeep (who, > as you note, is the original author of the code you want to use) want to see > this be a fresh implementation. > We're already looking at 4.2 for this feature, and this is supposedly going to > have a short lifetime as a rewrite seems to be in your plans anyway, so I am > not sure of the efficacy of jumping through the process hoops in the short > term. (And while it's legally fine, there's still plenty of effort in the > process - > esp since the code you've identified is held by someone who is friendly to us > and the preference in the ASF is for voluntary contributions, we'd likely > 'prefer' to get a SGA for the code in question from Citrix - but as Prasanna > and Ram G can tell you - even simple things like that can linger on for months > to get the agreements signed) > > --David
