-
Notifications
You must be signed in to change notification settings - Fork 161
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
Provide implementation guidance for DCO/CLA #632
Comments
I am happy to be the guinea pig and help getting it set up in WebdriverIO. |
Do we have an existing suggestion for setting up DCO/CLA infrastructure? With GitHub newly introduced |
@brianwarner has experimented with some implementations of this |
Reporting back on this issue - @brianwarner has been working with the folks at the ProBot DCO project to incorporate some upstream changes that work for our use case. These are incoming! |
for context from today's meeting: there was a request from the probot/dco maintainers to have someone maintain the code that @brianwarner PR'ed in. IMO this is a reasonable request. I've asked if they'd be willing to add CODEOWNERS for these sections of code, and if so that makes it simpler to fence off the commitment. Ideally, we'd find someone from the CPC or member projects who'd be willing to take that responsibility. |
Today we learned that the Probot DCO will be shut down in 4 weeks if no one takes on ownership. dcoapp/app#162. I will connect the dots with those potentially interested in supporting this from the Linux Foundation. |
In #618 we agreed that it would be useful to provide guidance for DCO/CLA implementation and day to day use for both project maintainers and contributors.
For Project maintainers
Project maintainers need guidance to:
Contributors
The text was updated successfully, but these errors were encountered: