Contributor License Agreement issues

[HowardLook]

• [x] Put blank CLAs on developer microsite
• [x] Reach out to existing contributor and get a CLA in place
• [x] Put some kind of process in place for when people issue a pull request to make sure we have a CLA for them (e.g. keep a list of GitHub handles for CLAs that are in place, but keep signed CLAs out of public GitHub repos since they have PHI on them)

Blank and completed ones are here (in .docx and .pdf): google drive / Tidepool Legal / Contributor License Agreement

[brandonarbiter]

@HowardLook Is this complete? If so, I suggest we close. If not, I suggest we close and move to Trello.

[HowardLook]

Yes, CLA is now on microsite, and we have this language/process when we get a new pull request:

There's gonna be one bit of administrative thing that we are going to have to do before we can accept the contribution as well: get agreement to a CLA. Here's the canned text for that ;).

Before I can merge the pull request, we need you to agree to our CLA. You can find the CLA at http://tidepool-org.github.io/TidepoolCLA.pdf.

If you are working on your own behalf and agree to the CLA, responding here with a comment of "I agree to the terms of Tidepool Project's Contributor License Agreement as it exists at http://tidepool-org.github.io/TidepoolCLA.pdf on " is sufficient. If your contributions are on behalf of a company, can you have your company fill out the corporate CLA and submit it to us?

[kentquirk]

I hate hate hate Google Drive. Even with the information you provided, I can't find the corporate CLA, and the corporate CLA is not in the microsite. Can you please get me a link to the doc, or mail it to me, or post it on the microsite?

[HowardLook]

http://tidepool-org.github.io/TidepoolCLA.pdf