You don't; that is - it's up to the iCLA signer to represent that they have
the legal authority to sign the darned thing.
A cCLA kicks in when 1) the -company- is granting code, on a continuing basis,
and wants to make clear that all ongoing corporate-owned IP continues to be
granted to the ASF for their granted code; and 2) when the -individual- decides
they do not have the basis to sign the grant alone, as their work is for-hire
or other law kicks in which grants their efforts to their employer. For example
in California the work you do on your own time, on your own equipment, is yours.
But in other jurisdictions, unless part of your employment contract, what you do
in the evenings is the IP of your employer. It's up to the developer to know
their employment contract and law with respect to the code that is their's to
grant, and seek a cCLA when appropriate.
So if you ask someone for an iCLA, and they state they can't, give them -also-
the reference to the cCLA and have them approach their employer.
Bill
Alan D. Cabrera wrote:
The requirement for iCLAs is pretty straightforward. What is the rule
for requiring CCLAs? How do I, on the Apache side, perform due
diligence? Do I just point the candidates to the license page and ask
them to carefully read the material?
Regards,
Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
