Umbrella issue for the Linux Foundation (CNCF) CLA system

[caniszczyk]

Since the IP assets of Kubernetes are owned by the Cloud Native Computing Foundation (CNCF), it's time for us to move to the CNCF CLA system. We will beta test first on a test repo before rolling it out everywhere. cc: @bgrant0607

[smarterclayton]

Can you describe the process for migration of CLAs?

[caniszczyk]

@smarterclayton we will let the community know as soon as we have the new system up and running, there are a few approaches we are discussing to minimize any workflow disruption

[foxish]

Also see: cncf/foundation#1

[foxish]

We are transitioning to the Cloud Native Computing Foundation's CLA on all kubernetes repositories in the near future.
This transition is expected to occur across all our repositories during the week of 10/3.

Starting today, we are testing the new CLA mechanism in the kubernetes/contrib repository.
The Google CLA bot will operate in parallel with the CNCF CLA bot till 10/3.
Please note that PR merges and the submit-queue are not blocked on the signing of the CNCF CLA at this time, but will be when we complete the transition.

In order to minimize workflow disruption, if you are a contributor,
please visit https://identity.linuxfoundation.org/projects/cncf and sign the CLA as either an individual or an employee, whichever is appropriate.
If there are issues, please reference them in the tracking issue at: #27796

Upcoming steps:

• The submit-queue shall honor the cncf-cla labels.
• The googlebot's cla-yes/no labels shall be removed from the repositories.
• Turn the CNCF webhook org-wide and turn off the Google CLA bot.

[rata]

Hi, I want to sign the individual CLA and the hellosign page at the end asks for a "Title" (Signature, name, title and date).

I don't really know what to put on Title. I tried looking at https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and the previous CLA and no title was required (nor asked). I'm a computer science student.

What should I use for title? Or is it there on purpose or maybe it's a leftover?

Thanks!

[sarahnovotny]

@rata, I think a title of "Student" is a fine solution. @caniszczyk, could you confirm?

[caniszczyk]

@sarahnovotny Student or N/A is fine

[rata]

@sarahnovotny @caniszczyk: thanks a lot!

[foxish]

@sarahnovotny, @caniszczyk, it seems like Redhat is having issues with the CNCF CLA. Can you help them out? It could be an issue with the corporate CLA, or a technical issue and we're not sure.

cc @eparis @ingvagabund

[emsearcy]

@eparis, what happens when you go to https://identity.linuxfoundation.org/projects/cncf and choose "Contribute as an employee"? This should prompt you to associate your GitHub account, which hasn't been done yet.

(Those who are authorized to manage the authorized contributors for their companies are not automatically set up as contributors themselves; the system still expects them to sign up as contributors for tracking purposes.)

[eparis]

@emsearcy I e-mailed @caniszczyk
but when I go to that link I get
Your organization is not authorized under a Corporate Contributor License Agreement. If you have signed agreements, please check back later or use the contact form below.

[eparis]

@emsearcy is there a way we can chat privately? e-mail me? eparis at redhat ?

[jbeda]

I'm hitting a bug with the account system at https://identity.linuxfoundation.org. Who should I contact about that?

Cannot change password on accounts created via github creds

• Created account with github. Never established a password
• Went to change my email address
• Was told I need a password to change email address
• Requested password reset email
• Followed link in email
• Clicked on "reset password link"
• Was told I needed a password to change my password

[emsearcy]

@jbeda, I'm guessing you were logged in still? (The password reset page says "You must log out to use the password reset link in the e-mail"). Otherwise it says you are still logged in when you try and use it.

[bboreham]

I tried to "sign up as an employee", and got as far as "Please contact somebody within your organization who is responsible for overseeing authorized employee contributors for this project".

That would be me; what next?

[caniszczyk]

@bboreham have your company/organization sign up here https://identity.linuxfoundation.org/node/285/organization-signup

[bboreham]

@caniszczyk what I did:

• Visit your URL.
• Login via Google.
• Look for any way to declare my organisation and its personnel.
• Came back here.

Can you say exactly where I click to have the organisation (Weaveworks, Inc) sign up?

[caniszczyk]

@bboreham with that link, there's a way to sign up your organization and e-sign the corporate CLA, once you do that, you'll be able to do everything else

[bboreham]

For me, the way was to open an "incognito" browser window, then after logging in again the form was presented. No amount of logging out or clicking in the original window would bring this form up.

[technicianted]

I Signed the CLA as an individual and onboarded to GitHub. I have a pending PR that complains that I haven't done so. I checked that the email on the commit matches my GitHub which has been verified.

Can you please check?

Here is a link to the PR:
#60962

[dankohn]

@technicianted Please contact helpdesk@rt.linuxfoundation.org and they’ll sort it out for you.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[justinsb]

/reopen

Remains a major barrier to new contributors

[justinsb]

/remove-lifecycle rotten

[tpepper]

FYI last week during the KubeCon / CloudNativeCon China new contributor workshop I observed many (most?) of the participants struggling with the UI/UX in:

https://camo.githubusercontent.com/cdcaa8a1b2679acb1c8452091a05e27c8e68bc54/687474703a2f2f692e696d6775722e636f6d2f74456b3278336a2e706e67

Two things specifically:

• Facebook, Google, GitHub, OpenStack are to varying degrees location or ecosystem specific and also graphical so likely not translated in-browser.
• the "Or -- LOG IN" alternative half of the log in element does not stand out clearly as a clickable element as opposed to just being Linux Foundation blue themed text in a blue box.

Given GitHub is generally required for participation, it might be visually easier to have only two boxes:

1. Log in with GitHub
2. Log in with Linux Foundation ID

and strip the other options from the screen to visually simplify. If the person's selected Linux Foundation ID only then have a screen that asks for their existing Linux Foundation ID or allows creation of one.

I suspect most people will simply choose GitHub and that's the flow for which the dialog should be optimized.

[srmocher]

I've been trying to sign the CLA to proceed with my PR #72275 but I haven't received the agreement by email despite numerous tries. I have also contacted helpdesk@rt.linuxfoundation.org 2 days back but have not received any response yet - it would seem like their responses will be minimal/delayed as it is the holiday period. I was hoping for a way to unblock myself on that PR soon.

[dankohn]

Apologies @srmocher but the Linux Foundation help desk won’t be able to address this until Jan 2.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

/remove-lifecycle stale
/lifecycle frozen

[Anutrix]

I signed the CLA as an individual contributor in the past.
Now I work for a company where I’ll make contributions during worktime and obviously the IP is owned by the company when I do so. But not everything I do outside of work belongs to the company.

My questions:

* How do I change my account from "Individual" to "Employee"? I already changed the email-address, but I can’t find the button for changing this.

* How do I reflect that the IP of the things I create depends on context (when I create things and what it is)? This is not uncommon in European employment law. Because it is illegal for companies to just claim everything people create while they are employees in many jurisdiction.

* So technically I can be both (Schrödinger’s contributor) an individual and an employee contributor depending on quite a few circumstances. How do I keep both things signed?

Same issue. Any updates on this?

[dims]

i think we can close this now :) we can open follow up issues as needed.

/close

[k8s-ci-robot]

@dims: Closing this issue.

In response to this:

i think we can close this now :) we can open follow up issues as needed.

/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.