cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebgoa <run...@gmail.com>
Subject Re: License to be signed for contributing to CloudStack
Date Mon, 02 Jun 2014 14:59:13 GMT

On May 30, 2014, at 10:57 PM, Ritu Sabharwal <rsabharw@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 <rsabharw@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 <rsabharw@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
> 


Mime
View raw message