You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by David Nalley <da...@gnsa.us> on 2012/11/07 12:20:58 UTC
Re: git commit: cli: pip install cloudmonkey works
Rohit:
I saw the below commit, and then this:
http://pypi.python.org/pypi/cloudmonkey/0.0.4
Is this a release of a portion of the CloudStack codebase? (This
wasn't in the 4.0.0-incubating release was it?)
Did I miss a discussion of the publication on list somewhere?
--David
On Tue, Nov 6, 2012 at 5:40 AM, <bh...@apache.org> wrote:
> Updated Branches:
> refs/heads/master a94f6f19b -> b71386530
>
>
> cli: pip install cloudmonkey works
>
> Patch makes cloudmonkey installable and redistributable using source dist from
> pypi under apache compliant license. Most visible issues have been solved and
> cloudmonkey should work well with CloudStack 4.0 and master, also until APIs do
> not change.
>
Re: git commit: cli: pip install cloudmonkey works
Posted by Chip Childers <ch...@sungard.com>.
On Sat, Nov 10, 2012 at 2:40 AM, Rohit Yadav <ro...@citrix.com> wrote:
> Hi Chip,
>
> I've added a notice on pypi page saying that it's not an official Apache CloudStack distribution, published and maintained by community member(s) and listed the author/maintainer fields as in tools/cli/setup.py: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob;f=tools/cli/setup.py;h=627a938e5ba1280356d42f02267e6eb6db47c6b1;hb=29978bdb8160c46fd8d047807b074048a7c7381d
Thanks for making this change Rohit!
> We can have more than one person as admin on the pypi distribution, please let me know I will add anyone who wants to administrate.
> Alright, if other projects do it along with their release process then we should upload it officially on pypi starting 4.1.0 after voting/release process.
We'll need to figure out how others handle the use of external package
repos, and community access. Should this be opened up for any
committer? Should it be limited to people that are acting as release
managers (which can actually be any committer)?
> Till 4.1.0 release we can keep the notice and use it for non-official releases.
> Lastly, not sure about listing ASF as the author, I used "The Apache CloudStack Team" (like in top level pom.xml).
Perfect!
> Regards.
>
> ________________________________________
> From: Chip Childers [chip.childers@sungard.com]
> Sent: Saturday, November 10, 2012 2:09 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: git commit: cli: pip install cloudmonkey works
>
> On Wed, Nov 7, 2012 at 7:27 AM, Rohit Yadav <ro...@citrix.com> wrote:
>>
>> On 07-Nov-2012, at 4:50 PM, David Nalley <da...@gnsa.us> wrote:
>>
>>> Rohit:
>>>
>>> I saw the below commit, and then this:
>>>
>>> http://pypi.python.org/pypi/cloudmonkey/0.0.4
>>>
>>> Is this a release of a portion of the CloudStack codebase? (This
>>> wasn't in the 4.0.0-incubating release was it?)
>>> Did I miss a discussion of the publication on list somewhere?
>>
>> I released it on pypi (cheese shop) without asking anyone. I did that so a user can simply get the cli using pip or easy_install.
>>
>> Do I need to go through some process to release the cli on pypi, think like maven snapshots?
>> I'm sorry if I did anything wrong, I'm unsure and don't know the release process for distributing client snapshots or python libs such as marvin which are within the source code. Starting 4.1.0 we can distribute cli etc. along with the release.
>>
>> Regards.
>
> First, let me say that I love the CLI, and am really happy to see it
> under development. Though now that I look at this closely, I think
> there might be a couple of issues to discuss here. This is IMO, so
> others should chime in.
>
> In reality, we're using the very permissive ASLv2 license for the
> project, and technically, on pypi, you've not identified the package
> as an official CloudStack project. You could consider that listing on
> Pypi as the "Rohit distro" of the tool. Also, you retain the
> copyright to your work and just grant a liberal license to the ASF.
> INAL, but AFAIK you did nothing *legally* wrong.
>
> Here's the part where I think we can work together to improve things:
>
> Obviously, Apache has not *released* any code that includes the
> cloudmonkey CLI tool yet, so that's one concern for us to consider.
> Second, what I've seen other projects do with package distro sites
> like this is to tie the updates / changes to the release process. For
> example, Deltacloud uploads their gems after voting and releasing the
> source.
>
> Should we consider operating in that way? Should we further consider
> posting to Pypi with The Apache Software Foundation as the listed
> author?
>
>
>>
>>>
>>> --David
>>>
>>> On Tue, Nov 6, 2012 at 5:40 AM, <bh...@apache.org> wrote:
>>>> Updated Branches:
>>>> refs/heads/master a94f6f19b -> b71386530
>>>>
>>>>
>>>> cli: pip install cloudmonkey works
>>>>
>>>> Patch makes cloudmonkey installable and redistributable using source dist from
>>>> pypi under apache compliant license. Most visible issues have been solved and
>>>> cloudmonkey should work well with CloudStack 4.0 and master, also until APIs do
>>>> not change.
>>>>
>>
>>
>
RE: git commit: cli: pip install cloudmonkey works
Posted by Rohit Yadav <ro...@citrix.com>.
Hi Chip,
I've added a notice on pypi page saying that it's not an official Apache CloudStack distribution, published and maintained by community member(s) and listed the author/maintainer fields as in tools/cli/setup.py: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob;f=tools/cli/setup.py;h=627a938e5ba1280356d42f02267e6eb6db47c6b1;hb=29978bdb8160c46fd8d047807b074048a7c7381d
We can have more than one person as admin on the pypi distribution, please let me know I will add anyone who wants to administrate.
Alright, if other projects do it along with their release process then we should upload it officially on pypi starting 4.1.0 after voting/release process.
Till 4.1.0 release we can keep the notice and use it for non-official releases.
Lastly, not sure about listing ASF as the author, I used "The Apache CloudStack Team" (like in top level pom.xml).
Regards.
________________________________________
From: Chip Childers [chip.childers@sungard.com]
Sent: Saturday, November 10, 2012 2:09 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: git commit: cli: pip install cloudmonkey works
On Wed, Nov 7, 2012 at 7:27 AM, Rohit Yadav <ro...@citrix.com> wrote:
>
> On 07-Nov-2012, at 4:50 PM, David Nalley <da...@gnsa.us> wrote:
>
>> Rohit:
>>
>> I saw the below commit, and then this:
>>
>> http://pypi.python.org/pypi/cloudmonkey/0.0.4
>>
>> Is this a release of a portion of the CloudStack codebase? (This
>> wasn't in the 4.0.0-incubating release was it?)
>> Did I miss a discussion of the publication on list somewhere?
>
> I released it on pypi (cheese shop) without asking anyone. I did that so a user can simply get the cli using pip or easy_install.
>
> Do I need to go through some process to release the cli on pypi, think like maven snapshots?
> I'm sorry if I did anything wrong, I'm unsure and don't know the release process for distributing client snapshots or python libs such as marvin which are within the source code. Starting 4.1.0 we can distribute cli etc. along with the release.
>
> Regards.
First, let me say that I love the CLI, and am really happy to see it
under development. Though now that I look at this closely, I think
there might be a couple of issues to discuss here. This is IMO, so
others should chime in.
In reality, we're using the very permissive ASLv2 license for the
project, and technically, on pypi, you've not identified the package
as an official CloudStack project. You could consider that listing on
Pypi as the "Rohit distro" of the tool. Also, you retain the
copyright to your work and just grant a liberal license to the ASF.
INAL, but AFAIK you did nothing *legally* wrong.
Here's the part where I think we can work together to improve things:
Obviously, Apache has not *released* any code that includes the
cloudmonkey CLI tool yet, so that's one concern for us to consider.
Second, what I've seen other projects do with package distro sites
like this is to tie the updates / changes to the release process. For
example, Deltacloud uploads their gems after voting and releasing the
source.
Should we consider operating in that way? Should we further consider
posting to Pypi with The Apache Software Foundation as the listed
author?
>
>>
>> --David
>>
>> On Tue, Nov 6, 2012 at 5:40 AM, <bh...@apache.org> wrote:
>>> Updated Branches:
>>> refs/heads/master a94f6f19b -> b71386530
>>>
>>>
>>> cli: pip install cloudmonkey works
>>>
>>> Patch makes cloudmonkey installable and redistributable using source dist from
>>> pypi under apache compliant license. Most visible issues have been solved and
>>> cloudmonkey should work well with CloudStack 4.0 and master, also until APIs do
>>> not change.
>>>
>
>
RE: git commit: cli: pip install cloudmonkey works
Posted by Rohit Yadav <ro...@citrix.com>.
I agree with you. So here's what I did, I added a notice stating that it's not an official distribution but added author as the whole CloudStack team and myself as maintainer. I don't know about the url, should I remove it? The version number is also different than CloudStack's (actually reverse). No harm intended, please let me know if I should change something.
Regards.
________________________________________
From: David Nalley [david@gnsa.us]
Sent: Saturday, November 10, 2012 3:51 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: git commit: cli: pip install cloudmonkey works
On Fri, Nov 9, 2012 at 3:39 PM, Chip Childers <ch...@sungard.com> wrote:
> On Wed, Nov 7, 2012 at 7:27 AM, Rohit Yadav <ro...@citrix.com> wrote:
>>
>> On 07-Nov-2012, at 4:50 PM, David Nalley <da...@gnsa.us> wrote:
>>
>>> Rohit:
>>>
>>> I saw the below commit, and then this:
>>>
>>> http://pypi.python.org/pypi/cloudmonkey/0.0.4
>>>
>>> Is this a release of a portion of the CloudStack codebase? (This
>>> wasn't in the 4.0.0-incubating release was it?)
>>> Did I miss a discussion of the publication on list somewhere?
>>
>> I released it on pypi (cheese shop) without asking anyone. I did that so a user can simply get the cli using pip or easy_install.
>>
>> Do I need to go through some process to release the cli on pypi, think like maven snapshots?
>> I'm sorry if I did anything wrong, I'm unsure and don't know the release process for distributing client snapshots or python libs such as marvin which are within the source code. Starting 4.1.0 we can distribute cli etc. along with the release.
>>
>> Regards.
>
> First, let me say that I love the CLI, and am really happy to see it
> under development. Though now that I look at this closely, I think
> there might be a couple of issues to discuss here. This is IMO, so
> others should chime in.
>
> In reality, we're using the very permissive ASLv2 license for the
> project, and technically, on pypi, you've not identified the package
> as an official CloudStack project. You could consider that listing on
> Pypi as the "Rohit distro" of the tool. Also, you retain the
> copyright to your work and just grant a liberal license to the ASF.
> INAL, but AFAIK you did nothing *legally* wrong.
This is largerly where my concern stems from. On pypi, you list the
project home as the project site. Which would seem to infer that it's
an ASF project. There's a 'release' with a release number; but the
project has not voted on that release, (and in our case, the IPMC
hasn't sanctioned such a release either). While I agree with Chip that
there is nothing legally wrong here, and if it was clearer that you
were doing this as an individual effort, and not publishing a release
on behalf of the project, it would be a non-issue; the process problem
within the ASF is problematic IMO.
>
> Here's the part where I think we can work together to improve things:
>
> Obviously, Apache has not *released* any code that includes the
> cloudmonkey CLI tool yet, so that's one concern for us to consider.
> Second, what I've seen other projects do with package distro sites
> like this is to tie the updates / changes to the release process. For
> example, Deltacloud uploads their gems after voting and releasing the
> source.
>
> Should we consider operating in that way? Should we further consider
> posting to Pypi with The Apache Software Foundation as the listed
> author?
Re: git commit: cli: pip install cloudmonkey works
Posted by David Nalley <da...@gnsa.us>.
On Fri, Nov 9, 2012 at 3:39 PM, Chip Childers <ch...@sungard.com> wrote:
> On Wed, Nov 7, 2012 at 7:27 AM, Rohit Yadav <ro...@citrix.com> wrote:
>>
>> On 07-Nov-2012, at 4:50 PM, David Nalley <da...@gnsa.us> wrote:
>>
>>> Rohit:
>>>
>>> I saw the below commit, and then this:
>>>
>>> http://pypi.python.org/pypi/cloudmonkey/0.0.4
>>>
>>> Is this a release of a portion of the CloudStack codebase? (This
>>> wasn't in the 4.0.0-incubating release was it?)
>>> Did I miss a discussion of the publication on list somewhere?
>>
>> I released it on pypi (cheese shop) without asking anyone. I did that so a user can simply get the cli using pip or easy_install.
>>
>> Do I need to go through some process to release the cli on pypi, think like maven snapshots?
>> I'm sorry if I did anything wrong, I'm unsure and don't know the release process for distributing client snapshots or python libs such as marvin which are within the source code. Starting 4.1.0 we can distribute cli etc. along with the release.
>>
>> Regards.
>
> First, let me say that I love the CLI, and am really happy to see it
> under development. Though now that I look at this closely, I think
> there might be a couple of issues to discuss here. This is IMO, so
> others should chime in.
>
> In reality, we're using the very permissive ASLv2 license for the
> project, and technically, on pypi, you've not identified the package
> as an official CloudStack project. You could consider that listing on
> Pypi as the "Rohit distro" of the tool. Also, you retain the
> copyright to your work and just grant a liberal license to the ASF.
> INAL, but AFAIK you did nothing *legally* wrong.
This is largerly where my concern stems from. On pypi, you list the
project home as the project site. Which would seem to infer that it's
an ASF project. There's a 'release' with a release number; but the
project has not voted on that release, (and in our case, the IPMC
hasn't sanctioned such a release either). While I agree with Chip that
there is nothing legally wrong here, and if it was clearer that you
were doing this as an individual effort, and not publishing a release
on behalf of the project, it would be a non-issue; the process problem
within the ASF is problematic IMO.
>
> Here's the part where I think we can work together to improve things:
>
> Obviously, Apache has not *released* any code that includes the
> cloudmonkey CLI tool yet, so that's one concern for us to consider.
> Second, what I've seen other projects do with package distro sites
> like this is to tie the updates / changes to the release process. For
> example, Deltacloud uploads their gems after voting and releasing the
> source.
>
> Should we consider operating in that way? Should we further consider
> posting to Pypi with The Apache Software Foundation as the listed
> author?
Re: git commit: cli: pip install cloudmonkey works
Posted by Chip Childers <ch...@sungard.com>.
On Wed, Nov 7, 2012 at 7:27 AM, Rohit Yadav <ro...@citrix.com> wrote:
>
> On 07-Nov-2012, at 4:50 PM, David Nalley <da...@gnsa.us> wrote:
>
>> Rohit:
>>
>> I saw the below commit, and then this:
>>
>> http://pypi.python.org/pypi/cloudmonkey/0.0.4
>>
>> Is this a release of a portion of the CloudStack codebase? (This
>> wasn't in the 4.0.0-incubating release was it?)
>> Did I miss a discussion of the publication on list somewhere?
>
> I released it on pypi (cheese shop) without asking anyone. I did that so a user can simply get the cli using pip or easy_install.
>
> Do I need to go through some process to release the cli on pypi, think like maven snapshots?
> I'm sorry if I did anything wrong, I'm unsure and don't know the release process for distributing client snapshots or python libs such as marvin which are within the source code. Starting 4.1.0 we can distribute cli etc. along with the release.
>
> Regards.
First, let me say that I love the CLI, and am really happy to see it
under development. Though now that I look at this closely, I think
there might be a couple of issues to discuss here. This is IMO, so
others should chime in.
In reality, we're using the very permissive ASLv2 license for the
project, and technically, on pypi, you've not identified the package
as an official CloudStack project. You could consider that listing on
Pypi as the "Rohit distro" of the tool. Also, you retain the
copyright to your work and just grant a liberal license to the ASF.
INAL, but AFAIK you did nothing *legally* wrong.
Here's the part where I think we can work together to improve things:
Obviously, Apache has not *released* any code that includes the
cloudmonkey CLI tool yet, so that's one concern for us to consider.
Second, what I've seen other projects do with package distro sites
like this is to tie the updates / changes to the release process. For
example, Deltacloud uploads their gems after voting and releasing the
source.
Should we consider operating in that way? Should we further consider
posting to Pypi with The Apache Software Foundation as the listed
author?
>
>>
>> --David
>>
>> On Tue, Nov 6, 2012 at 5:40 AM, <bh...@apache.org> wrote:
>>> Updated Branches:
>>> refs/heads/master a94f6f19b -> b71386530
>>>
>>>
>>> cli: pip install cloudmonkey works
>>>
>>> Patch makes cloudmonkey installable and redistributable using source dist from
>>> pypi under apache compliant license. Most visible issues have been solved and
>>> cloudmonkey should work well with CloudStack 4.0 and master, also until APIs do
>>> not change.
>>>
>
>
Re: git commit: cli: pip install cloudmonkey works
Posted by Rohit Yadav <ro...@citrix.com>.
On 07-Nov-2012, at 4:50 PM, David Nalley <da...@gnsa.us> wrote:
> Rohit:
>
> I saw the below commit, and then this:
>
> http://pypi.python.org/pypi/cloudmonkey/0.0.4
>
> Is this a release of a portion of the CloudStack codebase? (This
> wasn't in the 4.0.0-incubating release was it?)
> Did I miss a discussion of the publication on list somewhere?
I released it on pypi (cheese shop) without asking anyone. I did that so a user can simply get the cli using pip or easy_install.
Do I need to go through some process to release the cli on pypi, think like maven snapshots?
I'm sorry if I did anything wrong, I'm unsure and don't know the release process for distributing client snapshots or python libs such as marvin which are within the source code. Starting 4.1.0 we can distribute cli etc. along with the release.
Regards.
>
> --David
>
> On Tue, Nov 6, 2012 at 5:40 AM, <bh...@apache.org> wrote:
>> Updated Branches:
>> refs/heads/master a94f6f19b -> b71386530
>>
>>
>> cli: pip install cloudmonkey works
>>
>> Patch makes cloudmonkey installable and redistributable using source dist from
>> pypi under apache compliant license. Most visible issues have been solved and
>> cloudmonkey should work well with CloudStack 4.0 and master, also until APIs do
>> not change.
>>
Re: git commit: cli: pip install cloudmonkey works
Posted by Rohit Yadav <ro...@citrix.com>.
Hi David,
Yes, the cli is part of the codebase in master's tools/cli and license wise compliant.
No, it was not part of 4.0 and was recently committed only last week to fix this feature issue:
https://issues.apache.org/jira/browse/CLOUDSTACK-132
which was requested here too:
https://issues.apache.org/jira/browse/CLOUDSTACK-367
and you may search ML for CLI related emails.
It's not part of the 4.0 release, but will work for 4.0 release and later as long as APIs don't change and are backwards compatible.
I put that on pypi so anyone can give it a try.
Regards,
Rohit
On 07-Nov-2012, at 4:50 PM, David Nalley <da...@gnsa.us> wrote:
> Rohit:
>
> I saw the below commit, and then this:
>
> http://pypi.python.org/pypi/cloudmonkey/0.0.4
>
> Is this a release of a portion of the CloudStack codebase? (This
> wasn't in the 4.0.0-incubating release was it?)
> Did I miss a discussion of the publication on list somewhere?
>
> --David
>
> On Tue, Nov 6, 2012 at 5:40 AM, <bh...@apache.org> wrote:
>> Updated Branches:
>> refs/heads/master a94f6f19b -> b71386530
>>
>>
>> cli: pip install cloudmonkey works
>>
>> Patch makes cloudmonkey installable and redistributable using source dist from
>> pypi under apache compliant license. Most visible issues have been solved and
>> cloudmonkey should work well with CloudStack 4.0 and master, also until APIs do
>> not change.
>>