-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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.
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
Relicense Bevy under dual MIT/Apache-2.0 #2373
Comments
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
1 similar comment
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I will now mention people in chunks of 50, as that is the max number of mentions per message. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
@0x22fe |
@tarkah |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
10 similar comments
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. To go a step further, you can do so for any other license you might add in the future. I think I only bumped a dependency in Cargo.toml. Makes me laugh, the idea that you would have to "reimplement" that. It would be like claiming plagiarism for the phrase, "in conclusion." |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
6 similar comments
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
1 similar comment
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
1 similar comment
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
…gine#4252) This reverts commit 08ef2f0. # Objective - bevyengine#4225 was merged without considering the licensing considerations. - It merges in code taken from https://github.com/cart/ecs_bench_suite/tree/bevy-benches/src/bevy. - We can safely assume that we do have a license to cart's contributions. However, these build upon cart/ecs_bench_suite@377e96e, for which we have no license. - This has been verified by looking in the Cargo.toml, the root folder and the readme, none of which mention a license. Additionally, the string "license" [doesn't appear](https://github.com/rust-gamedev/ecs_bench_suite/search?q=license) in the repository. - This means the code is all rights reserved. - (The author of these commits also hasn't commented in bevyengine#2373, though even if they had, it would be legally *dubious* to rely on that to license any code they ever wrote) - (Note that the latest commit on the head at https://github.com/rust-gamedev/ecs_bench_suite hasn't had a license added either.) - We are currently incorrectly claiming to be able to give an MIT/Apache 2.0 license to this code. ## Solution - Revert it
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
…gine#4252) This reverts commit 08ef2f0. # Objective - bevyengine#4225 was merged without considering the licensing considerations. - It merges in code taken from https://github.com/cart/ecs_bench_suite/tree/bevy-benches/src/bevy. - We can safely assume that we do have a license to cart's contributions. However, these build upon cart/ecs_bench_suite@377e96e, for which we have no license. - This has been verified by looking in the Cargo.toml, the root folder and the readme, none of which mention a license. Additionally, the string "license" [doesn't appear](https://github.com/rust-gamedev/ecs_bench_suite/search?q=license) in the repository. - This means the code is all rights reserved. - (The author of these commits also hasn't commented in bevyengine#2373, though even if they had, it would be legally *dubious* to rely on that to license any code they ever wrote) - (Note that the latest commit on the head at https://github.com/rust-gamedev/ecs_bench_suite hasn't had a license added either.) - We are currently incorrectly claiming to be able to give an MIT/Apache 2.0 license to this code. ## Solution - Revert it
What?
We would like to relicense Bevy under the "dual MIT / Apache-2.0 license". This allows users to select either license according to their own preferences. There are Very Good Reasons for this (see the "Why?" section below). However I can't just arbitrarily relicense open source code, despite being the maintainer / lead developer. Bevy has hundreds of contributors and they all agreed to license their contributions exclusively under our current instance of the MIT license.
If you are mentioned in this issue, we need your help to make this happen
To agree to this relicense, please read the details in this issue, then leave a comment with the following message:
If you disagree, please respond with your reasoning (just don't expect us to change course at this point). Anyone who doesn't agree to the relicense will have any Bevy contributions that qualify as "copyrightable" removed or re-implemented.
Why?
I originally chose to license Bevy exclusively under MIT for a variety of reasons:
However there were a variety of issues that have come up that make dual-licensing Bevy under both MIT and Apache-2.0 compelling:
Additionally, Bevy's current MIT license includes the
Copyright (c) 2020 Carter Anderson
line. I don't want to force Bevy users to credit me (and no one else) for the rest of time. If you agree to the relicense, you also agree to allow us to remove this copyright line crediting me.What will this look like?
After getting explicit approval from each contributor of copyrightable work
(as not all contributions qualify for copyright, due to not being a "creative
work", e.g. a typo fix), we will add the following file to our README:
We will add LICENSE-{MIT,APACHE} files containing the text of each license. We will also update the license metadata in our Cargo.toml to:
license = "MIT OR Apache-2.0"
Contributor checkoff
Contributors with "obsolete" changes (no need for approval)
Contributors with "trivial" changes that are ok to keep
Contributors with changes we reverted to unblock the relicense
The text was updated successfully, but these errors were encountered: