Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a CLA (Contributor License Agreement) #17

Open
nschonni opened this issue Sep 28, 2018 · 6 comments
Open

Add a CLA (Contributor License Agreement) #17

nschonni opened this issue Sep 28, 2018 · 6 comments
Labels
intellectual property Intellectual property licences Licences related issue

Comments

@nschonni
Copy link
Member

nschonni commented Sep 28, 2018

https://en.wikipedia.org/wiki/Contributor_License_Agreement
This should be checked by bots for signing if possible https://github.com/cla-assistant/cla-assistant

@gcharest
Copy link
Member

gcharest commented Sep 28, 2018

Jeff McAffer comments/questions

Contributors Licence Agreement:

  • Individual
  • Corporate

Not every company will authorize individual contributions, only corporate.

Opportunity to eliminate friction.

@nschonni nschonni changed the title Add a CLA Add a CLA (Contributor License Agreement) Sep 28, 2018
@smellems
Copy link
Member

https://opensource.com/article/18/3/cla-vs-dco-whats-difference

@gcharest
Copy link
Member

gcharest commented Sep 28, 2018

Joseph Potvin comments/questions

Exec Director XAlgorithms:

TBS IP policy defaults maps nicely to Fedora contributor agreement.

Challenge: no one follows the policy. It's a confusing policy => copyright remains with the supplier.

Copyright stays with the contributors/contractors; government is not on the hook.

Possibility of letting employees retain copyright of the code they are writing.

@gcharest gcharest reopened this Sep 28, 2018
@jtcowie
Copy link

jtcowie commented Oct 26, 2018

CLA's appear to be a slippery slope where in some cases, prior to acceptance, it would be prudent to get the CLA vetted by legal. Checkout Ben Balter's (a Senior Manager of Product Management at GitHub ) post https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-add-a-cla-to-your-open-source-project/

@gcharest
Copy link
Member

gcharest commented Nov 12, 2018 via email

@gcharest gcharest added intellectual property Intellectual property licences Licences related issue labels Nov 17, 2018
@gcharest
Copy link
Member

So, just to continue the discussion here, we will need to look at both sides of this:

  • CLA to contribute to external OSS projects.
  • Whether we need CLA for Government of Canada OSS projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
intellectual property Intellectual property licences Licences related issue
Projects
None yet
Development

No branches or pull requests

4 participants