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.

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

Add instructions on how to setup the CNCF CLA check #1649

Merged
merged 1 commit into from
Jan 22, 2018

Conversation

spiffxp
Copy link
Member

@spiffxp spiffxp commented Jan 22, 2018

This is pretty much rote copy-paste from a google doc I got from @foxish.

I followed these instructions as part of kubernetes-retired/testing_frameworks#3

/cc @mattfarina @foxish @idvoretskyi
since I mentioned this to you

FYI @kubernetes/sig-testing-pr-reviews
This could stand to be streamlined, any suggestions?

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 22, 2018
@idvoretskyi
Copy link
Member

/lgtm

@spiffxp thanks for collecting this!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 22, 2018
@spiffxp
Copy link
Member Author

spiffxp commented Jan 22, 2018

/hold
for comment

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 22, 2018
@foxish
Copy link
Contributor

foxish commented Jan 22, 2018

LGTM

@cblecker
Copy link
Member

@spiffxp is the root of the repo the best place for this?

@spiffxp
Copy link
Member Author

spiffxp commented Jan 22, 2018

@cblecker agreed, in general there's a lot of stuff lurking in root that seems like it should go elsewhere but... naming is hard for me today, so I'm very open to suggestion

ie: burying in a sig/wg/committee folder seemed wrong, contributors/devel didn't seem right either, and I didn't want to shuffle around a whole bunch of docs into a new folder as part of this pr

@cblecker
Copy link
Member

@spiffxp Makes sense. Then yeah, I'm okay with this for now. I'll think on this, as yeah, there are other docs like sysadmin.md that should kind of be grouped together under like.. community administration

Copy link
Contributor

@mattfarina mattfarina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great. Thanks for putting it together. I just have the one quick question. Otherwise it LGTM

- `comment=no` specifies that our system should not post help comments into the pull request (since the Kubernetes mungebot does this).
- `target=https://identity.linuxfoundation.org/projects/cncf` specifies what will be used for the "Details" link in Github for this status check.
- Content Type: application/json
- Secret: Please contact one of [@idvoretskyi](https://github.com/idvoretskyi), [@foxish](https://github.com/foxish), or [@spiffxp](https://github.com/spiffxp)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I previously spoke with Ihor he said the POCs for this were himself and Chris Aniszczyk. Is this an updated list from that?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mattfarina That's fine, I'm handling the questions of CLA for Kubernetes on behalf of CNCF.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, it was more that I know foxish and I have the secret (he's who ihor referred me to when I asked), and wanted to avoid a bottleneck here, but upon further thought it's probably wiser to keep that secret with them.

@k8s-github-robot
Copy link

/lgtm cancel //PR changed after LGTM, removing LGTM. @idvoretskyi @spiffxp

@k8s-github-robot k8s-github-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 22, 2018
@spiffxp
Copy link
Member Author

spiffxp commented Jan 22, 2018

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 22, 2018
@idvoretskyi
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 22, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: idvoretskyi, spiffxp

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:
  • OWNERS [idvoretskyi,spiffxp]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 58b9ba2 into kubernetes:master Jan 22, 2018
@spiffxp spiffxp deleted the setting-up-the-cla-check branch January 22, 2018 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants