Open baentsch opened 5 months ago
Seconding this as a priority; I've recently had to ask outside contributors to fix DCO in two different PRs that were otherwise ready to merge.
:-( This is precisely what would be good to avoid: process getting in the way of progress.
FWIW, I will not implement this as I a) think the current DCO process is a meaningless "checkbox-filling exercise" (who really understands what -s
implies?) that I don't stand behind and b) am a big believer in the concept that the person adding something should be the first to resolve problems their change introduces (such as to experience and resolve user problems in a scalable manner, e.g., automate or document).
Perhaps this would be a useful document to link to or build on to explain how to work with DCO: https://github.com/src-d/guide/blob/master/developer-community/fix-DCO.md
As per https://github.com/open-quantum-safe/liboqs/pull/1708#issuecomment-2069210942