incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: Callback CCLA questions
Date Thu, 15 Dec 2011 09:17:01 GMT
ICLAs are require. CCLAs are optional (they exist because some comp admires
want them not because the ASF wants them).

It is not possible to get commit access to our repositories without an ICLA
on file. Please tell me how I can help with the situation with RIM
employees. You need to get permission to sign the ICLA.


Sent from my mobile device, please forgive errors and brevity.
On Dec 15, 2011 12:58 AM, "Ken Wallis" <> wrote:

> Many companies (cough, eg. Rim) include in their employment contract that
> all work done by an employee, unless specifically excluded, is owned by the
> company.  In those scenarios, the individual usually can't sign an ICLA as
> it is not applicable.  This is often a point of contention in many open
> source projects.  It would be good to clarify the Apache stance, as for
> example, Gord and I have NOT signed/submitted ICLA's.
> ----- Original Message -----
> From: Filip Maj []
> Sent: Wednesday, December 14, 2011 07:35 PM
> To: <>
> Subject: Re: Callback CCLA questions
> >Two questions:
> >
> >1. If a contributor's corporation has submitted a CCLA, does the
> >contributor have to sign an iCLA? (my hunch is no)
> Pretty sure it's a YES - just like us, we had to submit both.
> >2. How do I verify that a corporation has submitted their CCLA so I
> >can merge in a patch?
> There was a link floating around somewhere earlier... Check the mailing
> list archives?
> >
> >For reference, see:
> >
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message