You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Ritu Sabharwal <rs...@Brocade.com> on 2014/05/30 00:10:45 UTC
License to be signed for contributing to CloudStack
Hi,
I wanted to know if there are any license to be signed by individuals or corporates to contribute to CloudStack.
Thanks & Regards,
Ritu S.
Re: License to be signed for contributing to CloudStack
Posted by sebgoa <ru...@gmail.com>.
On Jun 2, 2014, at 7:13 PM, Ritu Sabharwal <rs...@Brocade.com> wrote:
> Hi Chip,
>
> Thanks for the information.
>
> I created a JIRA bug for the plugin development CLOUDSTACK-6823.
>
> I don't have the Edit permissions to edit the wiki to add the design spec.
>
> User ID: rsabharw
you should be good to go now,
>
> Can I get the edit permissions to edit the wiki please?
>
> Thanks & Regards,
> Ritu S.
>
>
> -----Original Message-----
> From: Chip Childers [mailto:chipchilders@apache.org]
> Sent: Monday, June 02, 2014 7:53 AM
> To: dev@cloudstack.apache.org
> Cc: runseb@gmail.com; David Nalley; ilya musayev
> Subject: Re: License to be signed for contributing to CloudStack
>
> On Fri, May 30, 2014 at 01:57:13PM -0700, Ritu Sabharwal wrote:
>> Hi Sebastian,
>>
>> This gives a real good picture of the IP clearance process.
>>
>> I sent a Proposal email to mailing list last week, still waiting for acceptance. Can you please have a look at it and provide feedback?
>
> Don't assume that it requires any acceptance. Apache projects operate on the idea of lazy consensus, which means that a proposal like this is really only something that will be commented on if there is a strong opinion (on how to do it, or to do / not do it). Silence means consent, but that's another reason to incrementally submit patches as work in progress. That will ensure that you are seeing the results of your work get into our repo as you progress (and provide opportunities for individuals that might not have read the proposal to help guide the implementation).
>
>>
>> I am in the state to submit my design document to CloudStack wiki. I have created account on JIRA, Review Board and CloudStack wiki. I need permissions to contribute. Can you please give these permissions?
>>
>
> You are all set for JIRA. IIRC, you should be able to edit the wiki if you create an account on it.
>
>> It would be good to create a branch for Brocade plugin and we can submitting patches for review to Review Board in another one week .
>>
>
> We will do that (likely) when the first patch comes in. Please provide a note in the submission asking for a new branch.
>
>> Thanks & Regards,
>> Ritu S.
RE: License to be signed for contributing to CloudStack
Posted by Ritu Sabharwal <rs...@Brocade.com>.
Hi Chip,
Thanks for the information.
I created a JIRA bug for the plugin development CLOUDSTACK-6823.
I don't have the Edit permissions to edit the wiki to add the design spec.
User ID: rsabharw
Can I get the edit permissions to edit the wiki please?
Thanks & Regards,
Ritu S.
-----Original Message-----
From: Chip Childers [mailto:chipchilders@apache.org]
Sent: Monday, June 02, 2014 7:53 AM
To: dev@cloudstack.apache.org
Cc: runseb@gmail.com; David Nalley; ilya musayev
Subject: Re: License to be signed for contributing to CloudStack
On Fri, May 30, 2014 at 01:57:13PM -0700, Ritu Sabharwal wrote:
> Hi Sebastian,
>
> This gives a real good picture of the IP clearance process.
>
> I sent a Proposal email to mailing list last week, still waiting for acceptance. Can you please have a look at it and provide feedback?
Don't assume that it requires any acceptance. Apache projects operate on the idea of lazy consensus, which means that a proposal like this is really only something that will be commented on if there is a strong opinion (on how to do it, or to do / not do it). Silence means consent, but that's another reason to incrementally submit patches as work in progress. That will ensure that you are seeing the results of your work get into our repo as you progress (and provide opportunities for individuals that might not have read the proposal to help guide the implementation).
>
> I am in the state to submit my design document to CloudStack wiki. I have created account on JIRA, Review Board and CloudStack wiki. I need permissions to contribute. Can you please give these permissions?
>
You are all set for JIRA. IIRC, you should be able to edit the wiki if you create an account on it.
> It would be good to create a branch for Brocade plugin and we can submitting patches for review to Review Board in another one week .
>
We will do that (likely) when the first patch comes in. Please provide a note in the submission asking for a new branch.
> Thanks & Regards,
> Ritu S.
Re: License to be signed for contributing to CloudStack
Posted by Chip Childers <ch...@apache.org>.
On Fri, May 30, 2014 at 01:57:13PM -0700, Ritu Sabharwal wrote:
> Hi Sebastian,
>
> This gives a real good picture of the IP clearance process.
>
> I sent a Proposal email to mailing list last week, still waiting for acceptance. Can you please have a look at it and provide feedback?
Don't assume that it requires any acceptance. Apache projects operate
on the idea of lazy consensus, which means that a proposal like this is
really only something that will be commented on if there is a strong
opinion (on how to do it, or to do / not do it). Silence means consent,
but that's another reason to incrementally submit patches as work in
progress. That will ensure that you are seeing the results of your work
get into our repo as you progress (and provide opportunities for
individuals that might not have read the proposal to help guide the
implementation).
>
> I am in the state to submit my design document to CloudStack wiki. I have created account on JIRA, Review Board and CloudStack wiki. I need permissions to contribute. Can you please give these permissions?
>
You are all set for JIRA. IIRC, you should be able to edit the wiki if
you create an account on it.
> It would be good to create a branch for Brocade plugin and we can submitting patches for review to Review Board in another one week .
>
We will do that (likely) when the first patch comes in. Please provide
a note in the submission asking for a new branch.
> Thanks & Regards,
> Ritu S.
RE: License to be signed for contributing to CloudStack
Posted by Ritu Sabharwal <rs...@Brocade.com>.
Hi Sebastian,
Right now I am the only author for the plugin. Will add more to the wiki and Review Board as an when people join me.
Thanks & Regards,
Ritu S.
-----Original Message-----
From: sebgoa [mailto:runseb@gmail.com]
Sent: Monday, June 02, 2014 7:59 AM
To: Ritu Sabharwal
Cc: dev@cloudstack.apache.org; David Nalley; ilya musayev
Subject: Re: License to be signed for contributing to CloudStack
On May 30, 2014, at 10:57 PM, Ritu Sabharwal <rs...@Brocade.com> wrote:
> Hi Sebastian,
>
> This gives a real good picture of the IP clearance process.
>
> I sent a Proposal email to mailing list last week, still waiting for acceptance. Can you please have a look at it and provide feedback?
>
> I am in the state to submit my design document to CloudStack wiki. I have created account on JIRA, Review Board and CloudStack wiki. I need permissions to contribute. Can you please give these permissions?
>
> It would be good to create a branch for Brocade plugin and we can submitting patches for review to Review Board in another one week .
Just be careful with that *we*. Every code author should submit his own patches.
>
> Thanks & Regards,
> Ritu S.
>
> -----Original Message-----
> From: Sebastien Goasguen [mailto:runseb@gmail.com]
> Sent: Friday, May 30, 2014 12:42 PM
> To: dev@cloudstack.apache.org
> Cc: David Nalley; ilya musayev
> Subject: Re: License to be signed for contributing to CloudStack
>
>
> On May 30, 2014, at 1:55 PM, Ritu Sabharwal <rs...@Brocade.com> wrote:
>
>> Hi ilya, David,
>>
>> Thanks for the information!
>>
>> I am working with Brocade Communications Systems and we are implementing a network plugin for their VDX integration for L2 services. We are targeting for 4.5 release.
>>
>> Some follow up questions:
>>
>> 1. Since I am not an Apache committer, I need not sign an Individual Contributor License Agreement?
>
> Correct. You only sign an ICLA when you get invited to become a committer.
>
>> 2. For IP Clearance form for the plugin code, when do we send an email for the IP clearance and vote? Is it after the code review at the time of code merge to master branch?
>>
>
> I don't know what's the state of the plugin right now. But if it's developed from scratch, just start submitting patches to cloudstack via review board. The sooner you do this, the less likely you will face IP clearance issues. These issues tend to arise when code has been developed behind closed doors and with many authors. You raising this issue on the list is already a good start. I would recommend you submit patches (even though incomplete) yesterday :). We can create a brocade plugin branch for you, then you and other colleagues working on this should submit incremental patches. As we review the patches, we gain trust in you and your code, and most likely there will be no need for IP clearance. Something important to keep in mind is authorship. Do not submit code (via review board) that you have not written.
>
> Trying to avoid IP clearance is good -because it's a headache-.
>
>> Thanks & Regards,
>> Ritu S.
>>
>> -----Original Message-----
>> From: David Nalley [mailto:david@gnsa.us]
>> Sent: Thursday, May 29, 2014 6:13 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: License to be signed for contributing to CloudStack
>>
>> On Thu, May 29, 2014 at 6:10 PM, Ritu Sabharwal <rs...@brocade.com> wrote:
>>> Hi,
>>>
>>>
>>>
>>> I wanted to know if there are any license to be signed by individuals or corporates to contribute to CloudStack.
>>>
>>> Thanks & Regards,
>>> Ritu S.
>>
>>
>> So, it depends.
>> If you or your company is donating a significant contribution of code that was developed outside of the project; you probably need to go through IP Clearance. That typically involves a Software Grant Agreement or Contributor License Agreement.
>>
>> If you or your company are donating code that was developed inside the project, you probably don't need to sign anything unless it's a very large contribution.
>>
>> Also note that committers must sign an individual contributor license agreement for their account to be created.
>>
>> --David
>
Re: License to be signed for contributing to CloudStack
Posted by sebgoa <ru...@gmail.com>.
On May 30, 2014, at 10:57 PM, Ritu Sabharwal <rs...@Brocade.com> wrote:
> Hi Sebastian,
>
> This gives a real good picture of the IP clearance process.
>
> I sent a Proposal email to mailing list last week, still waiting for acceptance. Can you please have a look at it and provide feedback?
>
> I am in the state to submit my design document to CloudStack wiki. I have created account on JIRA, Review Board and CloudStack wiki. I need permissions to contribute. Can you please give these permissions?
>
> It would be good to create a branch for Brocade plugin and we can submitting patches for review to Review Board in another one week .
Just be careful with that *we*. Every code author should submit his own patches.
>
> Thanks & Regards,
> Ritu S.
>
> -----Original Message-----
> From: Sebastien Goasguen [mailto:runseb@gmail.com]
> Sent: Friday, May 30, 2014 12:42 PM
> To: dev@cloudstack.apache.org
> Cc: David Nalley; ilya musayev
> Subject: Re: License to be signed for contributing to CloudStack
>
>
> On May 30, 2014, at 1:55 PM, Ritu Sabharwal <rs...@Brocade.com> wrote:
>
>> Hi ilya, David,
>>
>> Thanks for the information!
>>
>> I am working with Brocade Communications Systems and we are implementing a network plugin for their VDX integration for L2 services. We are targeting for 4.5 release.
>>
>> Some follow up questions:
>>
>> 1. Since I am not an Apache committer, I need not sign an Individual Contributor License Agreement?
>
> Correct. You only sign an ICLA when you get invited to become a committer.
>
>> 2. For IP Clearance form for the plugin code, when do we send an email for the IP clearance and vote? Is it after the code review at the time of code merge to master branch?
>>
>
> I don't know what's the state of the plugin right now. But if it's developed from scratch, just start submitting patches to cloudstack via review board. The sooner you do this, the less likely you will face IP clearance issues. These issues tend to arise when code has been developed behind closed doors and with many authors. You raising this issue on the list is already a good start. I would recommend you submit patches (even though incomplete) yesterday :). We can create a brocade plugin branch for you, then you and other colleagues working on this should submit incremental patches. As we review the patches, we gain trust in you and your code, and most likely there will be no need for IP clearance. Something important to keep in mind is authorship. Do not submit code (via review board) that you have not written.
>
> Trying to avoid IP clearance is good -because it's a headache-.
>
>> Thanks & Regards,
>> Ritu S.
>>
>> -----Original Message-----
>> From: David Nalley [mailto:david@gnsa.us]
>> Sent: Thursday, May 29, 2014 6:13 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: License to be signed for contributing to CloudStack
>>
>> On Thu, May 29, 2014 at 6:10 PM, Ritu Sabharwal <rs...@brocade.com> wrote:
>>> Hi,
>>>
>>>
>>>
>>> I wanted to know if there are any license to be signed by individuals or corporates to contribute to CloudStack.
>>>
>>> Thanks & Regards,
>>> Ritu S.
>>
>>
>> So, it depends.
>> If you or your company is donating a significant contribution of code that was developed outside of the project; you probably need to go through IP Clearance. That typically involves a Software Grant Agreement or Contributor License Agreement.
>>
>> If you or your company are donating code that was developed inside the project, you probably don't need to sign anything unless it's a very large contribution.
>>
>> Also note that committers must sign an individual contributor license agreement for their account to be created.
>>
>> --David
>
RE: License to be signed for contributing to CloudStack
Posted by Ritu Sabharwal <rs...@Brocade.com>.
Hi Sebastian,
This gives a real good picture of the IP clearance process.
I sent a Proposal email to mailing list last week, still waiting for acceptance. Can you please have a look at it and provide feedback?
I am in the state to submit my design document to CloudStack wiki. I have created account on JIRA, Review Board and CloudStack wiki. I need permissions to contribute. Can you please give these permissions?
It would be good to create a branch for Brocade plugin and we can submitting patches for review to Review Board in another one week .
Thanks & Regards,
Ritu S.
-----Original Message-----
From: Sebastien Goasguen [mailto:runseb@gmail.com]
Sent: Friday, May 30, 2014 12:42 PM
To: dev@cloudstack.apache.org
Cc: David Nalley; ilya musayev
Subject: Re: License to be signed for contributing to CloudStack
On May 30, 2014, at 1:55 PM, Ritu Sabharwal <rs...@Brocade.com> wrote:
> Hi ilya, David,
>
> Thanks for the information!
>
> I am working with Brocade Communications Systems and we are implementing a network plugin for their VDX integration for L2 services. We are targeting for 4.5 release.
>
> Some follow up questions:
>
> 1. Since I am not an Apache committer, I need not sign an Individual Contributor License Agreement?
Correct. You only sign an ICLA when you get invited to become a committer.
> 2. For IP Clearance form for the plugin code, when do we send an email for the IP clearance and vote? Is it after the code review at the time of code merge to master branch?
>
I don't know what's the state of the plugin right now. But if it's developed from scratch, just start submitting patches to cloudstack via review board. The sooner you do this, the less likely you will face IP clearance issues. These issues tend to arise when code has been developed behind closed doors and with many authors. You raising this issue on the list is already a good start. I would recommend you submit patches (even though incomplete) yesterday :). We can create a brocade plugin branch for you, then you and other colleagues working on this should submit incremental patches. As we review the patches, we gain trust in you and your code, and most likely there will be no need for IP clearance. Something important to keep in mind is authorship. Do not submit code (via review board) that you have not written.
Trying to avoid IP clearance is good -because it's a headache-.
> Thanks & Regards,
> Ritu S.
>
> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Thursday, May 29, 2014 6:13 PM
> To: dev@cloudstack.apache.org
> Subject: Re: License to be signed for contributing to CloudStack
>
> On Thu, May 29, 2014 at 6:10 PM, Ritu Sabharwal <rs...@brocade.com> wrote:
>> Hi,
>>
>>
>>
>> I wanted to know if there are any license to be signed by individuals or corporates to contribute to CloudStack.
>>
>> Thanks & Regards,
>> Ritu S.
>
>
> So, it depends.
> If you or your company is donating a significant contribution of code that was developed outside of the project; you probably need to go through IP Clearance. That typically involves a Software Grant Agreement or Contributor License Agreement.
>
> If you or your company are donating code that was developed inside the project, you probably don't need to sign anything unless it's a very large contribution.
>
> Also note that committers must sign an individual contributor license agreement for their account to be created.
>
> --David
Re: License to be signed for contributing to CloudStack
Posted by Sebastien Goasguen <ru...@gmail.com>.
On May 30, 2014, at 1:55 PM, Ritu Sabharwal <rs...@Brocade.com> wrote:
> Hi ilya, David,
>
> Thanks for the information!
>
> I am working with Brocade Communications Systems and we are implementing a network plugin for their VDX integration for L2 services. We are targeting for 4.5 release.
>
> Some follow up questions:
>
> 1. Since I am not an Apache committer, I need not sign an Individual Contributor License Agreement?
Correct. You only sign an ICLA when you get invited to become a committer.
> 2. For IP Clearance form for the plugin code, when do we send an email for the IP clearance and vote? Is it after the code review at the time of code merge to master branch?
>
I don't know what's the state of the plugin right now. But if it's developed from scratch, just start submitting patches to cloudstack via review board. The sooner you do this, the less likely you will face IP clearance issues. These issues tend to arise when code has been developed behind closed doors and with many authors. You raising this issue on the list is already a good start. I would recommend you submit patches (even though incomplete) yesterday :). We can create a brocade plugin branch for you, then you and other colleagues working on this should submit incremental patches. As we review the patches, we gain trust in you and your code, and most likely there will be no need for IP clearance. Something important to keep in mind is authorship. Do not submit code (via review board) that you have not written.
Trying to avoid IP clearance is good -because it's a headache-.
> Thanks & Regards,
> Ritu S.
>
> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Thursday, May 29, 2014 6:13 PM
> To: dev@cloudstack.apache.org
> Subject: Re: License to be signed for contributing to CloudStack
>
> On Thu, May 29, 2014 at 6:10 PM, Ritu Sabharwal <rs...@brocade.com> wrote:
>> Hi,
>>
>>
>>
>> I wanted to know if there are any license to be signed by individuals or corporates to contribute to CloudStack.
>>
>> Thanks & Regards,
>> Ritu S.
>
>
> So, it depends.
> If you or your company is donating a significant contribution of code that was developed outside of the project; you probably need to go through IP Clearance. That typically involves a Software Grant Agreement or Contributor License Agreement.
>
> If you or your company are donating code that was developed inside the project, you probably don't need to sign anything unless it's a very large contribution.
>
> Also note that committers must sign an individual contributor license agreement for their account to be created.
>
> --David
RE: License to be signed for contributing to CloudStack
Posted by Ritu Sabharwal <rs...@Brocade.com>.
Hi ilya, David,
Thanks for the information!
I am working with Brocade Communications Systems and we are implementing a network plugin for their VDX integration for L2 services. We are targeting for 4.5 release.
Some follow up questions:
1. Since I am not an Apache committer, I need not sign an Individual Contributor License Agreement?
2. For IP Clearance form for the plugin code, when do we send an email for the IP clearance and vote? Is it after the code review at the time of code merge to master branch?
Thanks & Regards,
Ritu S.
-----Original Message-----
From: David Nalley [mailto:david@gnsa.us]
Sent: Thursday, May 29, 2014 6:13 PM
To: dev@cloudstack.apache.org
Subject: Re: License to be signed for contributing to CloudStack
On Thu, May 29, 2014 at 6:10 PM, Ritu Sabharwal <rs...@brocade.com> wrote:
> Hi,
>
>
>
> I wanted to know if there are any license to be signed by individuals or corporates to contribute to CloudStack.
>
> Thanks & Regards,
> Ritu S.
So, it depends.
If you or your company is donating a significant contribution of code that was developed outside of the project; you probably need to go through IP Clearance. That typically involves a Software Grant Agreement or Contributor License Agreement.
If you or your company are donating code that was developed inside the project, you probably don't need to sign anything unless it's a very large contribution.
Also note that committers must sign an individual contributor license agreement for their account to be created.
--David
Re: License to be signed for contributing to CloudStack
Posted by David Nalley <da...@gnsa.us>.
On Thu, May 29, 2014 at 6:10 PM, Ritu Sabharwal <rs...@brocade.com> wrote:
> Hi,
>
>
>
> I wanted to know if there are any license to be signed by individuals or corporates to contribute to CloudStack.
>
> Thanks & Regards,
> Ritu S.
So, it depends.
If you or your company is donating a significant contribution of code
that was developed outside of the project; you probably need to go
through IP Clearance. That typically involves a Software Grant
Agreement or Contributor License Agreement.
If you or your company are donating code that was developed inside the
project, you probably don't need to sign anything unless it's a very
large contribution.
Also note that committers must sign an individual contributor license
agreement for their account to be created.
--David
Re: License to be signed for contributing to CloudStack
Posted by ilya musayev <il...@gmail.com>.
Ritu,
Many companies donate their code to apache cloudstack. There is no
license to sign, however there is Intellectual Property Clearance
process you need to go through. From what i recall, you describe what it
is you would like to donate, we put it to a vote and once approved the
code is merged.
Here is an example
http://osdir.com/ml/general.incubator.apache.org/2013-01/msg00309.html
More folks can chime in and explain.
Regards
ilya
On 5/29/14, 3:10 PM, Ritu Sabharwal wrote:
> Hi,
>
>
>
> I wanted to know if there are any license to be signed by individuals or corporates to contribute to CloudStack.
>
> Thanks & Regards,
> Ritu S.
>