Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Contributor License Agreement Updates #85559

Copy link
Copy link
Closed
@zpao

Description

@zpao
Issue body actions

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/pytorch and pytorch/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 ICLA Diff
View CCLA Diff 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.