admin: Change open source license to Apache 2.0 #3899
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By majority vote of the TSC, we are changing OpenImageIO's main incoming/outgoing open source license from BSD-3-Clause to Apache-2.0. New code submitted from July 1, 2023 will be contributed under the Apache 2.0 license. Old code submitted prior to July 1 2023 is under the original BSD 3-clause license, unless relicensed per the process described in the new RELICENSING.md file. We hope to get the vast majority of the code base relicensed quickly and we will document which set of files contain a mixture of licenses. Instructions to everybody reading this: * If you are contributing code under the authorization of an employer, please let them know we are changing to Apache 2.0 and make sure that you are authorized to make all future contributions to under that license. * If you made prior contributions to OpenImageIO over the years and are willing to relicense your code under the Apache 2.0 license, please submit a PR adding your name to the list in RELICENSING.md. If you were working for a company that might own your IP output at the time you made those contributions, please also ask somebody there (who has the authority to do so) to submit a PR adding the company name as well, indicating that they are re-submitting all of the old contributions under the new license. Signed-off-by: Larry Gritz <[email protected]>
|
As far as package maintainers, I assume we'll need to update the license? |
|
@hobbes1069 On your end? Yes. It's a little complicated, it will be a mix of Apache 2.0 and BSD, but we hope very quickly to get to the point where the vast majority is Apache 2.0. At that point, we'll consider the project overall to be Apache 2.0, but with a dwindling amount of old code still being BSD (not unlike how there are a few isolated bits and pieces now that were imported from other projects with different, but compatible, licenses). I will probably merge this PR and the subsequent changes in license notices only in master, since we're so close to a big release anyway. So I don't think you'll need to worry on the packaging end about the change for packaging until the 2.5 series is released in ~September. |
|
I picked July 1 arbitrarily (but also, kind of a round number as the half-way date of the year) for the date that I will merge this and we'll officially switch to new code coming in being Apache 2.0. |
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Jul 9, 2023
…ation#3899) By majority vote of the TSC, we are changing OpenImageIO's main incoming/outgoing open source license from BSD-3-Clause to Apache-2.0. New code submitted from July 1, 2023 will be contributed under the Apache 2.0 license. Old code submitted prior to July 1 2023 is under the original BSD 3-clause license, unless relicensed per the process described in the new RELICENSING.md file. We hope to get the vast majority of the code base relicensed quickly and we will document which set of files contain a mixture of licenses. Instructions to everybody reading this: * If you are contributing code under the authorization of an employer, please let them know we are changing to Apache 2.0 and make sure that you are authorized to make all future contributions to under that license. * If you made prior contributions to OpenImageIO over the years and are willing to relicense your code under the Apache 2.0 license, please submit a PR adding your name to the list in RELICENSING.md. If you were working for a company that might own your IP output at the time you made those contributions, please also ask somebody there (who has the authority to do so) to submit a PR adding the company name as well, indicating that they are re-submitting all of the old contributions under the new license. Signed-off-by: Larry Gritz <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By majority vote of the TSC, we are changing OpenImageIO's main incoming/outgoing open source license from BSD-3-Clause to Apache-2.0. New code submitted from July 1, 2023 will be contributed under the Apache 2.0 license.
Old code submitted prior to July 1 2023 is under the original BSD 3-clause license, unless relicensed per the process described in the new RELICENSING.md file. We hope to get the vast majority of the code base relicensed quickly and we will document which set of files contain a mixture of licenses.
Instructions to everybody reading this:
If you are contributing code under the authorization of an employer, please let them know we are changing to Apache 2.0 and make sure that you are authorized to make all future contributions to under that license.
If you made prior contributions to OpenImageIO over the years and are willing to relicense your code under the Apache 2.0 license, please submit a PR adding your name to the list in RELICENSING.md. If you were working for a company that might own your IP output at the time you made those contributions, please also ask somebody there (who has the authority to do so) to submit a PR adding the company name as well, indicating that they are re-submitting all of the old contributions under the new license.