gRPC is switching from Google CLA to CNCF CLA - details and timelines
Kailash Sethuraman
Hi All,
If you do not contribute to the gRPC code base, you can stop reading now.
tldr: We are going to switch from the Google CLA to the CNCF CLA. You need to re-sign individual or corporate agreements with the CNCF in order to contribute to gRPC.
As you might recall, per https://github.com/grpc/proposal/blob/master/P1-cloud-native.md, we are now part of the CNCF foundation.
Given the migration, we are retaining the use of contributor license agreements, but will be moving to have those signed with CNCF, instead of Google. We will first add the CNCF CLA bot to our workflow, and then remove the Google CLA bot. The bots are functionally equivalent.
Do note that given that this is a license agreement, we will not manually migrate your consent over. You will need to sign a new CLA with the CNCF for any of your pending or future contributions, either as an organization or as an individual, even if you have previously signed such an agreement with Google.
The timeline for migration is as follows:
Mon Oct 16 2017: Enable CNCF CLA for grpc-go
Mon Oct 23 2017: Enable CNCF CLA for grpc-java, grpc and other repos.
During the transition period, you might encounter friction such as being asked to sign multiple CLAs, or being asked to sign the same CLAs multiple times. We will be monitoring for such friction closely and will try to address them quickly.
We will update this thread if there are any changes to the timeline. If there are any concerns or objections, or if you feel that the terms in the CNCF CLA might newly impact your ability to contribute the project, please let us know!
Thanks,
Kailash and Jan on behalf of the gRPC team