search

AcademySoftwareFoundation / openvdb

OpenVDB - Sparse volume data structure and tools
http://www.openvdb.org/
Mozilla Public License 2.0
2.62k stars 647 forks source link

Change MPL License to Apache 2.0 #1858

Open dgovil opened 2 months ago

dgovil commented 2 months ago

This PR changes the MPL 2.0 license to Apache 2.0 as discussed. However, we should wait to merge this in till the following things are completed:

I'm putting this PR up now so that I can get my own CLA squared away , and in case people want to see if I missed anything since it's a very large PR by file count.

The new CLA links: ICLA - https://cla-signature-files-prod.s3.amazonaws.com/contract-group/28a0d3d8-b869-44e0-a4f4-06b50c49822f/template/icla-2024-09-04T09-58-58Z.pdf CCLA - https://cla-signature-files-prod.s3.amazonaws.com/contract-group/28a0d3d8-b869-44e0-a4f4-06b50c49822f/template/ccla-2024-09-04T09-58-59Z.pdf

The link to pre-sign the CCLA https://organization.lfx.linuxfoundation.org/foundation/a092M00001If9vIQAR/project/lfPSOFZmSa0ojY6q7v/cla

linux-foundation-easycla[bot] commented 2 months ago

CLA Signed

The committers listed above are authorized under a signed CLA.

kmuseth commented 2 months ago

I believe we have sign-off from everyone now. @dgovil I guess this means we are ready to proceed? Does this PR include the latest version of NanoVDB that was merged into master recently?

dgovil commented 2 months ago

@kmuseth oh great news. Yes this should have all your nano VDB changes.

I can do another pass after I'm back on the 5th of August but everything should be done here afaik.

Cc @jmertic who can change the CLA once this PR is merged in.

I can do a follow up PR once I'm back in case there's anything I missed, but I don't believe there are any new files since then.

jmertic commented 2 months ago

I can make the CLA and Technical Charter changes whenever everyone is ready, provided the TSC has approved both. Let me know.

dgovil commented 2 months ago

Awesome. In that case, I think either order makes sense.

If the TSC wants to merge this PR, and then change the CLA after, you don't need to wait for my return for anything.

Otherwise if the CLA changes first, I'll have to re-sign the CLA which I'll only be able to do on the 5th. In that case, I can also update the CLA copies in the repo with the correct language as well.

Either way works. I'll do any follow up work as needed when I return.

Thank you all so much!

jmertic commented 2 months ago

@kmuseth - As TSC Chair, it's your call. Let me know.

dgovil commented 1 month ago

Looks like the meeting didn't happen this week. @kmuseth I just checked and this PR is up to date with all the latest commits that have been merged. So whenever you feel comfortable merging this the steps would be:

  1. This PR gets merged
  2. John updates the CLA on the Linux Foundation
  3. Either John or myself update the CLA documents in this repo.

Then that should basically be it :-)

kmuseth commented 3 weeks ago

it looks like the DCO signoff failed. I cannot merge before it's fixed

jmertic commented 3 weeks ago

We need to not merge this in until we are ready to switch over the CLA. We should be read to have the pre-signing tomorrow or Thursday at the latest. Thanks!

dgovil commented 3 weeks ago

I rebased on top of latest from master. I also fixed the DCO issue, and after talking to John, replaced the markdown copies of the CLA texts with links to the official PDFs.

The PR should be ready to merge whenever you feel comfortable with the companies signing off on the new CLA for the link John sent out.

dgovil commented 5 days ago

@danrbailey I've now added the links to the CLA text (both ICLA and CCLA) to the PR description. I've also added the link to pre-sign the CCLA as well.