clarify CLA and DCO policy for pre-transfer history#244
Conversation
Signed-off-by: Jon Lanz <jon.lanz@dreamworks.com>
|
Hmm, should this file be named something different, perhaps DCO_signoff.txt ? |
|
I suppose another question is should this file exist in every OpenMoonRay/ repository? ... and if so can it contain a link to this top-level file? |
|
Agreed that I wonder if we also need to add a date or commit hash to scope the range of covered commits, e.g.:
Lastly, while I like the simplicity of this approach, having a single file provide blanket coverage for all commits based on contributor names (similar to other projects' relicensing approaches), I wonder if more explicit per-commit sign-off is needed based on ASWF Contribution Guidelines and the linked Contribution Checker script:
The policy and script seems to suggest each user would need their own file in a I suppose which approach is taken, and whether or not the @jmertic , any thoughts or guidance here? |
|
Howdy - so there isn't a universal way to do this. I think what likely would make sense is to have some sort of a note in there ( in the README.md or maybe CONTRIBUTING ) that indicates the date of the switchover, as the tools will have a feature ( once I finish it up ;-) ) that will say "only look at commits after a specific date". |
Signed-off-by: Jon Lanz <jon.lanz@dreamworks.com>
|
@jmertic - is this what you had in mind? |
Signed-off-by: Jon Lanz <jon.lanz@dreamworks.com>
|
Yep - this looks good! Thanks! |
Signed-off-by: Jon Lanz jon.lanz@dreamworks.com