-
Notifications
You must be signed in to change notification settings - Fork 399
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
Adopt the DCO over a CLA. #5
Comments
We use https://github.com/cla-assistant/cla-assistant now, you can have a try. |
TiKV has now adopted the DCO! I think we can move forward with this. |
No, now raft is still in PingCAP, we need to use CLA. |
😢 Okay. |
Closed as DCO is used. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In an effort to reduce friction in accepting community contributions, I would propose in experimenting with using the Developer's Certificate of Origin over a Contributor License Agreement for this particular repository.
The DCO is as follows:
As you can see this is quite simple and does not include many scary legal terms. We can have this done via a signed-off-by.
We can use the available integration to enforce this easily.
Rationale from Other Companies
Alternatives
In lieu of this, we could simply not require any. Or keep using a CLA. All options are valid.
The text was updated successfully, but these errors were encountered: