Closed tomschenkjr closed 9 years ago
If someone's posting code and making it publicly available, it doesn't seem like they should need a CLA. After all we're using examples from SO, lots of packages, suggestions from people, and lots of other help in this project already. If we have to fill in every contribution with a CLA this might become literally impossible, but definitely unfeasible.
Yeah, a CLA is still needed. Had a lot of conversation about this 2+ years ago to derive the language with lawyers. Major open source projects, such as Apache projects and Ubuntu, require CLAs.
The most significant protection is if an employee from, for instance, IBM, submits a modification, the CLA protects us from IBM suing us for taking their IP. The CLA basically declares any modifications being submitted are being owned by the person making the submission (and not any 3rd party or company). This also helps if someone is stealing other proprietary code and placing it in our projects.
We don't need to go back to collect CLA signatures, everyone making contributions is covered under employment obligations (you + me + CDPH + Aakash) or other agreements signed earlier (Allstate). Using examples or using open source projects from us doesn't require a CLA.
CLAHub makes it really easy to collect signatures and fill out a CLA. It only needs to be signed once for contributors going forward.
Looks like clahub.com only works for public repospitories, so we might have to add later.
Ah, yeah, you’re right. This can be completed after the pull request is created and accepted into Master.
From: Gene Leynes [mailto:notifications@github.com] Sent: Tuesday, May 05, 2015 11:50 AM To: Chicago/food-inspections-evaluation Cc: Schenk, Tom Subject: Re: [food-inspections-evaluation] Add Contributor License Agreement (#51)
Looks like clahub.com only works for public repospitories, so we might have to add later.
— Reply to this email directly or view it on GitHubhttps://github.com/Chicago/food-inspections-evaluation/issues/51#issuecomment-99138026.
This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail (or the person responsible for delivering this document to the intended recipient), you are hereby notified that any dissemination, distribution, printing or copying of this e-mail, and any attachment thereto, is strictly prohibited. If you have received this e-mail in error, please respond to the individual sending the message, and permanently delete the original and any copy of any e-mail and printout thereof.
Fixed with 297820d1955369b1c13cddb3ea497b730ef93cde