Contributor License Agreements (CLAs)
If you’re here, it’s hopefully because you’re looking to contribute code to one (or more!) of our projects. We’d just like to extend a heartfelt ’thank you’ in advance, we appreciate any and all contributions.
Before we can accept any external contributions though, you’ll need to sign a CLA. If you’re familiar with the process, you can skip straight to the good stuff.
What’s a CLA?
Paraphrasing from the Apache Software Foundation, a Contributor License Agreement (CLA) allows open-source contributors to retain full rights to the contributions they provide to Silicon Ally, while providing Silicon Ally with the rights to distrbute and build upon those contrinbutions.
Why do I need to sign a CLA?
The CLA allows us to accept contributions from external contributors without worrying about future copyright claims. The Google Open Source office has a more thorough explanation on why they require contributors to sign their CLA, which is very much in line with our own rationale.
What’s in the CLA?
Our CLA is based on the Apache Contributor License Agreements. If you have any questions, feel free to reach out to cla@siliconally.org.
Signing the CLA
We use a GitHub Action called contributor-assistant to manage our CLAs.
To sign an individual contributor policy:
- Read the Individual Contributor License Agreement
- Pay special attention to section 4 of the agreement and confirm that you either do not need a Corporate Contributor License Agreement, or that your employer has already completed one.
- On your PR contribution, wait to be prompted by
CLA Assistant Lite, then comment on the PR:I have read the CLA Document and I hereby sign the CLA - Contribute to your heart’s content!
To sign a corporate contributor policy:
- Read the Corporate Contributor License Agreement
- TODO(#76): Figure out the flow here.