v2
  • LFX Toolkit
  • Release Notes
  • EasyCLA
    • Releases and Known Issues
    • Getting Started
      • Prerequisites
      • EasyCLA Troubleshooting
        • EasyCLA is Disabled
      • EasyCLA FAQs
      • EasyCLA Development Components
    • Project Managers
      • Set up project on EasyCLA
      • Sign in to Project Control Center
      • Create New CLA Group
      • Update Templates
      • Add or Remove a Project from CLA Group
      • View and Manage CLA Group Details
      • Add and Manage GitHub Organizations
      • Add and Manage Gerrit Organizations
      • Add and Manage GitLab Groups
      • View Connection Status of Git Organizations and Repositories
      • Enforce or Remove CLA Mechanism
      • Invalidate a Contributor's Signature
      • Uninstall the EasyCLA Application
    • Contributors
      • Individual Contributor
      • Corporate Contributor
    • Corporate CLA Managers
      • Sign In to the EasyCLA Corporate Console
      • Coordinate Signing CCLA and become initial CLA Manager
      • Add or Delete CLA Managers
      • Approve and Manage Contributors
    • CCLA Signatories
      • Review and Sign a Corporate CLA by Request
    • Glossary
  • Corporate CLA Console
    • Dashboard
    • Projects
      • Sign CLA for a Project
      • Add or Delete a CLA Manager
      • Add and Manage a Contributor
    • Manage Organization
    • Manage your Profile
  • Security Service
    • GitHub Onboarding
    • Manage Vulnerabilities
    • Manage False Positives
      • Regular Expressions Cheat Sheet
    • Manage Non Inclusive Naming
  • Project Control Center (PCC) - Pre Release
    • Overview
    • Adding a Main Project
    • Setup Services for a Project
    • IT Services for a Project
    • EasyCLA Service
    • PCC Dashboard
    • Security Service
    • Cloud Providers
    • Enabling Email Forwarding
    • Setting up a Domain for a Project
    • Source Control
    • Issue Tracking for a Project
    • Mailing List
    • Setting up Wiki
    • Meetings
  • Organization Dashboard - Pre Release
    • Overview
    • Global Statistics
    • Projects
    • My Organization
    • Organization Profile
    • Managing Teams
    • Global Events
    • Global Training and Certifications
    • Resources
    • Membership Details of a Project
    • Benefits
    • Committees
    • Project Contributors
    • Meetings
    • Project Contributions
    • Member Promotions
    • Dashboard
    • Membership Summary
    • Training and Certifications
    • Events Insights
    • Global Attendee Insights
Powered by GitBook
On this page
  • GitHub
  • Gerrit
  • GitLab
  • If your Company is not in the list
  • If your Company has not yet signed a CCLA
  • Yes (If you will become the initial CLA Manager)
  • No (If someone else will become the initial CLA Manager)
  • If you have not yet been added to the approved list
  • Acknowledge Company Contribution
  • For GitHub and GitLab:
  • For Gerrit:
  • If you are additionally asked to sign an ICLA
  1. EasyCLA
  2. Contributors

Corporate Contributor

PreviousIndividual ContributorNextCorporate CLA Managers

Last updated 3 years ago

A corporate contributor is one who contributes code on behalf of their employer (and not on their own behalf). If you are contributing code on your own behalf, please see the workflow.

Upon creating a pull request in GitHub or merge request in GitLab or submitting changed code in Gerrit, EasyCLA will check whether the contributor is authorized under a signed CLA for that project. If they are not, and if they are contributing on behalf of their employer, then they will need to be authorized under a signed Corporate CLA (CCLA):

  • If their company has not yet signed a CCLA, then the contributor can start the workflow for the signing process.

  • If the contributor has not yet been added to the authorized contributors list by their company's CLA Manager, then the contributor can submit a request to their CLA Manager to be added.

  • If the CCLA has been signed and the contributor is on the authorized contributors list, then the contributor will need to confirm their association with the company, and then will be able to proceed.

GitHub

  1. In GitHub, go to the repository that is linked to your project.

  2. Make a code change and create a pull request.

  3. EasyCLA checks the CLA status of all committers involved in that pull request.

  1. EasyCLA displays a cross or a check mark beside the name of each contributor involved in that pull request based on their CLA status.

  2. A cross next to a contributor's name means the EasyCLA check has failed, because the contributor is not authorized under a signed CLA.

5. Click Authorize LF-Engineering. (Subsequent contributions will not require authorization.)

Result: The CLA Contributor Console appears in a new tab.

6. Click Proceed as a Corporate Contributor.

7. On Select Organization window, type your company's name in the field, select it from the drop-down list, and click Proceed.

Note:

8. You will need to complete one of the following workflows:

Gerrit

  1. In Gerrit, clone a repository under the Gerrit instance into your local machine.

  2. Make a change and push the code to your Gerrit repository.

  3. A warning link that you need to sign a CLA appears if CLA is not signed for the project:

6. Navigate to Settings -— the gear icon on the upper right corner -- and click Agreements from the menu on the left:

7. Click New Contributor Agreement.

8. Click Corporate CLA, and then click the Please review the agreement link.

9. Click Proceed To Corporate Authorization.

Result: You are redirected to the EasyCLA Corporate Console. Sign in with your LF SSO account if prompted.

10. On Select Organization window, type your company's name in the field, select it from the drop-down list, and click Proceed.

11. You will need to complete one of the following workflows:

GitLab

  1. In GitLab, clone the repository you want to contribute to.

  2. Make changes, commit change and create merge request.

  3. EasyCLA checks the CLA status of all committers involved in that pull request.

  1. EasyCLA displays a cross or a check mark beside the name of each contributor involved in that pull request based on their CLA status.

  2. A cross next to a contributor's name means the EasyCLA check has failed, because the contributor is not authorized under a signed CLA.

5. Click Authorize (Subsequent contributions will not require authorization.).

Result: The CLA Contributor Console appears in a new tab. ​

6. Click Proceed as a Corporate Contributor.

7. On the Select Organization window, type your company's name in the field, select it from the drop-down list, and click Proceed.

Note:

8. You will need to complete one of the following workflows:

If your Company is not in the list

  1. Click +Click Here next to the Organization not listed?

2. Provide organization website URL, and organization name in the respective fields. Note: If the website URL is already associated with an organization, the organization name appears in the Organization Name field, and you cannot edit the name.

3. Click Next.

4. Click an answer: Are you authorized to be a CLA Manager for your organization?

  • No: Provide name and email address of the person who is authorized to be the CLA Manager from your company for this project, and click Submit Request. If you do not know who should be the CLA Manager from your company for this project, you should consult with your management or legal department to confirm.

If your Company has not yet signed a CCLA

If your company has not yet signed a CLA, the No Signed CLA Found window appears after selecting your company.

  1. Click an answer: Are you authorized to be a CLA Manager for your organization?

Yes (If you will become the initial CLA Manager)

  1. Click Proceed on the window that appears.

Note: If you don't have a username (LF SSO Account) associated with The Linux Foundation, you will be redirected to the LF SSO Account creation page.

2. Click Proceed again.

No (If someone else will become the initial CLA Manager)

  1. Complete the form, and click Submit Request. If you don't know the email address of the person who should become the CLA Manager of your company, then (unless you just created the company record) you can click the Contact Company Admin link, which may let you reach out to your company's LFX administrative contact if your company has set someone up with this role.

  2. Click Exit EasyCLA. You can contribute after your company signs the project's CCLA, and the CLA Manager adds you to the approved list.

If you have not yet been added to the approved list

If your company has signed a CCLA, but you have not yet been added to the approved list, the Request Authorization to Contribute window appears that shows the CLA Manager(s) for your company.

  1. Select one or more CLA Managers from the drop-down list whom you want to request to add you to the authorized list.

3. Click Exit EasyCLA.

Acknowledge Company Contribution

After the CCLA is signed and the CLA Manager adds you to the approved list, you must re-select your company association before you can contribute code under that company's signed CCLA.

For GitHub and GitLab:

  1. Navigate to the GitHub PR page or GitLab merge request page.

  2. Click Not Covered, and then click Proceed as a Corporate Contributor.

  3. On the Select Organization window, select your company, and click Proceed.

For Gerrit:

A window appears confirming your association with the company. Click Exit EasyCLA, and start contributing.

Important: If the status on Git command line still shows "No contributor agreement" when you push the code change, you need to navigate to the Gerrit window, sign out, sign in again, and then push the code.

If you are additionally asked to sign an ICLA

For certain projects, in addition to being authorized under your company's signed CCLA, you may also be required to individually sign an ICLA on your own behalf.

  1. Click Proceed.

  2. Follow the instructions in DocuSign, sign the ICLA, and click FINISH.

  • GitHub/GitLab Contributors: Navigate to the GitHub/GitLab page. Wait a few seconds for the CLA status to be updated or refresh the page.

  • Gerrit Contributors: If the status on Git command line still shows "No contributor agreement" when you push the code change, you need to navigate to the Gerrit window, sign out, sign in again, and then push the code.

4. Click or Please click here to be authorized.

​ ​

If your company is not in the list, you can add the company as described in .

4. Navigate to the Gerrit instance of your project. For example, if you are contributing to the ONAP project, navigate to

5. Sign in using your LF account.

​​ ​​

4. Click or Not Covered.

If your company is not in the list, you can add the company as described in .

Yes: Follow the procedure, and click Proceed to .

Note: After the authorized person signs CLA, and adds you to the approved list, you must before you can contribute.

— By clicking Yes, you will become the initial CLA Manager after the CCLA is signed.

— By clicking No, you will enter the details of someone else who will become the initial CLA Manager.

3. You will be redirected to the corporate console to .

Important: After the CCLA is signed, you will be the initial CLA Manager, but by default you will not also be an authorized contributor. In order to contribute to the project, you must then , and .

An Identify CLA Manager window appears.

Important: You will receive an email after the CLA Manager adds you to the approved list. After you are added to the approved list, you must before you can contribute to the project.

2. Click Request Authorization.

Important: You will receive an email after the CLA Manager adds you to the approved list. After you are added to the approved list, you must before you can contribute to the project.

A window appears confirming your association with the company. Click Exit EasyCLA, and you will be redirected back to the GitHub or GitLab page where the CLA status will be updated. If it does not immediately update, please wait a moment and then refresh the page.

Navigate to the Gerrit instance of your project, and re-complete the procedure by following to complete company acknowledgement.

If this is the case for your project, then after your CLA Manager adds you to the approved list, and after you , then the following screen appears:

On CLA Ready For Signature window, click SIGN CLA.

https://gerrit.onap.org
Single Sign-On (SSO)
coordinate the CCLA signing process
coordinate the CCLA signing process
If your company is not in the list
If your company is not in the company list
If your company has not yet signed a CCLA
If you have not yet been added to your company's approved list
Acknowledge company contribution after you are added to the approved list
If you are additionally asked to sign an ICLA
If your company is not in the company list
If your company has not yet signed a CCLA
If you have not yet been added to your company's approved list
Acknowledge company contribution after you are added to the approved list
If you are additionally asked to sign an ICLA
If your company is not in the list
If your company is not in the company list
If your company has not yet signed a CCLA
If you have not yet been added to your company's approved list
Acknowledge company contribution after you are added to the approved list
If you are additionally asked to sign an ICLA
complete your company acknowledgement
Yes
No
complete your company acknowledgement
complete your company acknowledgement
step 4 through step 10 as described above for Gerrit
Individual Contributor
GitHub
Gerrit
GitLab
complete the company acknowledgement
complete your company acknowledgement
add yourself to the approved list
CLA Check Fail
CLA CCLA Flow
Select Organization
CLA Gerrit Sign a CLA
Agreement Link
CLA Not Covered
CLA CCLA Flow
Select Organization
company not listed
Create New Organization
company has not signed cla
Proceed to Sign with SSO Account
Redirecting to CLA Manager Console
Request Authorization
Settings Icon
Gerrit Agreements