minor spelling fix

[micah]

Fix incorrect use of past tense.

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: helpdesk@rt.linuxfoundation.org

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. I understand the commands that are listed here.

[micah]

Sorry, but the CLA process is way too annoying:

1. I tried to register a LF account. This required me to do cloudflare captchas 6 times, only to find out that the account name was taken. Maybe it is mine?

2. I tried to reset the password for that account, using my email address. This required another round of cloudflare captchas, this time I got to do it 7 times, seriously guys, I'm not a robot, and those are all the cars and streetsigns...

3. turned out the email address did not match the account, so I have to create an account. So I do that, and guess what! Another cloudflare captcha, I lost track of how many times I proved I was not a robot and clicked on shop signs. Does the pole count for a street sign?

4. i got the confirmation link, I clicked on it. After about 3 minutes, I got a blank page... oook. I tried to go to the link again, and it said that I cannot re-use the confirmation link.

5. went to try and login, my password did not work, even though I know it is right.

6. reset password, cloudflare captcha time, yay.

7. Finally get in, go and dig up the CLA requirements again, click on it...

8. I need to link a 'social networking account' to continue. I dont use social networking, but ok... there is a github option. I pick that, it connects, and I authorize it.

9. ok, now you need to send me the CLA by email, so I can sign it. Weirdly, there is a form on the page that asks me to put a Subject and content of an email. So I fill that out, and hit submit, and it tells me:

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

10. I break my keyboard in frustration.

11. I buy a new keyboard.

12. I find that I actually DID get the email! Ok... so I click the link, and I'm brought to the page for the CLA form, I start reading... I need to put my actual physical address into this thing? You have to be kidding me, and a phone number? What is this insanity I just was trying to help you fix a typo.

13. No, nope, no, no way...

14. I write this issue, please lower the bar for contributions, because honestly...I was trying to be a good opensource citizen and help you with some trivial fixes I found along the way, and I'm hit with this epic annoying legal process that requires all kinds of personally identifying information, seriously alienating proofs that I'm not a robot, and total and complete discouragement from helping out.

[woopstar]

I'm sure you manage :)

[dkg]

The process described by @micah above is clearly unhinged and counterproductive. the patch proposed is a one-octet patch, which does not require copyright assignment under any interpretation of copyright i've ever heard of.

even if it did require copyright assignment, the level of intrusiveness described in the process above is far more than it ought to be. The irony that an account explicitly named as a robot is forcing a human to jump through all of these hoops to not be assumed to be a robot is pretty rich. If @micah was actually a robot that did grammar/spellchecking like the real @micah does, then it wouldn't need to assign any copyright at all, right? Why are we making life harder for humans to contribute to free software?

@woopstar -- yes, @micah (and some of the rest of us) can indeed "manage" -- but it costs us time that we could otherwise spend in more fruitful pursuits. And you don't even know how many people who decide "managing" isn't worth the bother and just go do something else. These hurdles are counterproductive to the community. Just accept his patch here.

And while you're at it, please improve the @k8s-ci-robot to not block trivial patches with this kind of nonsense. We need @micah spending his time actually being a good f/loss citizen, not "managing" all the grief described above.

[mattymo]

@dkg I appreciate your support for the situation, but all CNCF projects require that every contributor has signed the CLA. I can't change the policy and I encourage you folks to write to the CNCF directly to suggest improvements to the process. I managed okay, but I guess I'm just lucky.

[rsmitty]

Guys, we don't manage the CLA process. It's something that's required by the CNCF for every project in the incubator. We also can't merge any changes if the agreement isn't signed by the user providing the code. If you have issues with the agreement, please direct that to the proper folks.

[micah]

Matthew Mosesohn <notifications@github.com> writes:

@dkg I appreciate your support for the situation, but all CNCF projects require that every contributor has signed the CLA. I can't change the policy and I encourage you folks to write to the CNCF directly to suggest improvements to the process. I managed okay, but I guess I'm just lucky.

Rather than "manage" to divulge all this personal information unnecessarily, I'll just make issues for anything I find, and leave it to someone else who wants to give their phone number and address in order to fix a spelling mistake.

[dkg]

@mattymo and @rsmitty : you both suggest "writing to the CNCF" or "direct that to the proper folks", but those instructions are not clear. Presumably you know who "the proper folks" are, or what the address of the CNCF is (i don't even know what CNCF stands for without looking it up, i'm a bystander here).

Perhaps you could point out that their policy is driving away useful (if small) contributions and making their incubated project look bad?

[micah]

Spencer Smith <notifications@github.com> writes:

Guys, we don't manage the CLA process. It's something that's required by the CNCF for every project in the incubator. We also can't merge *any* changes if the agreement isn't signed by the user doing the merge. If you have issues with the agreement, please direct that to the proper folks.

Actually... the CNCF charter (https://www.cncf.io/about/charter/) says that you *do* get to decide if you want to have this CLA process, and it is *not* required by the CNCF: 11. IP Policy ... (b) Each project shall determine whether it will require use of an approved CNCF CLA. For projects that select to use a CLA, all code contributors will undertake the obligations set forth in the Apache contributor license agreement(s), altered only as necessary to identify CNCF as the recipient of the contributions, and which shall be approved by the Governance Board. See CNCF Contributor License Agreements available at https://github.com/cncf/cla. The process for managing contributions in accordance with this policy shall be subject to Governance Board approval.