Contributor License Agreement Updates #85559
Comments
This is part of the work required to switch over to the new PyTorch Foundation CLA (#85559). Pull Request resolved: #86127 Approved by: https://github.com/malfet
|
Pinning this issue since this is relevant for all PyTorch contributors |
|
A question that doesn't appear answered in the FAQ, or the project's issue history as far as I can tell based on searching: Is a Developer Certificate of Origin declaration acceptable for contributions to the PyTorch Project? |
Good question, and apologies for missing it. No, a DCO is not acceptable in place of the CLA. There's a lot of fun discussion around these options but generally a project picks one or the other (or neither). This provides consistent coverage. |
|
Ok, it's been ~6 months, so I'm going to close this out and unpin it. The EasyCLA process is well established and all PRs that were open at the time of cutover still have the reference to this issue for anybody who needs to catch up. |
|
Is it still planned a transition for other projects under the pytorch Github org? |
As part of the transition to the PyTorch Foundation, we will be moving away from the Meta CLA (Contributor License Agreement) and over to a Foundation-specific CLA. This will occur on Monday, October 3rd. All open pull requests not merged by this point, and all future pull requests, will require the author to be covered by a new CLA.
Initially, this new CLA will be required only for contributions to
pytorch/pytorchandpytorch/pytorch.github.io. All other repositories in the @pytorch organization will continue to be governed as they are today, until otherwise noted.Quick Links
FAQ
What does this mean for current contributors?
If you have signed our current Individual Contributor License Agreement (ICLA), you will need to sign the new ICLA. If you are contributing on behalf of an organization which has signed the Corporate Contributor License Agreement (CCLA) then a representative from your organization will need to sign the new agreement.
What's the difference between the old and new CLAs?
Both of these are based on the Apache Software Foundation's CLAs, which are used widely throughout the industry. The primary difference moving from Meta's CLAs to PyTorch Foundation's is the legal entity with which you are engaging. There are some other minor differences as well, as demonstrated in these images:
View ICLA Diff
View CCLA Diff
To reproduce these diffs, you can use these formatted copies of the CLAs (with some minimal instructions removed for ease of comparison) available here.
If I have multiple PRs open, will I need to sign multiple times?
No. We will trigger the CLA check on each open PR. Simply follow the instructions in one of your PRs. After you are covered by a CLA, you may need to retrigger the CLA checks on other open PRs you've authored. This can be done either by clicking on the link in the instructions on each of your PRs (which will redirect back and update the status) or you can comment with
/easycla.How do I manage my organization when using the CCLA?
The PyTorch Foundation makes use of the same tooling that other Linux Foundation projects use - EasyCLA. This allows organizations to add and remove members easily, without any complicated process. Some documentation relevant for "CLA Managers" can be found here.
The text was updated successfully, but these errors were encountered: