Skip to content

clarify CLA and DCO policy for pre-transfer history#244

Merged
jlanz merged 3 commits into
OpenMoonRay:mainfrom
dreamworksanimation:add-relicense-file
Jun 10, 2026
Merged

clarify CLA and DCO policy for pre-transfer history#244
jlanz merged 3 commits into
OpenMoonRay:mainfrom
dreamworksanimation:add-relicense-file

Conversation

@jlanz

@jlanz jlanz commented May 28, 2026

Copy link
Copy Markdown
Contributor

Signed-off-by: Jon Lanz jon.lanz@dreamworks.com

Signed-off-by: Jon Lanz <jon.lanz@dreamworks.com>
@jlanz

jlanz commented May 29, 2026

Copy link
Copy Markdown
Contributor Author

Hmm, should this file be named something different, perhaps DCO_signoff.txt ?

@jlanz

jlanz commented May 29, 2026

Copy link
Copy Markdown
Contributor Author

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?

@jlanz jlanz requested a review from a team May 29, 2026 16:59
@matthewlow-dwa

Copy link
Copy Markdown
Contributor

Agreed that ‎RE-LICENSE_NOTE.txt is perhaps a misleading filename as it suggests something related to the Apache 2.0 license, which is not changing. DCO_signoff.txt seems fine.

I wonder if we also need to add a date or commit hash to scope the range of covered commits, e.g.:

The following copyright holders agree that all of their contributions originally submitted to this project prior to May 29th, 2026 (commit hash: 1234asdf) are submitted pursuant to ...

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 dco-signoffs directory, explicitly enumerating each covered commit by hash and message.

I suppose which approach is taken, and whether or not the contrib_check script is used, will help inform if this needs to be done per-repo or can be aggregated into just here in the superproject.

@jmertic , any thoughts or guidance here?

@jlanz

jlanz commented Jun 1, 2026

Copy link
Copy Markdown
Contributor Author

Actually, I found this, which seems to imply that the file should be named past_commits.txt.

I also found this, but I'm still reading up and haven't tried running it.

@jmertic

jmertic commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

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>
@jlanz

jlanz commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

@jmertic - is this what you had in mind?

Comment thread CONTRIBUTING.md Outdated
Signed-off-by: Jon Lanz <jon.lanz@dreamworks.com>
@jmertic

jmertic commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Yep - this looks good! Thanks!

@jlanz jlanz changed the title Add RE-LICENSE_NOTE.txt clarify CLA and DCO policy for pre-transfer history Jun 9, 2026
@jlanz jlanz merged commit 5e31f9d into OpenMoonRay:main Jun 10, 2026
2 checks passed
@jlanz jlanz deleted the add-relicense-file branch June 10, 2026 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants