Hi Ted,

That is an interesting question. Does anyone know if the Schedule B mechanism has been used before with corporate OpenStack contributions? The idea (I think) is that the CCLA identifies a specific, and presumably 'large', set of code that is covered by the CCLA (not to the exclusion of other contributions).

In the ancestral Apache context, CCLAs are normally not signed at all, and where they are I don't know whether 'Schedule B' (which exists in the Apache CCLA too) has ever been used. When Red Hat sought in some past cases to transfer substantial codebases to the ASF, we were typically asked to sign a separate document called a 'Software Grant'. (The term 'software grant' is also used in the CCLA Schedule B.)

- Richard

On Mon, Jul 07, 2014 at 09:21:23PM -0400, McCullough, Theodore wrote:

Hi Folks:

I am interested in using the CCLA Schedule B as a vehicle to make contributions as per the OpenStack CCLA- “Contribution” shall mean the code, documentation or other original works of authorship expressly

identified in Schedule B…”

Currently, my thought is to post in the GIT Commit Message accompanying the contribution, “Per the terms of the CCLA, this is a CCLA Schedule B Submission” or “CCLA Schedule B Submission”.

I would like some feedback regarding using the Schedule B to make contributions.

Thank you in advance for your thoughts.

Best regards,

-T.

---

legal-discuss mailing list legal-discuss@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss