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

Provide implementation guidance for DCO/CLA #632

Open
tobie opened this issue Sep 1, 2020 · 6 comments
Open

Provide implementation guidance for DCO/CLA #632

tobie opened this issue Sep 1, 2020 · 6 comments
Assignees

Comments

@tobie
Copy link
Contributor

tobie commented Sep 1, 2020

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:

  • Set up DCO/CLA infra.
  • Document DCO/CLA requirements for contributors.
  • Handle common issues with DCO/CLA, e.g. for DCO:
    • What happens when there are multiple authors?
    • What happens when commits are squashed?
    • Can I sign off for someone else when I merge a commit?
    • What if I'm batch-merging commits made with GitHub's "insert a suggestion" feature?
    • Is a Sign-off-by in the body of the pull request good enough?

Contributors

  • Understand what they have to do to contribute IP.
  • Understand when they need employer agreement to do so.
  • Solve common problems they might bump into.
@christian-bromann
Copy link
Member

I am happy to be the guinea pig and help getting it set up in WebdriverIO.

@mmarchini
Copy link

Set up DCO/CLA infra.

Do we have an existing suggestion for setting up DCO/CLA infrastructure? With GitHub newly introduced pull_request_target event for Actions, it's likely that we can implement it solely as an Action.

@MylesBorins
Copy link
Contributor

@brianwarner has experimented with some implementations of this

@jorydotcom
Copy link
Contributor

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!

@bnb
Copy link
Member

bnb commented Aug 17, 2021

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.

@rginn
Copy link

rginn commented Oct 12, 2021

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.

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

9 participants