Cross-project-council: Provide implementation guidance for DCO/CLA

[tobie]

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]

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

[mmarchini]

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]

@brianwarner has experimented with some implementations of this

[jorydotcom]

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!