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

Setup accepting cncf cla/DCO before PR can be merged #30

Open
linsun opened this issue Dec 6, 2024 · 15 comments
Open

Setup accepting cncf cla/DCO before PR can be merged #30

linsun opened this issue Dec 6, 2024 · 15 comments

Comments

@linsun
Copy link
Contributor

linsun commented Dec 6, 2024

No description provided.

@ilrudie
Copy link
Contributor

ilrudie commented Dec 9, 2024

Should I try to request access to be able to set this up? It doesn't seem like I have it right now.

@linsun
Copy link
Contributor Author

linsun commented Dec 9, 2024

Yes please :) Thanks!

@ilrudie
Copy link
Contributor

ilrudie commented Dec 9, 2024

Opened a request. We'll see what they say.

@linsun
Copy link
Contributor Author

linsun commented Dec 16, 2024

Looks like DCO is also acceptable and used by cncf/toc repo as well, along with linkerd2.

@linsun linsun changed the title Setup accepting cncf cla before PR can be merged Setup accepting cncf cla/DCO before PR can be merged Dec 16, 2024
@ilrudie
Copy link
Contributor

ilrudie commented Dec 17, 2024

I added the CNCF/DCO-2 app to our org and set it up to check the community repo. https://github.com/k8sgateway/community/pull/43/checks?check_run_id=34563443814 is an example.

@ilrudie
Copy link
Contributor

ilrudie commented Dec 18, 2024

#37 now includes documenting the DCO requirements

@linsun
Copy link
Contributor Author

linsun commented Dec 19, 2024

Yay, awesome Ian!! Thanks!

@linsun linsun closed this as completed Dec 19, 2024
@ilrudie
Copy link
Contributor

ilrudie commented Dec 19, 2024

Should we wait until this is enabled on kgw/kgw to close? Right now it's only on kgw/community

@linsun
Copy link
Contributor Author

linsun commented Dec 19, 2024

Ah, got it, reopen and closing it when you are ready :)

@linsun linsun reopened this Dec 19, 2024
@ilrudie
Copy link
Contributor

ilrudie commented Jan 10, 2025

Need to revisit whether this is blocking acceptance into the CNCF sandbox. The DCO experience was bad for developers.

cc @linsun

@craigbox
Copy link
Contributor

It will not block acceptance but it's on the list of things you do to onboard to set up one of the other, with DCO preferred.

TBH I hear @ilrudie but I think DCO is much lower effort if you're required to get a corporate CLA signed.

@ilrudie
Copy link
Contributor

ilrudie commented Feb 13, 2025

We can adopt whichever the community prefers. I long ago developed a personal habit of cryptographically signing as well as "signing off on" every commit I make so this is a moot point for me.

Since other folks found it to be bad, and we were generally sympathetic to "feels bad even if good for project", I backed DCO out to ease the pain pending further discussion.

@craigbox
Copy link
Contributor

we need to tell people to put the following in .git/hooks/commit-msg (one time)

#!/bin/sh
SIGNATURE="Signed-off-by: `git config --global --get user.name` <`git config --global --get user.email`>"
grep -qs "^${SIGNATURE}" "$1" || echo "\n${SIGNATURE}" >> "$1"

@ilrudie
Copy link
Contributor

ilrudie commented Feb 13, 2025

Yeah, we can make some recommendations to ease the pain. We also probably need to document "Oops, 10 commits with no signoffs... now what?" It's gunna happen to most fly by contribs I expect and instead of "go sign this web form and ask someone to rerun the CLA test" you're gunna get into some git gymnastics and a force push.

@craigbox
Copy link
Contributor

Feel free to lift https://github.com/kubescape/project-governance/blob/main/CONTRIBUTING.md#sign-your-commits

(the linked src-d guide is CC-BY-SA-4.0 licensed and unmaintained; we could inherit that too.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants