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.

Sign up for GitHub

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

Jump to bottom

Easy CLA vs. DCO #63

Closed
andorsk opened this issue Nov 10, 2022 · 3 comments
Closed

Easy CLA vs. DCO #63

andorsk opened this issue Nov 10, 2022 · 3 comments
Assignees
@andorsk
Labels
priority: high It is important for the group to resolve this issue soon. type: admin This issue requires an action by an admin.
Milestone
PR-1

Comments

@andorsk
Copy link
Contributor

andorsk commented Nov 10, 2022

Comment on TechArch about investigating EasyCLA allowance to turn off DCO.
@andorsk andorsk self-assigned this Nov 10, 2022
@andorsk andorsk added the type: admin This issue requires an action by an admin. label Nov 10, 2022
@andorsk andorsk added this to the PR-1 milestone Nov 10, 2022
@andorsk
Copy link
Contributor Author

andorsk commented Nov 10, 2022 •
edited
Loading

I haven't used CLA before tbh, but from what I've seen, it should be able to replace DCO. I could pretend I have a well informed opinion, but really I read through the issue below:

electron/governance#441

Which are other's people experiences with the tradeoffs. So the answer is yes, we can turn off DCO w/ CLA, but should understand that CLA imposes a tradeoff.

From my personal experience, even with open source work, I haven't seen a lot of DCO/CLA process involved. When it's DCO, I just automatically turn on signing on the repo locally, but that's not necessarily easy for others to do.

I can say DIF doesn't use it, and other projects I've contributed to don't generally use it either, but I'm sure there are quite a few projects that do use it that I just haven't been a part of.

I'd specifically point to this comment: electron/governance#441 (comment) which is quite interesting.

@andorsk andorsk added the priority: high It is important for the group to resolve this issue soon. label Nov 10, 2022
@andorsk
Copy link
Contributor Author

andorsk commented Dec 1, 2022

I think this can be closed.

@talltree
Copy link
Collaborator

talltree commented Feb 5, 2023

Agreed. Closing this issue.

@talltree talltree closed this as completed Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andorsk andorsk

Labels
priority: high It is important for the group to resolve this issue soon. type: admin This issue requires an action by an admin.
Projects
None yet
Milestone
PR-1
Development

No branches or pull requests
2 participants
@talltree @andorsk