Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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.
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 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 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.
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
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.
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:
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.