Deno: Enhancing the Contributor License Agreement (CLA)

Created on 30 Jun 2020  路  6Comments  路  Source: denoland/deno

Hello friends,

I, and potentially a few other folk at Bloomberg, would like to contribute to Deno. The only hold up is the Deno Individual Contributor License Agreement (CLA).

There are two issues with the CLA that mean our Open Source Program Office (OSPO) is unwilling to let employees sign it. Other companies are likely to have similar blockers, so hopefully solving these issues will help other folk to contribute to Deno too.

1. Copyrights and patent licenses are assigned to an individual person

The CLA assigns copyrights and patent license to an individual person. We can only sign it if some other type of legal entity is used.

Just to highlight how unusual this is, our OSPO team, that has been running for over six years, has never been asked to approve a CLA where the assignment is to a named person.

2. There is no Corporate Contributor License Agreement

Our employees do not have permission to license patents owned by the company, so they cannot sign the current agreement.

Introducing a Corporate Contributor License Agreement would solve this problem. Here is one example from Apache.

As a success story, when we first started working with Microsoft on TypeScript, the project had no Corporate CLA. We worked with them to put one in place and enhanced the CLA-assistant bot (that Deno also uses) to be super easy-to-use - checking compliance based on the origin org of a Pull Request.

Most helpful comment

馃帀 馃帀 Really looking forward to having contributions from Bloomberg! Have lots of respect what you folks have Bloomberg have been doing in the wider community!

All 6 comments

Hi @robpalme, thanks for relaying the explicit requirements you have. I've been meaning to update the CLA for a while - I'll get on that this week.

馃帀 馃帀 Really looking forward to having contributions from Bloomberg! Have lots of respect what you folks have Bloomberg have been doing in the wider community!

@robpalme Issue number 1 is now resolved. The CLA now assigns patents and licenses to Deno Land Inc, a legal entity.

Hi @robpalme, I've updated the CLA with the entity Deno Land Inc rather than my personal name. However I'm unable to get the app we use (https://cla-assistant.io/) to display both the corp and individual. Is it possible that I send you all the corporate agreement and have you sign it manually? The corporate agreement is here https://gist.github.com/ry/3c2e34f5fcd5cc3e8ee91ddef80d73c1 - you can printed that out , have it signed, and email it back to me [email protected]. Then I can add any Bloomberg contributors manually to the CLA assistant accept list.

If you're using an up-to-date version of CLA Assistant, there's an even better option (which another person at Bloomberg contributed!). You can add 'bloomberg' to the accept list, and it will accept PRs which originate from forks in our org; then we can manage permissions for individuals to contribute without having to notify you at all (to add or remove). We're using this model with a number of companies already (first one was Microsoft for TypeScript) and it pretty much eliminates the administrative burden. I'll take a look at the CCLA you've posted and may suggest some additional language to support the 'org origin' method.

@kpfleming Thanks for the tip. I was going to add people individually to the accept list, glad to know it supports orgs.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

doutchnugget picture doutchnugget  路  3Comments

davidbarratt picture davidbarratt  路  3Comments

zugende picture zugende  路  3Comments

sh7dm picture sh7dm  路  3Comments

ry picture ry  路  3Comments