Skip to end of metadata
Go to start of metadata
Icon

The following is a draft of a new CLA/CCLA process based on the new role of Kuali License Steward. There are some proposed changes embedded in this process. These include:

  1. Steward handles agreements and sets up KIS accounts.
  2. Schedule A of the CCLA will be maintained by the Steward and kept up to date.
  3. Schedule A of the CCLA will be reviewed and updated on an annual basis by the submitting organization.

The Kuali Foundation requires that all contributors sign and submit a Contributor License Agreement (CLA). In those cases where a contributor is employed by an organizations such as a company or university, A Corporate Contributor License Agreement (CCLA) may be submitted on behalf of all contributing members of that organization. This page documents the license agreement process.

1. Contributor License Agreement (CLA)

Individual contributors are now required to have a CLA on file before access to the Kuali collaboration resources (Confluence, Subversion, etc.) is granted. The following process is used:

  1. The contributor downloads the Contributor License Agreement, prints it, and signs it.
  2. The contributor scans the signed copy and emails it to help@kuali.org
    1. If no scanner is available, the contributor needs to mail the signed hard copy to the address on the CLA.
    2. Kuali Admin receives the signed hard copy and scans it, if no scan was made.
  3. Kuali Admin sends the scan in an email message to the Kuali License Steward indicating a new CLA has been received.
  4. Kuali License Steward reviews the scanned CLA and approves it. Follow up by email if needed.
  5. Kuali License Steward posts the scanned copy of CLA to Google Docs.
  6. Kuali License Steward creates an account in the Kuali Information System (KIS) for the new user.
  7. Kuali License Steward registers the CLA in KIS.
  8. Kuali License Steward adds the new contributor to the correct group (how is this determined?) and grants access to Confluence, Subversion, etc.
  9. Kuali License Steward notifies the Kuali group project leader and the new contributor that they are now a fully registered Kuali contributor.

2. Corporate Contributor License Agreement (CCLA)

Often, multiple people will contribute to a Kuali project that all work for the same organizations. In such cases, a single Corporate Contributor License Agreement (CCLA) may be submitted on behalf of a named list of contributors in that organizations. Three situations are described below: a new organizations, adding a contributor, updating the list of contributors.

2.1 New Organization

New organizations joining the Kuali Foundation are encouraged to submit a CCLA on behalf of people they employ who will be contributing to one or more Kuali projects. This is not, however, a requirement. Contributors employed by organizations that chose not to submit a CCLA may submit a CLA as described above. The following process is used to submit and process a CCLA:

  1. An authorized representative of the organization downloads the Corporate Contributor License Agreement.
  2. The terms of the CCLA are reviewed by the organization using legal guidance, if necessary.
  3. An authorized representative of the organization signs a printed hard copy of the CCLA.
  4. The authorized representative scans the signed copy and emails it to help@kuali.org
    1. If no scanner is available, the authorized representative mails the signed hard copy to the address on the CCLA.
    2. Kuali Admin receives the signed hard copy and scans it if no scan was made.
  5. Kuali Admin sends the scan in an email message to the Kuali License Steward indicating a new CCLA has been received.
  6. Kuali License Steward reviews the CCLA for errors or problems. Follow up by email if needed.
  7. Kuali License Steward verifies that the organization has completed the joining process (dues paid, etc.) with the Kuali Executive Director.
  8. Kuali License Steward posts the scanned copy of CCLA to Google Docs.
  9. Kuali License Steward processes the list of contributors in Schedule A of the CCLA:
    1. Create an account for the contributor in KIS.
    2. Reference to the CCLA is made in the KIS account entry.
    3. Add the contributor to the correct group and grant access to Confluence, Subversion, etc.
  10. Kuali License Steward notifies the Kuali group project leader and the new organization that they are registered Kuali contributors.

2.2 Adding a Contributor

Two situations arise when adding a new contributor to an existing CCLA. If the request comes from an individual, his employment with the registered organizations is verified by the Kuali License Steward with the authorized representative on record. If the request comes from the representative, it is assumed to be valid.

  1. Kuali License Steward checks to see if the requested new contributor already has an account.
    1. In the case of a change in employment, the contributor is removed from the old CCLA and added to the new one.
  2. Kuali License Steward updates the Schedule A of the CCLA for this organization and does the following:
    1. Create an account for the new contributor in KIS.
    2. Reference to the CCLA is made in the KIS account entry.
    3. Add the new contributor to the correct group and grant access to Confluence, Subversion, etc.
  3. Kuali License Steward notifies the Kuali group project leader and the and the authorized representative of the organization that the new contributor is now registered.

2.3 Updating the List of Contributors

Over time, people come and go from a company or university department. For legal reasons, it is necessary to keep the Schedule A document associated with a CCLA up to date. As such, organizations that use a Kuali CCLA will be asked to review the list of contributors documented in Schedule A and produce a list of new contributors to add and a list of contributors to remove. The CCLA update process is:

  1. Kuali License Steward sends a notice to all active registered organizations with a CCLA asking them to update their list of contributors.
  2. Kuali License Steward receives the update notice by email.
  3. Kuali License Steward adds new contributors using the process described above.
  4. Kuali License Steward removes inactive contributors using the following process:
    1. The inactive contributor is removed from all Kuali access groups.
    2. The inactive contributor is flagged as inactive in KIS (TBD).
    3. Kuali License Steward sends an email to the inactive contributor informing them of their change in status.

       

  5. Kuali License Steward sends a message to the organization to report update changes.
  6. In the event of non-response to the update request, a message is sent to the Kuali Executive Director for further action.

 

Icon

When a CLA and CCLA are REQUIRED for “contributions” to a Kuali product?

A Contributor License Agreement (as the name suggests), is required for any contribution for a Kuali product, if it is not covered by some other agreement.

So, if an OLE user writes about an interesting new extension to OLE on the Kuali Confluence site, this does NOT require a CLA, because submissions to the wiki are covered by a Creative Commons agreement. All code changes, regardless of how they are made (patches, source file changes, etc.) require a CLA and a CCLA from that person's employer.  Ideas suggested in email or list exchanges should be carefully considered, especially if any code or pseudo code is included in the email.  If the suggestion is used, best to get a CLA/CCLA.  

If I am a developer and I am attaching a “patch” that may, or may not be harvested by the product team do I and my institution need a CCLA?

A CLA and CCLA is needed from the original author of the patch.  It is new intellectual property and rights must be transferred via the CLA/CCLA.  This is true even if another developer applies the patch to source code.  It is best to be on the safe side of these matters.  Yeah, it's a bit tiresome, but once the CLA/CCLA is on record, no further work is needed unless the contributor changes employment.

  • No labels