Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

EasyCLA migration #2778

Closed
mrbobbytables opened this issue Jun 10, 2021 · 19 comments
Closed

EasyCLA migration #2778

mrbobbytables opened this issue Jun 10, 2021 · 19 comments
Assignees
@mrbobbytables @nikhita

Comments

@mrbobbytables
Copy link
Member

The CNCF is ready to cut over to EasyCLA

Right now the target timeframe is just after code-freeze (7/10) when activity in k/k should be minimal.
The validation plan will include verifying org members exist in both systems, in addition to a random selection of contributors, along with running the check against a list of PRs.

/assign @mrbobbytables @nikhita @dims
For main points of contact.

Planning Doc: https://docs.google.com/document/d/1DYSysEYUvLFq_Jhx7QM5AAKhFEKN9cjm27vt1ZKk_Nc/edit

Hi Nikhita, Bob, Amye, and Chris,

I'm working with Pranab and team to support your migration onto EasyCLA v2, and I've created a rough plan for what this could look like - Please take a look and let me know what you think.
LFX EasyCLA v2 - Kubernetes | Go-to-Market Plan
This is pretty similar to what we did for the pilot and general releases, which worked very well. Ultimately, our goal is to make sure this is as smooth a transition as possible for your community, so I hope you find this plan helpful.

I'd like to schedule some time for us to review this early next week. Would any of the following times work for you (all times in PT and IST)?
Mon 5/24 - Between 10am - 1pm PT (10:30pm - 1:30 am IST)
Tue 5/25 - After 3pm PT (Morning next day, IST)
Wed 5/26 - 11:30am PT or after 3pm PT (12am or after 3:30am next day, IST)
**@nikhita - I understand you're based in India, so please let me know what hours are preferred for you and I'll do my best to accommodate.

Thanks!
Stephanie
This was referenced Jun 25, 2021
Closed
Closed
@mrbobbytables
Copy link
Member Author

mrbobbytables commented Jun 28, 2021 •
edited
Loading

Migration has been pushed back to the 2nd week of August, at this time here are the current known tasks excluding messaging that must be completed before a potential roll-out.

  • Verify Kubernetes Org Members exist in both systems
    • LF given a dump of Org Members
    • Verified against their cla DB
  • Confirm Branch Protection configuration with LF
  • EasyCLA support by the prow plugin (CLA Plugin: Add support for EasyCLA test-infra#22721)
  • Configure and test with contributor-playground repo

@mrbobbytables
Copy link
Member Author

mrbobbytables commented Jul 2, 2021 •
edited
Loading

During the org audit multiple members did not come up with an association in the LF CLA DB. Below are the active contributors from the audit that having a missing CLA association.

If you are on this list, please reply here, or reach out to me directly in slack / email killen.bob[@]gmail.com with your email(s) that might be associated with your cla, and if at all possible your lfid. With that we should be able to get it squared away before migration.

@dims
Copy link
Member

dims commented Jul 2, 2021

@mrbobbytables i've pinged everyone on slack as well. 🤞🏾

@mrbobbytables
Copy link
Member Author

Thanks @dims <3

@howieyuen
Copy link
Member

howieyuen commented Jul 4, 2021 •
edited by mrbobbytables
Loading

During the org audit multiple members did not come up with an association in the LF CLA DB. Below are the active contributors from the audit that having a missing CLA association.

If you are on this list, please reply here, or reach out to me directly in slack / email killen.bob[@]gmail.com with your email(s) that might be associated with your cla, and if at all possible your lfid. With that we should be able to get it squared away before migration.

hello, what should I do ?

@wangyx1992
Copy link

The same question as @howieyuen.

@dims
Copy link
Member

dims commented Jul 5, 2021

@wangyx1992 @howieyuen there are instructions from @mrbobbytables :) he needs the following info.

please reply here, or reach out to me directly in slack / email killen.bob[@]gmail.com with your email(s) that might be associated with your cla, and if at all possible your lfid.

@mrbobbytables
Copy link
Member Author

@dims has it right, I just need your email address that you used to sign the cla and if at all possible your lfid. The WORST case is post migration you will have to sign the CLA again.

@howieyuen
Copy link
Member

I am howieyuen, my CLA email is haoyuan@mail.ustc.edu.cn

@wangyx1992
Copy link

I am wangyx1992，my CLA email is wang.yixiang@zte.com.cn

@helight
Copy link

helight commented Jul 14, 2021

I am helight，my CLA email is helightxu@tencent.com

@mrbobbytables
Copy link
Member Author

ref: kubernetes/test-infra#22721 (comment)
Here is the current plan:

  1. Enable EasyCLA as non-blocking org wide next week (accompanied by comms)
  2. Assuming no issues are reported, we cut-over after code freeze (Nov 16th). This means updating the current CLA plugin to look for EasyCLA instead of cla/linuxfoundation, removing our help text, and potentially updating it to also look for /easycla in the comments. The LF will also perform their final sync of the DBs between systems.
  3. Given the time, most PRs should be updated with an EasyCLA status. We script hitting open PRs to refresh CLA status on the remaining PRs.

If there is an issue, we revert to the old system. Anyone that signed up after cut over may have to sign the old CLA.

@brendandburns
Copy link

brendandburns commented Nov 16, 2021 •
edited
Loading

@mrbobbytables I'm seeing discrepancies between the old CLA bot and EasyCLA, e.g.

kubernetes-client/c#93

And this is blocking merges. I'm not sure this change was widely broadcast to all repositories.

@brendandburns brendandburns mentioned this issue Nov 16, 2021
Merged
@mrbobbytables
Copy link
Member Author

@brendandburns thats weird...it shouldn't be blocking, we have prow setup to ignore to the EasyCLA context

@mrbobbytables
Copy link
Member Author

Found the issue, it was only setup to be ignored in kubernetes 🤦

@sftim
Copy link
Contributor

sftim commented Jan 5, 2022

(low priority)
How's this migration going?

@mrbobbytables
Copy link
Member Author

Current plan is to migrate the weekend of Feb 5th, right after Enhancements freeze. comms will be going out later today

@dims dims removed their assignment Jan 31, 2022
@mrbobbytables
Copy link
Member Author

We are now migrated over. 🎉
Going to go ahead and close this out

/close

@k8s-ci-robot
Copy link
Contributor

@mrbobbytables: Closing this issue.

In response to this:

We are now migrated over. 🎉
Going to go ahead and close this out

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mrbobbytables mrbobbytables

@nikhita nikhita

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@dims @helight @brendandburns @mrbobbytables @nikhita @k8s-ci-robot @sftim @howieyuen @wangyx1992