Blog

Blog

The EasyCLA documentation is now available in GitHub at https://github.com/communitybridge/easycla/blob/master/docs/getting-started.md

Here are the ways you can open the documentation in GitHub:

  • In README.md, find and click the Getting Started Guide link.
  • Go to the docs folder and click getting-started.md.
  • Go to the docs folder, browse the list of markdown files, and open a file for a topic of interest, for example: Install-the-EasyCLA-Application.md.

The EasyCLA documentation in the Linux Foundation Product Documentation remains as a convenience for you, but we will not update it beyond August 29, 2019. For the latest EasyCLA documentation, go to GitHub.

The Linux Foundation Contributor License Agreement Tool is renamed to EasyCLA.

Here are the updated features for the Linux Foundation Contributor License Agreement Tool.

The CLA Management Console is updated to let you more easily:

  • Select a template style to use for your CCLA and ICLA. The template style for Apache CLAs is available.
  • Add CCLAs and ICLAs to CLA groups.
  • Update CLAs with revised versions—you simply add the updated CLA using the same procedure as for adding the initial CLA.
  • View the current and previous CLA versions.

A template lets you create a contract that defines the legal status of the contributed code in two types of CLAs: individual Contributor License Agreement (ICLA) and Corporate Contributor License Agreement (CCLA). 

See:

Add Contributor License Agreements

Add a CLA Group

View Current and Previous CLA PDFs

Here are the new, updated, or fixed features for the Linux Foundation Contributor License Agreement Tool:

  • The CLA Corporate Console now enables you to whitelist entities to contribute under a GitHub username.
  • Fixed a bug where employee contributors were not able to see their companies due to the company not having a CCLA. Contributors are now able to view all companies registered by company administrators in the CLA System. If the company has not signed a CCLA for the project, contributors are able to send an email request to the company administrators to sign the CCLA.

Here are the new or updated features for the Linux Foundation Contributor License Agreement Tool:

  • New CLA templates: OpenColorIO, OpenVDB, Tungsten Fabric
  • CLA managers who send a Corporate CLA to a company signatory in the Corporate Console are now returned to the company page after sending the document.
  • Improved the usability of the Corporate Console by adding prominent buttons to create a company and initiate a CLA signature.
  • Fixed an issue causing pre-filled DocuSign fields to expire.
  • Fixed an issue preventing newly invited CLA managers from viewing their company.
CommunityBridge

With the public release today, we also wanted to update everyone on the open source plans for the software itself. We are currently cleaning up the code, enhancing documentation and getting ready to open source the codebase so that it will be easier for developers to learn the code and contribute. We are a nonprofit and don't have an army of developers so it will take a bit more time. We're also working on soliciting feedback from developers about our plans for the license, code upstreaming model, and code of conduct. In particular we are seeking to align the licensing structure with free software principles. We will open source the codebase with the next release targeted for early Q3.

CommunityBridge is a platform created by the Linux Foundation to empower developers — and the individuals and organizations who support them — to advance sustainability, security, and diversity in open source technology.


Funding is a service on the CommunityBridge platform that helps projects to be financially sustainable. 

CommunityBridge Funding provides a single, centralized location where projects can manage receiving and disbursing funds:

  • funders can donate funds to an account managed by The Linux Foundation, to be used to finance a project’s expenses;
  • maintainers can set funding goals and allocations, and manage disbursements; and
  • project participants can submit expenses for reimbursement and receive corresponding tax documentation.

The Funding service also enables donated funds to be used toward project-wide initiatives, such as stipends for mentorships through CommunityBridge People.


People is a service on the CommunityBridge platform that helps projects to grow their communities, become more diverse, and provide an on-ramp for new participants.

CommunityBridge People provides a hub where projects can offer and manage mentorships:

  • mentees can join an open source community, develop their skills and potentially get an opportunity to connect with prospective employers;
  • mentors can give back with their time and skills, by helping new participants become part of their community;
  • projects can expand and bring in new contributors, to create a larger and more diverse community; and
  • companies and organizations can support the projects that matter to them, by funding mentorship stipends and by offering interview opportunities to mentee graduates.

Some mentorships offer financial stipends to the mentee, which are funded through CommunityBridge Funding. Other mentorships will not offer stipends, but still offer the benefits of a mentor’s guidance and assistance getting involved in a particular developer community.

Additionally, to support its diversity initiatives and to encourage participation from a diverse group of mentees, The Linux Foundation is offering matching stipends for the first 100 mentees selected for diversity mentorships through CommunityBridge People. These stipends will consist of $3,000 USD funded by the project and a matching grant of $3,000 USD funded by The Linux Foundation.

Here are the new features for the Linux Foundation Contributor License Agreement Tool:

Flexible CLA Enforcement for Repositories

CLA groups give you the flexibility to enforce different CLA requirements for various GitHub repositories and Gerrit instances. A CLA group defines:

  • What CLA types your project requires for pull request or push submissions—the agreement types are for corporate or individual CLA signatories
  • What CLAs and their versions are used for the contributors
  • What GitHub repositories, Gerrit instances, or both enforce CLA monitoring

As a project manager, you use the CLA Management Console to add and name CLA groups for your project. 

Gerrit Support

The Linux Foundation CLA monitoring is now available for Gerrit code reviews. Gerrit lets authorized contributors merge changes to the Git repository after reviews are done. Project managers create and configure a Gerrit instance to add Gerrit instances to CLA monitoring. Project managers also modify CLA configurations for the 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.

New CLA Consoles that are Appropriate for Your Role

New consoles let you do CLA tasks in simple workflows that are appropriate for your role: project manager, CLA manager, CLA signatory, corporate contributor, and individual contributor.

CLA Management Console

As a project manager of an open-source project, the new CLA Management Console lets you easily perform the following CLA set-up and management tasks:

  • Install the LF CLA Application
  • Add and manage CLA groups and CLAs
  • Add GitHub organizations and repositories to CLA monitoring
  • Add Gerrit instances to CLA monitoring

CLA Corporate Console

As a CLA manager for a project to which company developers contribute, the new CLA Corporate Console lets you easily perform the following CLA set-up and management tasks:

  • Associate a Corporate CLA to a project
  • Whitelist domain names and Email addresses
  • Edit the Company Name and Manager details

As a CLA signatory, the new CLA Corporate Console lets you easily sign a Corporate Contributor License Agreement (CCLA) on behalf of a company.

CLA Contributor Console

As a contributor, the new CLA Contributor Console lets:

  • Corporate contributors confirm their association with a company that has a signed CCLA
  • Individual contributors sign an individual Contributor License Agreement (ICLA)

The CLA Contributor Console appears as part of your code submission process—you are prompted to click a link to open it.

Enhancements for Contributors

The following CLA enhancements are for contributors:

  • Contributors request association to a company as part of the CCLA submission process. The association is established by company whitelists. The whitelists apply to the CLA group for which the company has signed a CCLA. The CLA application checks whitelists for allowing contributions to a project. A Send E-Mail To CLA Signatory form lets you contact your CLA manager to request association to the company by being added to a whitelist. The Signatory Name and Signatory E-Mail are pre-populated in the form. 

  • CLA signing and submission now uses DocuSign rather than HelloSign.
  • Contributor License Agreement signing is easier for you because the Name and Email fields are pre-populated in the DocuSign document.