Course contentsShow
← Software Engineering
Lesson 1881 of 1,93354. Software Licensing and Intellectual PropertyFree lesson

Corporate Contributor Agreements

Understanding CLAs, DCOs, and employer policies when contributing to open source on company time.

Corporate Contributor Agreements

You'll learn how Contributor License Agreements (CLAs), Developer Certificates of Origin (DCOs), and employer policies govern your open source contributions when you're contributing on company time or using company resources.

What Are Corporate Contributor Agreements?

When you contribute to open source projects while employed, you're navigating a legal intersection between your employer's intellectual property rights and the open source project's licensing needs. Most companies own the code their employees write on company time or using company equipment—even if it's contributed to external projects.

Many open source projects require formal agreements before accepting contributions:

Contributor License Agreements (CLAs)

CLAs are legal contracts where you (and often your employer) grant the project specific rights to use your contribution. They might require you to confirm you have permission to contribute or that your employer has signed a Corporate CLA authorizing contributions. Projects like Apache and Google use CLAs to ensure they can redistribute and sometimes relicense contributed code.

Developer Certificate of Origin (DCO)

The DCO is a lighter-weight alternative to CLAs. By signing off on commits (using git commit -s), you certify that you have the right to submit the code under the project's license. The Linux kernel and many others use DCOs. It's a statement, not a transfer of rights.

Employer Policies

Before contributing, review your employment agreement and company open source policy. Some companies require pre-approval for contributions, while others have blanket policies permitting contributions to specific projects or licenses. Violating these policies can create legal issues for both you and your employer.

Key Takeaway: Before contributing to open source on company time, understand whether the project requires a CLA or DCO, ensure your employer has signed any necessary Corporate CLA, and verify your contribution complies with company policy to avoid intellectual property conflicts.