Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This is the deprecated version of LFX EasyCLA application. For the new LFX EasyCLA workflow, refer to V2 (Current).
LFX EasyCLA helps streamline the contribution process for open source projects that use Contributor License Agreements (CLAs), by streamlining workflows for project maintainers, contributors, and organizations whose employees are contributing to the project. EasyCLA coordinates the process of getting CLAs signed and, for companies and other organizations, the process of authorizing employees to contribute under a signed CLA. By automating many of the manual processes, this open source solution hosted by The Linux Foundation reduces delays for developers to get authorized under a CLA.
Some projects use a Contributor License Agreement (CLA) to define the terms under which content (such as source code or documentation) is contributed to the project.
Not all projects use CLAs; many use alternative contribution mechanisms, such as the Developer Certificate of Origin sign-off process. For those that do use CLAs, LFX EasyCLA helps to ensure that contributions are not merged into a project unless the contributors are covered under a signed CLA.
There are two types of CLAs:
Corporate Contributor License Agreement
If the company (employer) owns the contribution, a CCLA signatory signs a Corporate CLA. The Corporate CLA legally binds the corporation, so the agreement must be signed by a person with authority to enter into legal contracts on behalf of the corporation. A project may require that every employee (developer) should sign their own individual CLA (which separately covers contributions owned by the individual contributor) besides being covered by corporate CLA.
Individual Contributor License Agreement
If as an individual you own the contribution, you sign the Individual CLA. A signed Individual CLA may be required before an individual's contribution can be merged into the project repository.
The following high-level diagram shows the different flows and roles that EasyCLA supports.
How you interact with EasyCLA depends on your role. EasyCLA supports the following roles in its workflow:
You are a project manager if you are the project maintainer who has responsibilities such as managing a project’s GitHub organization or Gerrit instance, members, repositories, and CLAs. You have access to specific projects within the EasyCLA project console, also referred as Project Control Center.
With EasyCLA, you do the following CLA set-up tasks:
Add GitHub repositories or Gerrit instances to enforce CLA monitoring.
At any time, you can change the settings to manage your project CLA monitoring, and do other management tasks:
You are a contributor (developer) if you contribute code to GitHub or Gerrit projects. With EasyCLA, you will follow different workflows depending on whether the project is hosted on GitHub or Gerrit, and whether you contribute on behalf of a company or yourself as an individual:
Individual Contributor (GitHub): Sign a CLA as an Individual Contributor and contribute to GitHub project.
Individual Contributor (Gerrit): Contribute to Gerrit project
Corporate Contributor (GitHub): Contribute to GitHub project
Corporate Contributor (Gerrit): Contribute to Gerrit Project
You are a Corporate CLA manager (CCLA manager) if you are the person authorized to manage the list of approved contributors under your company’s Corporate CLA. There can be one or more CLA managers for a company. With this responsibility, you use EasyCLA to:
You are a Corporate CLA signatory (CCLA signatory) if you are authorized to sign contracts, such as the project’s CLA, on behalf of the company. With EasyCLA, you can:
Troubleshooting helps you solve problematic symptoms in your CLA implementation.
If you are having issues with EasyCLA, go to https://support.linuxfoundation.org, click Get Help with CLA, and file a ticket.
​EasyCLA is Disabled​
Prerequisites:
Ensure that your project meets the EasyCLA Requirements.
Ensure that you have an LF Single Sign-on (SSO) account, create an account if you do not have an SSO account.
To get access to EasyCLA:
Share your username with the EasyCLA administration team at docucla@linuxfoundation.org.
Provide sample ICLA and CCLA template documents to the EasyCLA administration team at docucla@linuxfoundation.org.
After the EasyCLA administration team confirms your setup, you can Sign In to the EasyCLA Management Console to do the EasyCLA activities as a project manager.
Note: CLA managers can immediately start using the EasyCLA Corporate Console because it does not require activation from the EasyCLA administration team. Simply Sign In to the EasyCLA Corporate Console to do the EasyCLA activities for CLA Managers.
To Sign out of EasyCLA:
THE LINUX FOUNDATION pane appears.
Click Sign Out.
You are signed out and the sign-in page appears.
Go to a page that shows the hamburger icon on the top-left corner such as on the main CLA Management Console or CLA Corporate Console page.
Click the hamburger icon .
EasyCLA has the following requirements:
Your project repositories are in GitHub or Gerrit
If your project uses Gerrit source control, the Gerrit instance should be hosted on The Linux Foundation platform.
You have an LF Single Sign-On (SSO) account. If you do not have an SSO account, create an account.
For Corporate CLAs, your company has a corporate authority role
As a repository administrator, enable Branch Restrictions and Branch Protection for your organizations in GitHub. Set the restrictions and protection to enable required status checks on a branch regardless of the role for the organization.
The CLA Management Console data may not load due to a bug in the Auth0 implementation. This is a sample sentence.
Solution:
On a Chrome window, open developer panel by typing command + option + i. for mac, and ctrl + shift + i for windows.
Select the Application tab.
Click Clear storage under Application in the left pane.
Select Clear site data from the bottom of the developer console.
Sign out of the CLA Management Console.
Sign back in.
If the issue persists, try using an incognito browser window.
EasyCLA is disabled hence the GitHub organization(s) that I want EasyCLA to monitor are not monitored.
Solution:
GitHub is set up to permit administrators and organization owners to have maximum flexibility, which includes disabling installed applications, such as EasyCLA. To avoid this, you must enable branch protection by selecting the Enable Branch Protection check box after the GitHub organization is added to a project or add the branch protection rule manually, as described below:
Do these steps:
1. As the GitHub organization owner or administrator, go to the GitHub repository that you want EasyCLA to monitor.
2. Click Settings from the top menu.
3. Settings appear with Options in the left pane.
4. Click Branches under Options.
Result: Branch settings appears.
5. Select master for the Default branch. Click Edit or Add rule for Branch protection rules of your organization.
Result: Branch protection rule settings appears
6. Select the following check boxes in Rule settings and click Create.
Require status checks to pass before merging
Require branches to be up to date before merging
Include administrators
The EasyCLA Application installation process connects GitHub to the CLA Management Console. After you complete installation, you must configure the repositories to enforce CLA monitoring.
To Install the EasyCLA Application:
1. Sign in to the CLA management console.
2. Click a project of interest.
3. Click CONNECT GITHUB ORGANIZATION. The Add GitHub Organization dialog appears and lets you specify the GitHub organization.
Connecting your GitHub organization will let you enable EasyCLA checks on that organization. If you already have a CLA process in place, go to the Linux Foundation Support Center, fill the form, and click Create to file a ticket to describe your particular needs, and import your existing CLAs.
4. Enter your organization name in the GitHub Organization URL field. The URL automatically appends the name. Click CONNECT.
Result: The Connect LF CLA App to GitHub Organization dialog appears.
The GitHub organization name value is case-sensitive—make sure that the name you enter matches the case of your GitHub organization name exactly.
5. Read the instructions and click INSTALL THE GITHUB CLA APP. ​The EasyCLA Application opens in GitHub
6. Click Install on the EasyCLA Application.
7. Select one or more repositories and assign permissions. Click Install.
The CLA Management Console appears and the GitHub Organizations pane shows the organizations and the repositories that the EasyCLA Application is authorized to monitor.
To delete an organization from monitoring, click DELETE next to the organization that you want to delete. A confirmation dialog appears. Click DELETE. You must also Uninstall LF CLA Application for Your Organization that you installed in Step 5.
A message informs you that your project needs a CLA group. A CLA group defines one or more CLA types that contributors must sign.
If the EasyCLA Application is not connected to GitHub properly, an error message appears under the organization name: Not Configured. Please connect the CLA App to the Github Org. Click the message link to return to Step 4.
8. Repeat Steps 2 through 7 to connect as many organizations as you want.
Important: To enable a CLA check on a repository, you must configure a GitHub repository or add a Gerrit instance. Simply adding an organization to the project does not enable the CLA check for any CLA groups.
When corporate contributors are added to the approved list or they complete CLA signing process, the CLA status still remains Not Covered for GitHub, and shows No Contributor Agreement for Gerrit while submitting change.
After you are added to approved list, you must acknowledge company contribution or sign ICLA if your CLA requires you to sign individual CLA for getting full authorization to contribute.
Navigate to Gerrit window, sign out and sign in again, and then submit a change.
As a project manager, you have responsibilities to manage a project’s GitHub organization or Gerrit instance, members, repositories, and legal aspects like the CLA. You use the CLA Management Console to set up CLA.
To Set Up CLA:
​Add a CLA Group.
At any time, you can change the settings to manage your project's CLA monitoring, and do other management tasks:
​Manage CLA Group Details​
Who do I contact to enable my Linux Foundation-hosted project to use EasyCLA?
Submit the form describing your requirements, and import your existing CLAs.
Why does The Linux Foundation ask contributors of some projects to sign CLAs?
Some project communities have elected to use CLAs as a required step for code contributions. The Linux Foundation wants to ensure that contributions comply with the IP (Intellectual Property) policies of that project.
What is the difference between Corporate CLA and Individual CLA?
A Corporate CLA needs to be in place if you are contributing code on behalf of your employer. A Corporate CLA should be signed by an individual who is authorized to enter into legal agreement on behalf of the company. After the Corporate CLA is signed, your email address needs to be included in an approved list for the project. A CCLA manager for your company is responsible for managing the approved list.
An Individual CLA is signed by an individual for contributions that they contribute on their own behalf, as opposed to contributions on behalf of their employer or another entity.
Which Corporate CLA approved-list option has the lowest maintenance overhead?
Using the Domain Approval Criteria requires less overhead because CCLA signatories and CCLA managers do not need to add and manage numerous employee email addresses.
I contribute to an open source project as an employee for a company. Do I need to complete, sign, and submit a DocuSign document?
Probably not. If your company's CCLA signatory has signed a Corporate CLA, and if you are included in the approved list under that company's CLA, then you simply confirm your association to the company during your code submission process.
However, if you are the first one from your company to contribute to a project, then your company's CCLA signatory will need to sign a Corporate CLA as part of the EasyCLA setup process. Depending on the company, you might be an authorized CCLA signatory (please check with legal counsel of your company to be sure).
Otherwise, if your company has already signed a Corporate CLA, but you are not yet on your company's approved list, then you must be included in the approved list by your company's CCLA manager as part of the EasyCLA process.
What should I do if my company is not listed while signing CLA?
You must create a company as described here.
If my project community has elected to use CLAs as a required step for contributions to their code, do I need to be authorized under a CLA for each project to which I contribute?
Yes, provided that the project has a CLA.
If you are contributing as an individual—you must sign an Individual CLA for each project to which you contribute.
If you are contributing as an employee of a company, your company's CCLA signatory must sign a Corporate CLA.
Do I have to sign a CLA every time I contribute code?
Signing a CLA for a project covers all code contributions to that project. You may, however, need to sign additional CLAs if you choose to contribute to other projects that require CLAs.
What is the acceptable email format?
A valid email address with an email prefix and an email domain, for example abc@mail.com
The allowed characters for email prefix are letters (a-z), numbers, underscores, periods, and dashes, and an underscore, period, or dash must be followed by one or more letter or number, for example: abc-d@mail.com/abc.def@mail.com/abc@mail.com/abc_def@mail.com
The allowed characters for email domain are letters, numbers, dashes, and the last portion of the domain must be at least two characters, for example: .com, .org, .cc
Project managers sign in to the EasyCLA Management Console to perform the CLA set-up and management tasks.
2. On Projects card, click Proceed.
3. Enter your credentials as the project manager, and click SIGN IN.
Result: The CLA Management Console appears and lists your assigned projects from the Linux Foundation, for example:
4. Click a project name of interest.
For each project, the CLA Management Console provides the following information:
GitHub Organizations shows the organizations to which you have connected to the CLA Management Console. Organizations are shared accounts where companies and open source projects can collaborate across many projects at once.
CLA Groups shows the CLA groups that you have added to the project. A CLA group defines one or more CLA types that contributors must sign.
GitHub Repositories shows the repositories that you have configured to require CLA monitoring for pull requests.
Gerrit Instances shows the Gerrit instances that you have added to require CLA monitoring for pushes.
1. Go to
The CLA Management Console lets you select a template style to use for your Corporate CLA and Individual CLA.
In some circumstances, you need to change the legal text of the CLA agreement in major and minor revisions:
A major revision (for example, a change to your charter) is one in which you are legally required to have all contributors re-sign the revised agreement.
A minor revision is one that does not change a legal perspective and contributors do not need to re-sign the revised agreement.
In these cases, you simply add the updated CLA using the same procedure as for adding the initial CLA.
Verify that the pop-up blocker is disabled on your browser before you begin this procedure.
To Add CLA:
1. Sign in to the CLA management console.
2. Click a project of interest.
3. Go to the CLA group to which you want to add a CLA and click SELECT TEMPLATE. The Select a template page appears and lists available templates.
4. Click the button on the template you want to use.
A template information form appears. The information you enter in this form will populate the corresponding fields in the resulting Corporate CLA and Individual CLA PDFs. The following form is an example; each form is specific to the project.
5. Complete the form fields and click GENERATE AND REVIEW PDFS. The CLA appears.
6. Click VIEW CCLA (Corporate CLA) or VIEW ICLA (Individual CLA) to view the respective PDF and scroll through the content to review it.
7. Click DONE. (BACK TO TEMPLATE INFORMATION returns you to the template form.)
The Projects page shows that you have successfully uploaded the Corporate CLA and Individual CLA templates under your CLA Group. Refresh the page if the templates do not appear.
(Optional) View Current and Previous CLA PDFs
As a project manager, you can add GitHub repositories to CLA monitoring or remove them from CLA monitoring.
To add or remove Github Repo:
1. Sign in to the CLA management console.
2.Click a project of interest.
3. In the GitHub Repositories pane, click CONFIGURE GITHUB REPOSITORIES.
The Configure GitHub Repositories dialog appears and lists the GitHub repositories that are available for your organization.
4. For the repository that you want to configure, click an option:
ADD adds the repository to the CLA group and to CLA monitoring. After you add a repository, the REMOVE option becomes available next to the repository.
REMOVE disables CLA enforcement on the repository. After you remove a repository, the ADD option appears next to the repository.
REMOVE removes the repository from the CLA group and CLA monitoring. After you remove a repository, the ADD option appears next to the repository.
DISABLED indicates that the repository has been configured for another CLA group and thus cannot be configured for the selected CLA group.
ADD ALL REPOS adds all repositories for the corresponding GitHub Organization to CLA enforcement. After you add the repositories the REMOVE option appears next to each repository.
5. Click CLOSE.
The CLA Management Console appears. Repositories shows a checkmark next to each repository that EasyCLA will monitor for the organization and the CLA group.
As a project manager, you use the CLA Management Console to:
Add one or more Gerrit instances to CLA monitoring
Integrate the Gerrit repositories so you can monitor all the code submissions that contributors make
Delete Gerrit instances from CLA monitoring as required
If you already added a Gerrit instance during the CLA onboarding process, skip this procedure unless you want to add more Gerrit instances.
To add or remove Gerrit Instances:
1. Sign in to the CLA management console.
2. Click a project of interest
3. Click ADD GERRIT INSTANCE ****The Add Gerritt Instance form appears.
4. Complete the form fields, and click SUBMIT. Gerrit Instance Name - Name of the Gerrit Instance Gerrit Instance URL - URL of the Gerrit Instance ICLA Group ID - An existing LDAP Group ID for Individual CLAs CCLA Group ID - An existing LDAP Group ID for Corporate CLAs
Notes:
Contact the Linux Foundation IT if you do not know the LDAP Group IDs.
One or both LDAP groups must exist for you to be able to create a Gerrit instance. If a group does not exist, an error message appears and you are prevented from creating a Gerrit instance.
The CLA Management Console lists the instance under Gerrit Instances.​​
The CLA Management Console presents a CLA block of code:
[contributor-agreement "{ICLA-Name} “]
description = ICLA for Linux Foundation
agreementUrl = {URL }
accepted = group {Group-Name}
[contributor-agreement "{CCLA-Name} “]
description = CCLA for Linux Foundation
agreementUrl = {URL }
accepted = group {Group-Name}
5. Copy the block. As the Gerrit instance administrator, you will modify CLA configurations for the following files under the Gerrit instance’s All-Projects repository. If you are not the administrator, contact the Gerrit instance administrator to include the following files under the Gerrit instance’s All-Projects repository. Projects are organized hierarchically as a tree with the All-Projects project as root from which all projects inherit.
You can get and set the configuration variables by using the git config command with the -l option (this option provides the current configuration), or if you are using the Gerrit web interface, go to Projects and click List. Select your project and click Edit Config.
project.config - Add the contributor license agreement block to this project configuration file. This is the project configuration file across all repositories of the Gerrit instance. At the end of the file, replace the variables with your project CLA values and then save the file:
[contributor-agreement "{CLA-Name} “]
description = CLA for Linux Foundation
agreementUrl = {URL }
accepted = group {Group-Name}
CLA-Name can be a name of your choosing. The name must include the double quotes.
URL** ** refers to the URL to the CLA Contributor Console.
Group-Name should be an existing Group Name, under the Group section of the Gerrit instance. This name refers to the LDAP Group that the user will be added to.
groups - If the Group-Name value that you specified in the project.config file does not exist in this file, add it to this file, and then save the file.
Provide these files and Gerrit configuration to the Linux Foundation Release Engineering team to finish configuration. The CLA Management Console shows the repositories that the CLA application will monitor.
6. To delete an instance from monitoring, click DELETE next to the instance that you want to delete. A confirmation dialog appears. Click DELETE.
The CLA Management Console lets you select and view the current CLA PDF and previous CLA PDFs for your project.
To view CLA PDFs:
1. Sign in to the CLA management console
2. Click a project of interest.
3. Go to the CLA group that has the CLA PDF that you want to view.
5. Click the PDF icon next to the version that you want to view.
6. Click View PDF.
The PDF opens in a new window.
4. Click the PDF icon . The CLA PDF dialog appears and shows the current CLA PDF and previous CLA PDFs.
As a project manager, you use the CLA Management Console to manage your CLA group details, and view user signatures and companies.
To manage CLA groups:
Sign in to the CLA management console
Click a project of interest.
Do any of the following actions:
You can change your CLA type selections if needed.
The CLA Group dialog appears and shows your current CLA type selections.
2. Change the CLA Group Name, selections, or all, and click SAVE.
You can view the full set of signatures and list of approved contributors who are interacting with a project. A signature list shows details about who signed a CLA for your project.
1. Click VIEW SIGNATURES.
Details for all user signatures appear:
Type shows Company, Individual, or Employee depending on the CLA type that the user signed.
Name identifies the individual or employee who signed the CLA.
Company identifies the company that is associated with a Corporate CLA.
GitHub ID shows the GitHub identity of the individual or employee.
LFID shows the Linux Foundation identity of the individual or employee.
Version identifies the version of the CLA.
Date Signed shows the date that the individual, employee, or CLA signatory signed the CLA.
2. (Optional) Click a column header to sort the column values in ascending or descending order. Use the pagination options to go to subsequent or previous pages.
3. Click CLOSE.
The Corporate CLA list lets you see what companies in your project have a signed Corporate CLA.
1. Click VIEW COMPANIES on a Corporate CLA.
All companies that have signed the Corporate CLA are listed.
2. Click CLOSE.
As a project manager, you can uninstall the EasyCLA Application for a GitHub organization. When you uninstall the app, it is removed from all your repositories. CLA monitoring is no longer in effect.
To Uninstall:
1. Sign in to GitHub, and navigate to the organization for which you want to uninstall the EasyCLA application.
2. Under Settings tab, select Installed GitHub Apps from the left side navigation pane.
3. Click Configure for the Linux Foundation: EasyCLA app.
4. Navigate to Danger zone > Uninstall Linux Foundation: EasyCLA section, and click Uninstall.
5. Refresh the CLA Management Console.
The EasyCLA Application is uninstalled.
1. Click the gear icon next to the CLA group name.
As a CLA manager, you do the following CLA tasks after you sign in to the CLA Corporate Console:
Approve Contributors—each approved list applies to the project for which the company has signed a Corporate CLA.
As a CLA manager, sign in to the EasyCLA Corporate Console to add your company to a project and do management tasks.
Enter your credentials as the CLA manager and click SIGN IN.
The CLA Corporate Console appears and shows Companies.
On Organizations card, click Proceed.
Note: If you are also the project manager, make sure that you are logged out of the CLA Management Console before you begin using the CLA Corporate Console.
To Add a Company:
​Sign in to the CLA corporate console.
Sign out or continue to Sign a Corporate CLA for Company.
Click GET STARTED.
Type a company's name in the dialog fields and click ADD COMPANY. **** ​​
As a CCLA signatory, you may receive email requests to review and sign a Corporate CLA.
To sign a CCLA:
Look in your email inbox for a CLA Sign Request email and open the email.
Click REVIEW DOCUMENT in the email.
The Corporate CLA dialog opens.
Click OPEN CLA and then follow the instructions that DocuSign presents. Some fields are pre-populated such as the company name and email.
After the Corporate CLA is signed, the Company page shows the signed Corporate CLA under Signed Project CCLAs. You receive a CLA Signed Document email with an attached document PDF. Contributors to the company project simply need to confirm their association to the company, and then they can continue with their pull requests. Their subsequent contributions will not require association confirmations.
A Corporate CLA that is signed by the CCLA signatory remains in effect even when that CCLA signatory is no longer employed at a company.
​​
You must be authorized by your company to sign a Corporate CLA. If you are a CLA manager but not a CLA signatory, you can request that the CCLA signatory sign the Corporate CLA.
1. Sign in to the corporate console.
2. Under Companies you are associated with in Easy CLA, click the company for which you want to sign a Corporate CLA.
3. Click SIGN NEW CLA.
4. The Select a Project to Sign a CCLA dialog appears and lists CLA groups.
5. Select the CLA group of interest. A CLA Signing Requirement dialog appears:
6. Click YES or NO according to your permissions:
The Corporate CLA dialog opens.
Click OPEN CLA.
Follow the instructions that DocuSign presents, sign it, and click FINISH. Some fields are pre-populated such as the company name and email.
You receive an email from The Linux Foundation, informing you that you have signed the CLA.
The Send E-Mail To CLA Signatory form opens. The Signatory Name and Signatory E-Mail fields may be pre-populated; if not complete the fields. Click SEND.
​The CLA signatory receives a CLA Sign Request email, reviews and signs the document.
After the Corporate CLA is signed, the Company page shows the signed Corporate CLA under Signed Project CCLAs. You receive a CLA Signed Document email with an attached document PDF. Contributors to the company project simply need to confirm their association to the company, and then they can continue with their pull requests. Their subsequent contributions will not require association confirmations.
A Corporate CLA that is signed by the CLA signatory remains in effect even when that CLA signatory is no longer employed at a company.
After you sign in to EasyCLA consoles, navigate to Get Help and select an option from the drop-down list.
Docs opens the Linux Foundation Product Documentation. Support opens the Help Center.
You will receive an email when a contributor sends a request to be added to the Approved list. To approve them, you must add their email address or GitHub username to the Approved list.
You can approve contributors by adding them to the Approved List. Approved Lists are lists of domain names, email addresses of individuals, GitHub usernames, or GitHub organization names who are authorized to contribute under a signed Corporate CLA. As a CCLA manager, you allow contributions to projects on behalf of your company by using any approved list:
Domain Approved List allows entities to contribute under any email address under that domain name.
Email Approved List allows entities to contribute under an individual email address.
GitHub Approved List allows entities to contribute under a GitHub username.
GitHub Organization Approved List allows entities to contribute under a GitHub organization name.
Each approved list applies to the project for which the company has signed a Corporate CLA. The CLA application checks all the approved lists for allowing contributions to a company project. A contributor only needs to be on one approved list. Contributors can use EasyCLA to send email requests to be associated (authorized) with the company.
To Approve Contributors:
2. The CLA Corporate Console appears and shows Companies.
3. Click a company of interest.
4. The CLA Corporate Console appears and shows projects with signed CLAs.
5. Click MANAGE APPROVED LIST for a **** CLA **** under which you want to add a contributor. You can identify a recent request for a CLA by seeing the value as 1 under Pending Contributor Requests column. Following is an example:
6. Under Pending Contributor Requests, click ACCEPT, and then click APPROVE REQUEST on the confirmation window to add the contributor to the approved list or click DECLINE to decline the contributor's request to be added. The contributor receives an e-mail notification about the status.
Result: If you click ACCEPT, the contributor will be added to the list, and is removed from the Pending Contributor Requests section.
7. (Optional) You can edit a contributor's approved list details by:
The corresponding Edit domain/email/github approved list dialog lets you add, edit, and delete values to the approved list so that employees (developers) can be associated to the company. An example domain name value is joesbikes.com. A wildcard approves/authorizes the domain and all subdomains, for example: *.joesbikes.com or *joesbikes.com would authorize joes.bikes.com, shop.joesbikes.com, and blog.joesbikes.com.
Note: To remove an entry from the approved list, click X next to the item, and click SAVE.
Click the edit icon( pencil ) next to the approved list that you want to edit:
Click ADD DOMAIN/EMAIL/GITHUB, enter a domain name, email address, or GitHub username for the employees for who you want to authorize, and click SAVE APPROVED LIST. For example:
Your entries appear in their corresponding approved lists.
The GitHub Organization Approved List lets you add or remove organizations from an approved list so that company employees can contribute to project—the CLA service checks the GitHub organizations that the user belongs to.
Requirements:
Each member of your organization must ensure that these items are Public in their GitHub Profile:
The associated email address for the organization member. Each Private member should make their associated email address Public (members can have multiple emails in their Profile, so they must select the appropriate one).
To Add or Remove an Organization from Approved List:
1. Click the edit icon (pencil) next to Github Org Approved List. The Edit Github Organization Approved List dialog appears.
Note: Click CONNECT GITHUB if the organization you want to authorize is not listed in the dialog. The Add GitHub Organization dialog appears and lets you specify the GitHub organization.
2. To Add, type a GitHub organization name in the field, select from drop-down, and click SAVE APPROVED LIST.
Your organizations appear in their organization approved list.
CCLA managers have the following responsibilities:
Add a company to a project.
Authorize domain names and email addresses.
Change the settings to manage your company CLAs.
To Add or Delete CLA Managers:
Click a company of interest.
The CLA Corporate Console shows Signed CLAs.
Click a CLA.
Project Signatures lists the CCLA Managers and Employee Acknowledgements for the project.
Do an action:
Click the plus sign (+) in the CLA Managers pane.
The Add CLA Manager dialog appears.
Enter the Linux Foundation identification of the CCLA manager who you want to add and click SAVE.
The CCLA manager is listed under CLA Managers.
Click Delete next to a CCLA manager to remove that person as a CCLA signatory.
Click DELETE on the Delete Manager confirmation dialog.
The CCLA manager is removed from under CLA Managers.
You can download the PDF document by clicking the link form the email. You will be re-directed to Linux Foundation's website. If the download doesn't start automatically, click Proceed to Download.
1. ​ to the corporate console.
Their membership with the organization. Each Private member should follow this to make their membership Public.
3. To remove, click next to the organization that you want to add/remove, respectively.
​ to the corporate console.
​​
​​
​​
CLA managers can view a list of employee acknowledgements.
To View Employee Acknowledgements:
​Sign in to the corporate console.
Click a company of interest.
The CLA Corporate Console shows Signed CLAs.
Click a CLA.
Project Signatures lists the CLA Managers and the signed Employee Acknowledgements for the project. Each acknowledgement shows the employee name, the agreement name, and the date the employee acknowledged the agreement.
To Edit Company details:
To see all companies in your organization which are associated to the Linux Foundation, click the hamburger icon next to CLA Corporate Console.
Click a company of interest.
The CLA Corporate Console appears, and shows your company and all its signed project CLAs.
Click the pencil icon next to the company name.
The Edit Company dialog appears.
Edit any of the details you want to change and then click SAVE:
Company Name
Your email
Your name
The Company page reflects your changes.
​​
​ to the .
​​
Approved Lists are lists of domain names, email addresses of individuals, GitHub usernames, or GitHub organization names who are authorized to contribute under a signed Corporate CLA. CLA managers create and manage the approved list.
A Contributor License Agreement (CLA) defines the terms under which intellectual property is contributed to a company or project. Typically, the intellectual property is software under an open source license. It is a legal contract signed by contributors before they can contribute code to a project.
Corporate Contributor License Agreement (CCLA) defines terms and conditions under which employees contribute code on behalf of the company.
A CLA template is a document that contains terms and conditions under which contributors contribute code. The Linux Foundation provides an apache style CLA template that is generated after project managers provide project details while creating a CLA group, and contains information such as project name, project full entity name, and contact address. Project Managers use this template under a CLA group to let contributors sign before they can contribute code.
A CLA group defines CLA details, such as CLA types (ICLA and/or CCLA) a project requires for pull requests or push submissions, GitHub repositories and/or Gerrit instances that are CLA enforced, and projects under a foundation that are CLA enabled. One CLA group is used under a unique CLA template.
Individual Contributor License Agreement (ICLA) defines terms and conditions under which individuals contribute code on behalf of their own.
CLA managers are authorized by the company to manage the list of approved contributors under a company’s Corporate CLA. They use the company dashboard to add and manage contributors and other CLA managers.
A CLA signatory signs CLA on behalf of the company. CLA signatories can be any individual with legal authority to sign documents on behalf of the company.
Authorized corporate employees and CLA Managers use the CLA Corporate Console to view and manage company’s CLA information based on their permissions.
Project managers use the CLA Management Console to create CLA groups, add and manage projects, repositories, view who have signed the CLA, and perform many other activities for the projects they manage.
While creating a PR, corporate and individual contributors are navigated to the contributor console to sign CLA under a CLA group before they can contribute to a project.
Individual contributors contribute code on their own behalf (not on behalf of an employer). CLA is verified while creating a PR, and they must sign CLA before they can contribute to GitHub or Gerrit. They are navigated to the LFX Contributor Console from GitHub or Gerrit to sign the CLA.
Project managers or Project admins are authorized by The Linux Foundation to maintain projects. They use the CLA Management Console where they have access to specific projects as per the permission provided by The Linux Foundation. They add and manage projects and repositories on the CLA Management Console.
Legal entity is a team of The Linux Foundation that has legal rights and responsibilities to manage projects and provide access to project managers to maintain projects.\
A CLA group defines:
What CLA types your project requires for pull requests or push submissions—the agreement types are for corporate or individual CLAs
What CLAs and their versions are used for the contributors
What GitHub repositories, Gerrit instances, or both enforce CLA monitoring
A CLA group gives you the flexibility to handle different CLA requirements for various GitHub repositories and Gerrit instances.
To Add a CLA Group:
1. Sign in to the CLA management console.
2. Click a project of interest. The project page appears. A message informs you that your project needs a CLA group. A CLA group defines one or more CLA types that contributors must sign before they can contribute to a project.
3. Click ADD CLA GROUP.
4. Complete the dialog options:
5. Enter a CLA Group Name. The CLA Group Name indicates that a project has one or more CLAs (Individual CLA, Corporate CLA, or both). Consider matching the CLA group name to the project name for easy identification.
6. Select the CLA types that you want applied to contributions to the project:
Corporate CLA: to be signed by a company - This Corporate CLA must be signed by the CCLA signatory for your company. This person has authority to enter into legal contracts on behalf of the corporation.
Individual CLA: to be signed as an individual contributing - A developer who is not contributing on behalf of any company signs this Individual CLA. This individual is contributing to a project on their own behalf. Selecting this type automatically enables the "Contributors under Corporate CLA must also sign Individual" CLA type.
Contributors under Corporate CLA must also sign Individual CLA - Employees (developers) of a company use this agreement. A Corporate CLA may not remove the need for every employee to sign their own Individual CLA as an individual. This option covers both owned contributions and not-owned contributions by the corporation signing the Corporate CLA.
7. Click SAVE.
The CLA group that you added and the CLA types that you specified appear under CLA Groups.
(Optional) Manage CLA Group Details
As a contributor, you must sign CLA document before you can contribute to a repository. EasyCLA lets you sign CLAs from within a pull request. After you sign a CLA or sign a confirmation of association with your company, the status of your pull request is updated and you can contribute.
You can contribute on behalf of a company or contribute individually by doing one or both of the following tasks:
Important: You should not submit a contribution under an Individual CLA if that contribution is done using time and/or material resources belonging to your company. Instead, you should contribute it under a Corporate CLA signed by your company.
​. You write code for your employer and contribute this code to a project on your employer's behalf.
​. You are contributing code on your own behalf (code that you write on your own time, and not for an employer or using your employer’s facilities or equipment).
Gerrit contributors, see .
As an individual contributor, you are contributing code on your own behalf (not on behalf of an employer). You create a pull request in GitHub or submit changed code in Gerrit to inform reviewers about the changes. During the process, your CLA is verified, and you must sign a CLA if you have not already signed, before you can contribute to GitHub or Gerrit.
1. Navigate to the GitHub repository that is linked to the project for your organization.
2. Make a change and send a pull request.
EasyCLA checks your CLA status. It marks a cross or a tick beside your name based on your CLA status.
A cross next to your contributor name means the CLA check failed.
4. Click Authorize LF-Engineering. (Subsequent contributions will not require authorization.)
The CLA Contributor Console appears and shows the CLA group for your project. The CLA types display:
5. Click Individual and then click OPEN CLA.
DocuSign presents the agreement that you must sign. The ICLA is not tied to any employer you may have, so enter your @personal address in the E-Mail field.
6. Follow the instructions in the DocuSign document, sign it, and click FINISH.
You receive an email from The Linux Foundation, informing you that you have signed the CLA.
You are redirected to GitHub. Wait a few seconds for the CLA status to update. A tick appears next to your branch.
7. Click Merge pull request and confirm the merge.
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:
4. Navigate to the Gerrit instance of your project. For example, if you are contributing to OPNFV project, navigate to https://gerrit.opnfv.org​
5. Sign in using your Single Sign-On (SSO) account.
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. Select Individual CLA (ICLA), and click Please review the agreement.
9. Sign in to EasyCLA if you are prompted.
10. Click OPEN CLA on the dialog that appears: DocuSign presents the agreement that you must sign. The Individual CLA is not tied to any employer you may have, so enter your @personal address in the EMail field.
11. Follow the instructions in the DocuSign document, sign it, and click FINISH.
You are redirected to Gerrit. Wait a few seconds for the CLA status to update.
As a corporate (employee) contributor, you are contributing code on company's behalf. When Corporate CLA is signed for the project, you confirm your association with the company during your first pull request or change submit. Your subsequent contributions will neither require association confirmations nor will they be gated by CLA check.
1. In GitHub, go to the repository that is linked to the project for your organization.
2. Make a change and send a pull request.
EasyCLA checks your CLA status. It marks a cross or a tick beside your name based on your CLA status.
A cross next to your contributor name means the CLA check failed.
4. Click Authorize LF-Engineering. (Subsequent contributions will not require authorization.)
5. The CLA Contributor Console appears and shows the CLA group for your project.
6. Select Company. Note: To contribute to this project, you must be added to an approved list by the CLA manager under a signed Contributor License Agreement. You are contributing on behalf of your work for a company.
7. Continue:
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:
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. Select Corporate CLA, and click Please review the agreement.
9. Sign in to EasyCLA if you are prompted.
10. Continue:
11. After you complete signing the CLA, navigate to gerrit window, sign out from gerrit, and sign in again for the CLA status to be updated.
1. Read the Confirmation of Association statement and select the checkbox.
2. Click CONTINUE.
A dialog appears and informs you: You are done!
3. Click RETURN TO REPO.
You are redirected to GitHub. Wait a few seconds for the CLA status to update or refresh the page.
You must be added to the approved list under a signed CCLA before you can contribute to the project.
To contact your CLA manager to add you to the approved list:
1. Click CONTACT under Contact the CLA Manager to be approved under their signed Corporate CLA.
2. Select an option, and complete the form.
3. Click SEND. A message appears informing you that the e-mail is sent successfully.
You will receive an email notification if the CLA manager approves or rejects your request to be approved as a corporate contributor for the company.
If your company has not signed CLA, Verify Your Permission window appears. To proceed:
Click an answer: Are You a CLA Manager?
Complete the form and click SEND.
The CCLA manager signs a Corporate CLA and adds you to the approved list.
If you don't find your company's name in the list:
Click COMPANY NOT IN LIST? CLICK HERE.
The Verify Your Permission of Access dialog appears.
Click an answer: Are You a CLA Manager?
Complete the form and click SEND.
The CCLA manager signs a Corporate CLA and adds you to the approved list.
3. Click or Please click here to be authorized.
​
You can download the PDF document by clicking the link form the email. You will be redirected to Linux Foundation's website. If the download doesn't start automatically, click Proceed to Download.
​​ ​​
3. Click or Please click here to be authorized. Note: The Authorize Linux Foundation: EasyCLA dialog appears.
​​
4. Navigate to the Gerrit instance of your project. For example, if you are contributing to OPNFV project, navigate to ​
5. Sign in using your account.
​​ ​​
This message appears if you are added to the approved list, and your CLA doesn't require you to sign ICLA. If the CLA is configured for you to sign ICLA, you will be redirected to sign an Individual CLA, as shown in .
YES— You will be redirected to the to .
NO— A Request Access form appears. Continue to next step.
YES— You will be redirected to the to to a project.
NO— A Request Access form appears. Continue to next step.
You are a CLA signatory if you are authorized to sign a CLA on behalf of the company. You receive an email informing you that you are designated to be an authorized signatory for a company. You can review and sign a corporate CLA on behalf of the company.