Re: XAPI API (aka xenserver-java)

[David Nalley <da...@gnsa.us>]

On Sun, May 20, 2012 at 4:02 PM, Mike McClurg <mi...@gmail.com> wrote:
> On Sat, May 19, 2012 at 4:12 AM, David Nalley <da...@gnsa.us> wrote:
>> I just looked at xenserverjava (the version shipped today 5.6.100-1,
>> and 6.0.0-1)
>>
>> However, while there is a copy of ASLv2 in the source, it does so
>> because some dependencies that it uses are licensed under ASLv2, but
>> the actual code itself has only GPLv2 headers.
>
> David,
>
> Thanks for spotting that. As I said, we should have no problem
> changing the license to something more suitable. I have a few
> questions.
>
> - What is the best license to release this software under? I expect
> that a permissive, BSD-like license would be acceptable for the Apache
> Foundation, yes?
>
> - Will it be necessary to also release the API generation code as
> well? This is something I want to do anyway, but I want to know if it
> will be required for the Apache Foundation.
>
> - Will we have to re-license and re-publish previously released
> versions of the xenserverjava library? Which versions does CloudStack
> depend on? Would it instead be sufficient to re-license the library in
> the next version of XenServer?
>
> Thanks,
>
> Mike

Hey Mike,

Any update on this relicensing issue? We have a proposed code freeze
in ~1 week, and AFAIK it's been around 2 months since I've seen any
updates on this.

--David

Re: XAPI API (aka xenserver-java)

[David Nalley <da...@gnsa.us>]

Mike:

Any update on this?

--David

On Mon, Jul 30, 2012 at 8:17 PM, David Nalley <da...@gnsa.us> wrote:
> On Sun, May 20, 2012 at 4:02 PM, Mike McClurg <mi...@gmail.com> wrote:
>> On Sat, May 19, 2012 at 4:12 AM, David Nalley <da...@gnsa.us> wrote:
>>> I just looked at xenserverjava (the version shipped today 5.6.100-1,
>>> and 6.0.0-1)
>>>
>>> However, while there is a copy of ASLv2 in the source, it does so
>>> because some dependencies that it uses are licensed under ASLv2, but
>>> the actual code itself has only GPLv2 headers.
>>
>> David,
>>
>> Thanks for spotting that. As I said, we should have no problem
>> changing the license to something more suitable. I have a few
>> questions.
>>
>> - What is the best license to release this software under? I expect
>> that a permissive, BSD-like license would be acceptable for the Apache
>> Foundation, yes?
>>
>> - Will it be necessary to also release the API generation code as
>> well? This is something I want to do anyway, but I want to know if it
>> will be required for the Apache Foundation.
>>
>> - Will we have to re-license and re-publish previously released
>> versions of the xenserverjava library? Which versions does CloudStack
>> depend on? Would it instead be sufficient to re-license the library in
>> the next version of XenServer?
>>
>> Thanks,
>>
>> Mike
>
> Hey Mike,
>
> Any update on this relicensing issue? We have a proposed code freeze
> in ~1 week, and AFAIK it's been around 2 months since I've seen any
> updates on this.
>
> --David