-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
Should I try to request access to be able to set this up? It doesn't seem like I have it right now. |
Yes please :) Thanks! |
Opened a request. We'll see what they say. |
Looks like DCO is also acceptable and used by cncf/toc repo as well, along with linkerd2. |
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. |
#37 now includes documenting the DCO requirements |
Yay, awesome Ian!! Thanks! |
Should we wait until this is enabled on kgw/kgw to close? Right now it's only on kgw/community |
Ah, got it, reopen and closing it when you are ready :) |
Need to revisit whether this is blocking acceptance into the CNCF sandbox. The DCO experience was bad for developers. cc @linsun |
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. |
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. |
we need to tell people to put the following in
|
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. |
Feel free to lift https://github.com/kubescape/project-governance/blob/main/CONTRIBUTING.md#sign-your-commits (the linked |
No description provided.
The text was updated successfully, but these errors were encountered: