Kubernetes: Umbrella issue for the Linux Foundation (CNCF) CLA system

Can you describe the process for migration of CLAs?

@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

Also see: https://github.com/cncf/foundation/issues/1

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: https://github.com/kubernetes/kubernetes/issues/27796

Upcoming steps:

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

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!

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

@sarahnovotny Student or N/A is fine

@sarahnovotny @caniszczyk: thanks a lot!

@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

@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.)

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

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

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

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

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?

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

@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?

@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

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.

There seem to be some issues with the CNCF corporate CLA. @euank should be covered under the corporate CLA for CoreOS, however

• https://github.com/kubernetes/kubernetes/pull/34058
• https://github.com/kubernetes/kubernetes/pull/33965

do not reflect this.

@caniszczyk could you please take a look at the issue that @calebamiles mentioned above?

It looks like @euank just needs to click "Contribute as an Employee" and will be automatically associated with the CoreOS CCLA.

Yup, thanks @emsearcy, last time I think I must have accidentally ended up with my personal email. Looks good now!

(also, nice profile picture)

When I try to log in with github to verify my CLA, I get an access denied error, and then when I try again I get access denied with "You have already registered this identity". Is there any way I can verify my CLA?

Oh ... and then when I look at the "Details" link for someone that hasn't signed the CLA, I _do_ get _my_ CLA. I would expect to see the CLA status for the user in question.

Also having problems with the CNCF CLA. Chose individual contributor, and was unable to change the email it chose for me which was an old work email, probably pulled from github (luckily was able to access it). Now, I can see my signed CLA but am still not marked approved on the PR.

Also having issues, tried to sign up via GH which had an old email as primary, then signed up using different email and now can not link my GH account.

It's clear that the Linux Foundation (LF) CLAbot is not yet fully baked. What we need right now is some product manager help to analyze where users are (sometimes) getting stuck in a cul de sac. Based on that analysis, we will look at whether to enhance the LF CLAbot or consider alternative (open source) solutions.

I've spoken with @philips about potentially providing some assistance, and hope to have an update soon. If anyone else wants to help shepherd forward this progress, please feel free to contact me by email.

In the meantime, apologies for the delay.

@derekparker I hit the same problem and ended up eventually finding the account edit page: https://identity.linuxfoundation.org/user/me/edit

Logging in via my github account and then manually changing the email to my CoreOS one got it to work. I think I had to go through the password reset workflow to be able to edit my details as well though

@dankohn, i think some robust documentation on the corporate signup,
corporate individual signups, and common troubleshooting out of these GH
issues would be a huge start.

On Tue, Oct 25, 2016 at 8:24 PM, Euan Kemp [email protected] wrote:

@derekparker https://github.com/derekparker I hit the same problem and
ended up eventually finding the account edit page: https://identity.
linuxfoundation.org/user/me/edit

Logging in via my github account and then manually changing the email to
my CoreOS one got it to work.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes/issues/27796#issuecomment-256239957,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHxigmn_N1BhGJDqvbBLWoCyNxMbsZlks5q3sfXgaJpZM4I7IQL
.

I'm the manager for the Red Hat org. When people ask me what is wrong I generally have no idea. I have no idea how to get that visibility, but if it didn't just work I'm totally lost...

@caniszczyk @emsearcy The webhook failed and no cncf-cla status on https://github.com/kubernetes/kubernetes/pull/35581. Would you be able to check on this?

@dankohn I am currently emailing potential folks we could work with; and I need to write the product requirements doc. I hope to do that by EOW.

@foxish Did we turn off the Google CLAbot in the kubernetes repo?

@bgrant0607 No, we have not done that. We will turn it off org-wide only after we have the CNCF mungegithub bot based on webhooks. Blocked by https://github.com/kubernetes/contrib/issues/1834

I'd like corporate contribution metrics to be independently verifiable by different groups.
It seems like the CLA process is an excellent forcing function which can be used to help maintain a map of individual contributors and their corporate affiliations (over time).

I've outlined a format for these requested CLA disclosures in this issue: https://github.com/kubernetes/contrib/issues/1972

We are ready to switch over to gate on the CNCF CLA by the end of the week. Will send out documentation, FAQs and so on this week before we complete the transition.
The blocking issue thus far was: https://github.com/kubernetes/contrib/issues/1834, which is now fixed.

cc @dims @soltysh @sarahnovotny

thanks a ton @foxish

The rollout is now complete and the kubernetes and kubernetes-incubator organizations are using the CNCF CLA.

@emsearcy @caniszczyk Could you please take a look at https://github.com/kubernetes/kubernetes/pull/35672 ? The author says he signed the cla but the status still says that he hasn't.

@emsearcy I hit an issue as well https://github.com/kubernetes/kubernetes/pull/37640#issuecomment-263760417

Aside: I am looking at open source options for the CLA handling so we can dig into and fix these issues without being a SPOF on @emsearcy. Nothing off the shelf fits the mold ATM.

PTAL, @emsearcy or @caniszczyk -- another deis employee @michelleN is having issues with CLAbot recognizing her CCLA.

User question:
Can I sign the CNCF CLA as an employee and as an individual?

I'll aggregate questions like this and update the FAQ so that we don't have to intervene manually so often.

To elaborate on the previous comment:

I've already signed the CLA as an individual using this Github account and my personal email. Now my employer has signed the CLA and I want to be able to contribute using the same Github account, which also has my employee email registered.

When I click through to sign up as an employee, I get the following message:

The system was unable to associate you with any organization which has signed a Corporate Contributor License Agreement for this project. Please ensure you are using your organization email address on your profile, contact somebody within your organization who is responsible for overseeing authorized employee contributors for this project, or use the contact form below.

My Linux Foundation profile has my personal email set and there doesn't seem to be any way to add multiple emails.

I am having issues as well. My company signed the CCLA. My LF ID shows that I am part of the CNCF Contributors group. But I can't link my LF Identity to my github identity. I get the error "This identity is registered to another user" when I try to link LF Id to github Id. I am using different emails for LF (company) & Github (personal). Probably a LF Id issue but maybe some else has hit this.

Blocked on my k8s pull request.

In the kubernetes/helm repository, somewhere in the process before creating a PR, I got directed to the Google CCLA form. After creating the PR, the LF CLA bot came in and directed me to the CNCF CCLA form.

You probably need to fix that first link, as it causes confusion and extra work for managers (which rarely is a good thing :)).

Following up on my previous comment:

I decided to create a separate GitHub account and use that for my corporate CLA. I removed my corporate email from my personal account and used it for my new account (https://github.com/yissacharcw).

My organization then sent me an invite to join the the Linux Foundation. I followed the link, and logged in using my new GitHub account. I filled in the account creation info and tried to create an account but got the error that my email was already in use. This should not be the case, given that I have not yet used this email to register an account. I don't see any indication on my personal account that the corporate email is used there. There is no info on how to claim this email for use.

I'm now stuck in that I have no way to register my corporate email for a Linux Foundation account.

Please email [email protected] to receive support regarding Linux Foundation IDs or signing CLAs. We'll need info like the email addresses being used that we wouldn't want to ask here, plus it's hard to track individual requests throughout a single thread. Using the contact forms on any "dead ends" in the CLA signing process will also create a support ticket with the Linux Foundation.

A couple comments on the above for posterity:

You shouldn't need a second Linux Foundation ID in order to contribute "as an employee" instead of as an individual. You can be associated with an organization either by your organization's CCLA manager sending you an invite, or, if enabled by your CCLA's manager, matching the corporate email address. You would need to temporarily change the email address on your Linux Foundation ID profile to do the latter if it is not currently your organization's address ("Please ensure you are using your organization email address on your profile").

Following an invite to join an organization can be done by logging in to your existing Linux Foundation ID account.

You cannot associate your GitHub account with more than one Linux Foundation ID.

Statuses not updating appears to be a bug: e.g. every update to 37640, our lfcla bot (a standalone webservice that receives Github notifications and updates the PRs based, on the user's status in the LF CLA system) has tried to set a "philips authorized" cla/linuxfoundation state=success status notification on the commits, which according to the go-github function is running successfully—except that Github doesn't actually save it. I'll look into this.

I'm also getting the error "This identity is registered to another user." like @hasahni. Initially, LF email was personal (I signed up as an individual contributor), and Git email had my company email as the primary address. I changed my Git email, but I'm still getting the same error.

I emailed the address @emsearcy posted above, and they were able to resolve my issue by unlinking my company email from whatever account it was linked to. I was then able to create a Linux Foundation account with my company GitHub account and company email address.

As mentioned above, it's easier if you just use one account. If you go back to https://identity.linuxfoundation.org/projects/cncf you can choose "Employee" if you chose "Individual" before, and vice-versa. Your organization manager can remove you from the org at a later date if you shouldn't be authorized under that org any more.

Linux Foundation IDs can be associated with logins to various LF project web sites, conference proposals, and our sysadmin certifications (which should stay with you when you change companies), so the account is expected to be more of a "belongs to you/follows you" setup. (Similar to how all of you reporting this issue presumably only have one GitHub account you are using!)

We're seeing a lot of people that continue to object to the CLA.

Is the source code for the CLA bot open source (and if so where is the repo), so we can try to improve the flow? Or are screenshots available (particularly for the individual version)?

_Something_ is obviously causing people to drop out of the funnel. I noticed right away that I could sign in with a non-github account, but then I had to sign in with github to link a github account. Unfortunately I don't have a second github account so that was as far as I got. But there's definitely low-hanging fruit.

Other thoughts:

• Is there a strong no-spam policy on the use of the email address, obviously linked?
• Does the linux foundation id default to my email address?

The LF CLAbot is not open source, and is not going to be open sourced, because (despite good work by @emsearcy) it's a hairball, especially in terms of its backend storage. On behalf of CNCF, I want to apologize for the problems people are encountering. The best short-term fix for login issues is to email [email protected] as they are quite responsive, although only during PT business hours.

The long-term fix being investigated by @philips is to work with one of the open source CLAbots and contract with one of their core developers to make the changes needed by Kubernetes and also to get those changes upstreamed. I'm hopeful we'll have progress on that front in January.

I don't think is so much a problem with CLAbot as much as the fact that the CLA is required in the first place. When a user has a largish feature that they're trying to contribute back upstream, they're likely to bear with it and go through the CLA process. But when the user is just contributing a simple doc fix or a small bug fix they're likely to just bail.

Consider the issue @justinsb just linked: the user is contributing literally a single-character doc fix. And for that they get saddled with a CLA that forces them to enter their info and a legal agreement. It's no wonder they want to bail out.

I know from my own personal experience that I resisted contributing doc fixes for a while since I didn't want to have to deal with the CLA. Only when I had a feature that I really wanted added did I go through the hassle of signing the CLA.

I don't know whether it is legally feasible but I really think that non-code submissions should not be subject to the CLA (it would also be ideal if trivial code changes were not subject to the CLA but I realize that line is harder to draw than code/non-code).

I understand the need for the Kubernetes project to protect itself legally, but pushing the CLA on trivial changes actively discourages the drive-by PRs that are so common in GitHub projects.

It also seems slightly absurd to me that if the user had just opened an issue instead ("The docs should say us-east-2 not us-east-1"), there would be no CLAbot interaction and someone would just make the change for them.

Furthermore, since I'm aware of the issue now, having seen the PR, I can go ahead and submit the fix myself (unless you tell me that this falls afoul of the CLA, which I would find even more surprising!).

Based on feedback from several actual and prospective projects, CNCF modified it's charter last month to enable each hosted project to determine whether or not they want a CLA (long thread with context). However, I think it's very unlikely given that Kubernetes is now one of the highest velocity software projects in history that the maintainers will decide to give up on the CLA. If you want to encourage them to do so, I'd suggest you open a new issue.

For now, we're assuming the CLA requirement will stay (and also that CNCF will likely have new projects with CLAs well), so we want a CLAbot that causes as little friction as possible.

fyi, OpenStack has had this same issue with requiring a ICLA/CCLA for a long time. "We" are moving towards the DCO:
https://wiki.openstack.org/wiki/OpenStackAndItsCLA#The_Proposal

Hello!

I am trying to sign the CLA but am stuck on the "validate email" step. I have not received an email (checked spam and everywhere) after the validation code was supposed to be sent to me. I have waited 5 hours so I have a feeling it won't be coming. I have also tried the "re-send verification" button a couple times and this has not sent me a code either.

My github email (the authorization I chose when setting up the linuxfoundation account) is the correct email.

I am not sure the correct place to ask this but the CLA FAQ told me to come here if I had any issues.

Thank you!

Apologies. Please email Linux Foundation Helpdesk <
[email protected]>.

On Wed, Jan 18, 2017 at 1:23 PM, khalpin11 notifications@github.com wrote:

Hello!

I am trying to sign the CLA but am stuck on the "validate email" step. I
have not received an email (checked spam and everywhere) after the
validation code was supposed to be sent to me. I have also tried the
"re-send verification" button a couple times and this has not sent me a
code either.

I am not sure the correct place to ask this but the CLA FAQ told me to
come here if I had any issues.

Thank you!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes/issues/27796#issuecomment-273605799,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC8MBlgbtF51VU6H50t-IT3_PFEDyOn3ks5rToLQgaJpZM4I7IQL
.

--
Dan Kohn dan@linuxfoundation.org
Executive Director, Cloud Native Computing Foundation https://cncf.io/
tel:+1-415-233-1000

Hi - I tried to register as a Heptio employee but the system was unable to verify me. Please help! Thanks.

@skriss Please email the the Linux Foundation Helpdesk [email protected] with your email and GitHub username.

I'm trying to register CERN with the CNCF CLA.

I have created a CNCF CLA for company 'test' to get a copy of the agreement to review with our legal team. Unfortunately, I now cannot register CERN as an organisation.

Can you delete the 'test' company that I registered and reset me back to the status of not being known by the system. My e-mail is tim.[email protected].

@noggin143 You've got to email your request to [email protected] and they will help you out.

I've tried to sign the CNCF CLA, but am still having issues. I also should have been registered as the official contact for the OpenStack Foundation to approve other contributors. I've also filed a ticket with the helpdesk. Thanks, Chris

@hogepodge, please email [email protected] to troubleshoot this. (as a note, being registered as the contact does not automatically put you in the CLA group.)

I've signed CNCF CLA. My commit is https://github.com/honkiko/kubernetes/commit/38b95f0c38f46303e7b091e56a70a515a8c4706c.patch, in which "[email protected]" is present. And I added this email into my github account email list.
But my pull request (https://github.com/kubernetes/kubernetes/pull/42232) is still in state "cncf-cla: no".

@honkiko Tencent hasn't signed the corporate CLA yet:

https://identity.linuxfoundation.org/node/463

If you have a copy of the signed CCLA you can send it to me [email protected] or to [email protected]

From a quick look, looks like "[email protected]" tried to esign it but never finished.

I've submit a PR, and the author of commit used my primary email which signed in the Github, but why the CLA sent to my public email all the way? Even I changed the public email address to my primary email, the CLA still sent to the previous email address? how to solve it?

I tried to sign up as an individual, but the link https://identity.linuxfoundation.org/projects/cncf leads to a page not found.

@sdomula I've opened an urgent ticket with the Linux Foundation to resolve. I'll post again when it's fixed.

@sdomula This is now resolved. We're investigating what caused the downtime. Sorry for the hassle.

Page not found : https://identity.linuxfoundation.org/projects/cncf

If I am right the correct url is now : https://identity.linuxfoundation.org/node/285/

Right ?

Looks like a bad config push.

/cc @caniszczyk

Re-escalating now.

And it's back up. We'll add our investigation into this downtime into the other investigation.

Hi all, I'm having troubles satisfying the cla-bot for https://github.com/kubernetes/charts/pull/766. I think it's because I signed up as "[email protected]" whereas my git commits are under "[email protected]". I've since changed my Linux Foundation email to match my git commits, but can't seem to generate a new CLA under the new email. Please halp.

@jpoon please email [email protected]

Will do. Thanks @dankohn

Hello, I'm having trouble passing the cla check on https://github.com/kubernetes/helm/pull/2143 and as far as i can tell i have done everything I needed to such as email is set correctly, form is signed and so on. Can anyone please help why the cla is not passing? thanks.

@dankohn I emailed [email protected] and the last response was a week ago. Not really sure how to get this resolved....

@jpoon apologies for the problem. Could you please resend to the help desk with a cc to caniszczyk at linuxfoundation.org

I've requested an email twice. Only first one arrived, and it's now expired. Second one never arrived. Failed the third time too.

@TheStalwart Have you emailed the help desk?

After another retry, i was able to sign via the link that was previously expired. Yay!

I'm having trouble satisfying the cla check for https://github.com/kubernetes/test-infra/pull/2450 . I signed up as an employee of Google using my github account and I used the same email that I use on my commits. I received an email asking to verify my email address and since then the linuxfoundation site says that I have signed up properly. However, my pull request still has the "cnfc-cla: no" flag, even after leaving additional comments on the PR. I would appreciate any help I can get on this issue. Thanks!

I'm seeing the same thing on several PRs.

@spxtr can you point out the relevant PRs?

Also, I recommend emailing "Linux Foundation Helpdesk helpdesk@rt.linuxfoundation.org" if you run into any CLA issues.

Most of the time, it's because you don't have the respective email listed in your GitHub profile settings or you didn't fully sign in to https://identity.linuxfoundation.org/projects/cncf and link your GitHub profile with the LF system.

I'm having trouble satisfying the cla check for kubernetes/test-infra#2450 . I signed up as an employee of Google using my github account and I used the same email that I use on my commits. I received an email asking to verify my email address and since then the linuxfoundation site says that I have signed up properly. However, my pull request still has the "cnfc-cla: no" flag, even after leaving additional comments on the PR. I would appreciate any help I can get on this issue. Thanks!

Same here, except I signed as a Individual Contributor, using the exact same email like GitHub (using GitHub Login). Still try to find out what went wrong.
I was writing to Linux Foundation Helpdesk, so far I nothing heard back from them.

https://github.com/kubernetes/kubernetes/pull/44727 Submit Queue — PR is missing CLA label; needs one of cla: yes, cncf-cla: yes or cla: human-approved

I think I have done everything...

I tried signing up as an individual (gh<at>purefiction.net), but after abou 4 hours I've yet to receive a confirmation email from the CNCF thing. Nothing in spam folder.

@atombender Sign-up on hellosign with same email address and you might the find the agreement doc there. Unfortunately, there is no re-send agreement option.

@dolftax: What is "hellosign" and how to I get there? That email address is not the one I use to author commits, so I need to change it, but it won't let me go through the process again.

@dolftax: I was able to get further by deleting cookies and going through the account creation here. However, nothing else happens. If I then go back to that same link, I get a page saying:

A Contributor License Agreement has been sent to your email address. This must be signed electronically to complete the contributor signup process.

...but no email.

@atombender @dolftax please email [email protected] and they can assist you with your issues. We're also evaluating how to change the error messages to make the next step clearer when the email doesn't arrive.

Our helpdesk will be following up to your ticket, but for general notes: HelloSign (our e-signing vendor that sends the agreement emails) does send reminders at 3 and 7 days. Our Helpdesk can send a reminder manually, too, even though this isn't functionality present in the user-facing UI.

As for the comment about signing up at Hellosign (thanks for the suggestion @dolftax!), that would be to go to https://www.hellosign.com/ and hit "Sign Up". A free account lets you send up to 3 documents per month, not counting documents sent to you by other people (which are normally signed without any account creation on the HelloSign side).

(I do see a pending agreement on the HelloSign "side" for the "gh" email. Their outbound notification didn't bounce, either, or it would tell me that.)

@dankohn: is this a common problem that users don't receive emails, where there is no typos or similar problem in play? We can reach out to HelloSign support and see if they can provide some case-by-case troubleshooting into these.

@dankohn Re-send agreement from linuxfoundation UI would be much better.

I have signed the CLA, but still the "cnfc-cla: no" flag, pleast take a look @foxish @sarahnovotny

I have a problem with the CLA, https://github.com/kubernetes/test-infra/pull/2764
I confirmed using the right email, logined CNCF as an individual, linked it to github and google, and make another commit afterward, still got error on CLA, could you please take a look?

@yutongz can you email Linux Foundation Helpdesk helpdesk@rt.linuxfoundation.org with your issue, make sure that your github id is linked with https://identity.linuxfoundation.org/projects/cncf and your commits

@sarahnovotny and @foxish
I’m having issues with signing the CLA

I've signed as [email protected] and I can't sign with [email protected] (primary github email) so I got problem on github like this one: https://github.com/kubernetes/contrib/pull/2548 (still waiting for my sign on CLA)

I've mailed to linux foundation a month ago, but I'm still blocked...
can you fix it ?

@naarani Apologies for the issue. I'll escalate this with LF IT.

The license check for https://github.com/kubernetes/community/pull/631 is failing, yet my profile (see attached) seems to put me under the CNCF group:

My email at https://identity.linuxfoundation.org/user/me/edit is the same as the one I used on the commit.

Is there anything I can do to get this cleared up? Thanks so much!

That group also shows for unsigned (pending) CLAs.

Thanks. It's likely that I didn't sign then.

I've been waiting for the email for a while now, and haven't gotten it...checked spam and all. Also, I don't seem to be getting copies of the messages with "Send me a copy" checked, so it could very well be a deliverability issue. I use FastMail. Is there a webpage or alternate way I can sign the agreement?

@wyc: yes, another user with Fastmail also wasn't getting email. We traced the problem to Fastmail not accepting mail from HelloSign, our e-signing vendor, with the following mail server response (provided by HelloSign, as it's their IP address):
451 4.7.1 Data command rejected: Host
198.61.255.111/do255-111.hellosign.com has exceeded the per-day email
limit of 40, try again later - helo= - RLR001

Would you be able to follow up with Fastmail and let them know that this 40-day-per IP limit (seems really low to me...) is affecting your ability to accept email from this legit service provider?

Above, it was suggested by another user above that if you go and log in/register at www.hellosign.com you should be able to see the pending e-sign request (though I haven't tried this to confirm that it works). Unless you have a Google Identity with this email, providing a validated email via SSO, you'll likely need to be able to receive an initial account validation email from HelloSign ... and then we're back at needing Fastmail to stop severely rate-limiting HelloSign.

Okay, @emsearcy, that worked like a charm. Thanks. I'll contact my email provider and try to get them to resolve this.

I did a small write-up on this below that we can hopefully add to https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ

Because GitHub Wiki doesn't currently allow outside contributions, below counts as a contribution based on the license I just signed :)

I'm not getting an email containing the CLA for Individual Contributor Agreements.

@emsearcy explains in
https://github.com/kubernetes/kubernetes/issues/27796#issuecomment-303234338
that some users of certain email providers (namely FastMail) were experiencing
deliverability issues with emails from the e-signing vendor, HelloSign. Until this
is redressed, the following workaround is available:

1. Create an account on HelloSign using the same email for the CLA.
2. Go to the "Documents" section using the left navigation bar and press the
   "Sign" button for "CNCF Individual Contributor License Agreement".
   
3. Review and sign, if desired.
   
4. Confirm that the agreement has been signed in the "Documents" section.
   
5. If you have an existing PR with cncf-cla: no, wait 5 minutes for HelloSign
   and the CI servers to resolve the new agreement. Leave a new comment on the
   PR, and the cncf-cla: no label should become a cncf-cla: yes.
   

Markdown:

### I'm not getting an email containing the CLA for Individual Contributor Agreements.

@emsearcy explains in
https://github.com/kubernetes/kubernetes/issues/27796#issuecomment-303234338
that some users of certain email providers (namely FastMail) were experiencing
deliverability issues with emails from the e-signing vendor, HelloSign. Until this 
is redressed, the following workaround is available:

1. Create an account on [HelloSign](https://hellosign.com) using the same email for the CLA.
2. Go to the "Documents" section using the left navigation bar and press the
   "Sign" button for "CNCF Individual Contributor License Agreement".
   ![HelloSign Documents Section](https://i.imgur.com/n6o6KzO.png)
3. Review and sign, if desired.
   ![HelloSign Signing Page](https://i.imgur.com/Tcyms6C.png)
4. Confirm that the agreement has been signed in the "Documents" section.
   ![HelloSign Documents Section Confirmed](https://i.imgur.com/99QWSNu.png)
5. If you have an existing PR with `cncf-cla: no`, wait 5 minutes for HelloSign
   and the CI servers to resolve the new agreement. Leave a new comment on the
   PR, and the `cncf-cla: no` label should become a `cncf-cla: yes`.
   ![CLA Fixed](https://i.imgur.com/pKhLQH5.png)

Thanks @wyc! Updated the FAQ.

Hi,

I tried to sign the CLA on behalf of my company. I signed up with Github, and added company details. The CLA that was generated has my person email in it though. I have gone and created another account with my company email and invited it as an organization manager. Is it possible to re-trigger the generation so it has my company email in the document? My company email is adam[@]iflix.com, and my personal one is adam[@]boxxen.org

Hi! I want to sign my new organization (blackduck software) up as a kubernetes contributor - however my current github account is tied to my previous org (red hat). How do I (1) detach my CLA and (2) create a new CLA for an organization that previously has not commited to kubernetes ? Thanks !

I just kicked you out of the RH CLA. I'm not sure how that could have been done self service.

thanks eric :) i guess were half way there .

After you have been removed from the organization you can create a new organization at https://identity.linuxfoundation.org/node/285/organization-signup

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:

curtis.l.[email protected]
Domain imwiz.com has exceeded the max emails per hour (168/150 (112%)) allowed. Message will be reattempted later

------- This is a copy of the message, including all the headers. ------
Received: from o5.sgmail.github.com ([192.254.113.10]:45396)
by box969.bluehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.87)
(envelope-from )
id 1dGU7y-000QH7-Mz
for [email protected]; Thu, 01 Jun 2017 11:43:21 -0600
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=ia3KtOMIWMbpcYNB7BF47jscgOE=; b=wrEnOf0+m7yWRmnA
HmbxqBgRZalVLCr9ltrAzRO0Xo9B5hetAXIRGt+KoyYjST6dnSVJZf2qr2c/ywsz
ibzt+VpXLS2N/ktdMhBLy25RzMe/UZzT2Ak1rA4JVgQwI8bW+XUTk3Wf1XW2mLev
aqgwhD/qyryuCJhunLBhqxJztrI=
Received: by filter0654p1mdw1.sendgrid.net with SMTP id filter0654p1mdw1-19843-5930522A-4
2017-06-01 17:43:06.164526033 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16])
by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id 8eFn2zRFThqa_B9E8cA5dw
for dev@imwiz.com; Thu, 01 Jun 2017 17:43:06.085 +0000 (UTC)
Date: Thu, 01 Jun 2017 10:43:05 -0700
From: Eric Searcy notifications@github.com
Reply-To: kubernetes/kubernetes reply@reply.github.com
To: kubernetes/kubernetes kubernetes@noreply.github.com
Cc: Subscribed subscribed@noreply.github.com
Message-ID:
In-Reply-To:
References:
Subject: Re: [kubernetes/kubernetes] Move to the Linux Foundation (CNCF) CLA
system (#27796)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59305229e47b9_383e3fe2b5315c2c56015";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: emsearcy
X-GitHub-Recipient: falenn
X-GitHub-Reason: subscribed
List-ID: kubernetes/kubernetes
List-Archive: https://github.com/kubernetes/kubernetes
List-Post: reply@reply.github.com
List-Unsubscribe: ,
https://github.com/notifications/unsubscribe/AAq2CmYSYGSFsTnGNPIQM8XWSlg0u0-Cks5r_vgpgaJpZM4I7IQL
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: [email protected]
X-SG-EID: APO41b8ovafPb3SK9rw3vNpc43NX8G/TIzmCUdtslW4MQwNXMLF1riQs5qL7Y2+n37CaeU19Lg72gH
pHediivQ8KuR0LkwdWDe2kalBL0uG3dmE1PZ4RXmc6VDFQRVH7wlG6Wc+wEcvscrXWEuXWCfCL+wOA
x5j/wGGY22HSrKDO211vnPTM3DVM/DsqL9WZDrgs4GyV2tnQ5+HKVxrY8g==
X-Spam-Status: No, score=-2.5
X-Spam-Score: -24
X-Spam-Bar: --
X-Ham-Report: Spam detection software, running on the system "box969.bluehost.com",
has NOT identified this incoming email as spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
root@localhost for details.

Content preview: After you have been removed from the organization you can
create a new organization at https://identity.linuxfoundation.org/node/285/organization-signup
-- You are receiving this because you are subscribed to this thread. Reply
to this email directly or view it on GitHub: https://github.com/kubernetes/kubernetes/issues/27796#issuecomment-305567241
[...]

Content analysis details: (-2.5 points, 4.0 required)

pts rule name description

-0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
-2.8 RCVD_IN_MSPIKE_H2 RBL: Average reputation (+2)
[192.254.113.10 listed in wl.mailspike.net]
-0.0 SPF_PASS SPF: sender matches SPF record
1.3 HTML_IMAGE_ONLY_24 BODY: HTML: images with 2000-2400 bytes of words
0.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
domain
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid
-0.8 AWL AWL: Adjusted score from AWL reputation of From: address
X-Spam-Flag: NO

----==_mimepart_59305229e47b9_383e3fe2b5315c2c56015
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit

After you have been removed from the organization you can create a new organization at https://identity.linuxfoundation.org/node/285/organization-signup

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kubernetes/kubernetes/issues/27796#issuecomment-305567241
----==_mimepart_59305229e47b9_383e3fe2b5315c2c56015
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit

After you have been removed from the organization you can create a new organization at https://identity.linuxfoundation.org/node/285/organization-signup

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_59305229e47b9_383e3fe2b5315c2c56015--

I can not save after edit my organization, there is error You must select one or more groups for this content. Anyone could help? Thanks!

hi @supereagle your best bet is to send an email to [email protected]. (please feel free to cc me.

@wyc good job!

Is there anyway to get the agreement signing working when using the github noreply email address in commits?
See https://help.github.com/articles/about-commit-email-addresses/

That is a question for [email protected]. I believe that the email address is what is used for CLA identification though, so it's unlikely.

We are considering this (noreply email addresses) as a feature request, but we may run into issues with it as more projects start adopting DCO in CNCF (which requires an email in the Signed-Off-By signature).

I signed the CLA as documented (with the correct github & email account) and it does not work for this PR: https://github.com/kubernetes/charts/pull/1578

For case-by-case troubleshooting, please email [email protected] if you haven't already.

Due to the CNCF requirement that we use corporate email addresses as our LF recovery email, I've been locked out of my personal LF account. I've emailed helpdesk and they recommended creating a new LF account.

I have 2 Linux Foundation accounts:

• cole.[email protected] (linked with GitHub), signed as an individual contributor
• cole.[email protected] (newly created)

But:

1. I need to sign the CLA with the second address.
2. To sign the CLA, the account must be associated with a GitHub account.
3. I can't do so, because my GitHub account is already associated with my personal LF account/CLA signature.

Any suggestions?

"Ditto", almost. My GitHub account has two verified email addresses, primary [email protected] and secondary ryan.[email protected], however GitHub does not have an option to publicly display secondary email addresses. I only have one LF account, which has [email protected] as the email and is already linked against my GitHub account, and the CLA is submitted, but there appears to be no way to set this up so that my canonical.com address is signing the CLA.

Hi. I’m trying to sign up to the CNCF CLA to be able to submit code, and I’m failing to do so. This is the PR where the corresponding check fails:

https://github.com/kubernetes-incubator/external-dns/pull/376

The commits were made using my corporate mail address. I signed up at LinuxFoundation using my private Github account and associated private mail address (not the same as the corporate mail address), then changed my mail address to be identical to the corporate one. From there I signed my employer’s company up as an organization at the Linux foundation, with me (and some other employees) as a manager. The CA check still fails.

Out of desperation I then changed the mail address back to the private one and create a second, entirely new LF account with a different username and my corporate mail address as its mail address, and successfully invited and joined that user into the group. The CA check still fails.

How do I find out what’s missing? Please help.

UPDATE: Got it to work now. Thanks @BenTheElder and LF foundation support people.

Is there any particular reason this issue is still open? Didn't we move to the LF CLA system? Does this need to be renamed to reflect a scope change?

@spiffxp It would be appropriate to rename to something like "Aggregate issues with LF CLA".

FYI, the LF will soon be rolling out a rewrite of our CLAbot that will hopefully address most of the workflows that have caused problems to date. When that happens, we can start a new issue and close this one.

Renamed

I accidentally entered the wrong mail-address when signing up for individual CLA. As a result the "CNCF Individual Contributor License Agreement - Signature request" was sent to the wrong address.
I updated the mail address in the account settings meanwhile.

Is it possible to receive a new "Signature Request" to the corrected address?

@axdotl Please email [email protected] and they will take care of you.

@dankohn Thanks!

I am getting this error when trying to sign up as an individual contributor with my github:

Sorry, there is a temporary problem signing up contributors for this project. Please try again later.

@enis That's an unhelpful error message. Could you please email [email protected].

@emsearcy @alanapost could you please see if something is down.

(Also replied via helpdesk)

The cause of this issue was that GitHub supposedly returns only validated email addresses via Oauth, but for this account they supplied a malformed/obfuscated email address (without any @ sign) that was used for this account. The e-signing component hit an edge case because it wasn't tested with non-conforming email strings.

We'll apply a fix in software, with the result that the user will have to fix any malformed email addresses and then validate it via our site.

Thanks Eric,

I was able to use my "enis" account for the CLA.

Thanks for the help. We can close this.
Enis

On Tue, Nov 21, 2017 at 4:21 PM, Eric Searcy notifications@github.com
wrote:

(Also replied via helpdesk)

The cause of this issue was that GitHub supposedly returns only validated
email addresses via Oauth, but for this account they supplied a
malformed/obfuscated email address (without any @ sign) that was used for
this account. The e-signing component hit an edge case because it wasn't
tested with non-conforming email strings.

We'll apply a fix in software, with the result that the user will have to
fix any malformed email addresses and then validate it via our site.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes/issues/27796#issuecomment-346203677,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAO1MF8kE4C7uanISq6r_-vl2LdlbZdVks5s42kPgaJpZM4I7IQL
.

I can't seem to get a CNCF-CLA signed with corporate email address.

I originally tried to sign a CNCF-CLA by logging in with my github.com account, saw that the CLA had my personal email account listed, and realised that my corp. email address hadn't been added to my gh account yet.

I cancelled out of the form, went to GH and added my corporate email address, then tried to re-sign the CLA but I only see a message saying that the CLA has been sent to my email address. No CLA form has been recieved - via either my personal or corp email address.

@greglanthier Could you please email [email protected] and they'll get you sorted out.

Hello, I signed up using github account but I had not realized it was using an old email address that I no longer want to use. I still have access to the old email for the time being. I am trying to change the email address on my linux foundation profile but I get this error above a message that says I will get an email.

    An attempt to send an e-mail message failed.
    Unable to send e-mail. Contact the site administrator if the problem persists.
    An attempt to send an e-mail message failed.
    Unable to send e-mail. Contact the site administrator if the problem persists.

A confirmation email has been sent to your new email address. You must follow the link provided in that email within 24 hours in order to confirm the change to your account email address.

I am not receiving emails and I think that's because of the error message above. Any help would be appreciated.
Thanks.

Please contact [email protected] and they’ll sort it out for you.

--
Dan Kohn dan@linuxfoundation.org
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com

On Jan 8, 2018, at 10:32, Christian Roy notifications@github.com wrote:

Hello, I signed up using github account but I had not realized it was using an old email address that I no longer want to use. I still have access to the old email for the time being. I am trying to change the email address on my linux foundation profile but I get this error above a message that says I will get an email.

An attempt to send an e-mail message failed.
Unable to send e-mail. Contact the site administrator if the problem persists.
An attempt to send an e-mail message failed.
Unable to send e-mail. Contact the site administrator if the problem persists.

A confirmation email has been sent to your new email address. You must follow the link provided in that email within 24 hours in order to confirm the change to your account email address.
I am not receiving emails and I think that's because of the error message above. Any help would be appreciated.
Thanks.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

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?

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:
https://github.com/kubernetes/kubernetes/pull/60962

@technicianted Please contact [email protected] and they’ll sort it out for you.

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

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

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

/reopen

Remains a major barrier to new contributors

/remove-lifecycle rotten

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.

I've been trying to sign the CLA to proceed with my PR https://github.com/kubernetes/kubernetes/pull/72275 but I haven't received the agreement by email despite numerous tries. I have also contacted [email protected] 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.

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

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

/remove-lifecycle stale
/lifecycle frozen