You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is a CLA required for contributions, or is signing-off on commits sufficient?
I read the CONTRIBUTING.md document and it contains links to both the individual and corporate CLAs but they seem to be dead links. The only working link was the link to the Linux Foundation CLA template, but it's a template and not the specific one for OpenEXR.
Is there a link available for the official CLAs?
The text was updated successfully, but these errors were encountered:
Oops, we're in the process of setting up a new automated CLA system, and it
looks like some files moved. We're working out the proper thing to do in
the interim, I'll report back shortly.
On Mon, Oct 14, 2019 at 11:15 AM David Aguilar ***@***.***> wrote:
Is a CLA required for contributions, or is signing-off on commits
sufficient?
I read the CONTRIBUTING.md document and it contains links to both the
individual and corporate CLAs but they seem to be dead links. The only
working link was the link to the Linux Foundation CLA template, but it's a
template and not the specific one for OpenEXR.
Is there a link available for the official CLAs?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#584>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFC3DGKB4DAP7XWZN2UYNSDQOSZKNANCNFSM4JASNPJQ>
.
--
Cary Phillips | R&D Supervisor | ILM | San Francisco
Is a CLA required for contributions, or is signing-off on commits sufficient?
I read the CONTRIBUTING.md document and it contains links to both the individual and corporate CLAs but they seem to be dead links. The only working link was the link to the Linux Foundation CLA template, but it's a template and not the specific one for OpenEXR.
Is there a link available for the official CLAs?
The text was updated successfully, but these errors were encountered: