Skip to content

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

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.

Sign up for GitHub

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

Merged
jlanz merged 3 commits into from
Jun 10, 2026
+14 −0
Merged

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

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b698ab0
Add RE-LICENSE_NOTE.txt
jlanz May 28, 2026
8fa12e3
Update CONTRIBUTING.md
jlanz Jun 8, 2026
85359d6
clarify CLA and DCO policy for pre-transfer history
jlanz Jun 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,14 @@ TAC](https://github.com/AcademySoftwareFoundation/tac/blob/main/process/contribu
Note that if you have signed a CLA for a different ASWF or LF project, that
CLA doesn't apply here and you need to sign for this project specifically.

On April 23, 2026, stewardship of the MoonRay repositories transferred from DreamWorks
Animation to the Academy Software Foundation. Contributions made before that date were
authored either by DreamWorks Animation employees or by third-party contributors under
the DreamWorks Animation CLA process then in effect. Those historical contributions
remain part of MoonRay and are distributed under the project's [Apache 2.0
license](LICENSE). Contributions submitted on or after April 23, 2026 are subject to
the MoonRay/ASWF EasyCLA requirements described above.

### Developer Certificate of Origin (DCO)

The MoonRay project requires the use of the [Developer Certificate of Origin 1.1 (DCO)](https://developercertificate.org/), which affirms that the contribution was created by you the contributor, and that you have the rights to contribute the changes under the open source license. It is the same mechanism that the [Linux® Kernel](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n416) and many other communities use to manage code contributions. The DCO is considered one of the simplest tools for sign offs from contributors as the representations are meant to be easy to read and indicating signoff is done as a part of the commit message.
Expand All @@ -77,6 +85,12 @@ You can include this automatically when you commit a change to your local git re

[Read more about MoonRay legal and licensing concerns for contributions here](https://docs.openmoonray.org/license/).

The DCO `Signed-off-by` requirement applies to contributions submitted on or after
April 23, 2026. Historical commits made before that date may not include a
`Signed-off-by` trailer, as DCO sign-off was not part of DreamWorks Animation's
contribution process at that time. Those historical contributions were accepted under
the project's prior contribution process and remain in the repository.

## Repository Structure

MoonRay is available as a number of repositories on GitHub. The main repository is [`openmoonray`](README.md), and it [references all the other repositories](.gitmodules) required to build MoonRay as [git submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules).
Expand Down