Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Ken Wallis <kwallis@rim.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Wed, 14 Dec 2011 19:58:16 -0500
Subject: Re: Callback CCLA questions
Thread-Topic: Callback CCLA questions
Thread-Index: Acy6wXJkziEApR68QgalPvKC0DzdbQAAy7Yc
Message-ID: <2225EEC9B3F7064AA3BDC6A62F70AAAE280222ECFC@XCH103CNC.rim.net>
In-Reply-To: <CB0E80AC.2186%fil@adobe.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0

Many companies (cough, eg. Rim) include in their employment contract that al=
l work done by an employee, unless specifically excluded, is owned by the co=
mpany.  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, G=
ord and I have NOT signed/submitted ICLA's.

----- Original Message -----
From: Filip Maj [mailto:fil@adobe.com]
Sent: Wednesday, December 14, 2011 07:35 PM=0A=
To: callback-dev@incubator.apache.org <callback-dev@incubator.apache.org>
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:
>https://github.com/callback/callback-ios/pull/36


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient 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 immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.