Relicense Bevy under dual MIT/Apache-2.0

Question

Relicense Bevy under dual MIT/Apache-2.0

cart opened this issue 3 years ago · comments

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:

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

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:

People and companies generally know and trust the MIT license more than any other license. Apache 2.0 is less known and trusted.
It is short and easy to understand
Many people aren't familiar with the "multiple license options ... choose your favorite" approach. I didn't want to scare people away unnecessarily.
Other open source engines like Godot have had a lot of success with MIT-only licensing

However there were a variety of issues that have come up that make dual-licensing Bevy under both MIT and Apache-2.0 compelling:

The MIT license (arguably) requires binaries to reproduce countless copies of the same license boilerplate for every MIT library in use. MIT-only engines like Godot have complicated license compliance rules as a result
The Apache-2.0 license has protections from patent trolls and an explicit contribution licensing clause.
The Rust ecosystem is largely Apache-2.0. Being available under that license is good for interoperation and opens the doors to upstreaming Bevy code into other projects (Rust, the async ecosystem, etc).
The Apache license is incompatible with GPLv2, but MIT is compatible.

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:

### License

Licensed under either of

 * Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
 * MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)

at your option.

### Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
additional terms or conditions.

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)

adekau
ColonisationCaptain
temhotaokeaha

Contributors with "trivial" changes that are ok to keep

follower
HyperLightKitsune
liufuyang
Raymond26
themilkybit
walterpie
EthanYidong

Contributors with changes we reverted to unblock the relicense

TomBebb

Zicklag · Answer 1 · Tue Jun 22 2021 11:10:22 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Yoh Deadfall · Answer 2 · Tue Jun 22 2021 11:14:07 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Carter Anderson · Answer 3 · Tue Jun 22 2021 11:17:16 GMT+0800 (China Standard Time)

I will now mention people in chunks of 50, as that is the max number of mentions per message.

James R · Answer 4 · Tue Jun 22 2021 11:17:18 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Carter Anderson · Answer 5 · Tue Jun 22 2021 11:17:28 GMT+0800 (China Standard Time)

@0x22fe
@8bit-pudding
@aclysma
@adam-bates
@adamaq01
@adekau
@aevyrie
@ak-1
@akiross
@alec-deason
@alexb910
@alexschrod
@alice-i-cecile
@AlisCode
@aloucks
@amberkowalski
@AmionSky
@anchpop
@andreheringer
@andrewhickman
@AngelicosPhosphoros
@AngelOnFira
@Archina
@ashneverdawn
@BafDyce
@bgourlie
@BimDav
@bitshifter
@bjorn3
@blaind
@blamelessgames
@blunted2night
@Bobox214
@Boiethios
@bonsairobo
@BoxyUwU
@Byteron
@CAD97
@CaelumLaron
@caelunshun
@cart
@CGMossa
@CleanCut
@ColdIce1605
@ColonisationCaptain
@Cupnfish
@dallenng
@Dash-L
@Davier
@dburrows0

Carter Anderson · Answer 6 · Tue Jun 22 2021 11:17:51 GMT+0800 (China Standard Time)

@dependabot[bot]
@deprilula28
@DGriffin91
@Dispersia
@DivineGod
@Divoolej
@DJMcNab
@e00E
@easynam
@elartista
@eliaspekkala
@enfipy
@EthanYidong
@figsoda
@fintelia
@Fishrock123
@FlyingRatBull
@follower
@forbjok
@frewsxcv
@freylint
@Frizi
@FSMaxB
@FuriouZz
@GabLotus
@gcoakes
@gfreezy
@Git0Shuai
@giusdp
@GrantMoyer
@Gregoor
@Grindv1k
@guimcaballero
@Halfwhit
@huhlig
@hymm
@HyperLightKitsune
@ifletsomeclaire
@iMplode-nZ
@Incipium
@iwikal
@Ixentus
@J-F-Liu
@jak6jak
@jakerr
@jakobhellermann
@jamadazi
@Jbat1Jumper
@JCapucho
@jcornaz

Carter Anderson · Answer 7 · Tue Jun 22 2021 11:18:09 GMT+0800 (China Standard Time)

@Jerald
@jesseviikari
@jihiggins
@jleflang
@jngbsn
@joejoepie
@JohnDoneth
@Josh015
@joshuajbouw
@julhe
@kaflu
@karroffel
@kedodrill
@kokounet
@Kurble
@lachlansneff
@lambdagolem
@lassade
@lberrymage
@lee-orr
@liufuyang
@logannc
@Lowentwickler
@lukors
@Lythenas
@M2WZ
@marcusbuffett
@MarekLg
@marius851000
@MatteoGgl
@maxwellodri
@mccludav
@memoryruins
@mfrancis107
@MGlolenstine
@MichaelHills
@MilanVasko
@MinerSebas
@mjhostet
@mkhan45
@mnmaita
@mockersf
@Moxinilian
@MrEmanuel
@mrk-its
@msklywenn
@mtsr
@multun
@mvlabat
@naithar

Carter Anderson · Answer 8 · Tue Jun 22 2021 11:18:23 GMT+0800 (China Standard Time)

@NathanSWard
@navaati
@ncallaway
@ndarilek
@Neo-Zhixing
@nic96
@NiklasEi
@Nilirad
@no1hitjam
@nside
@ocornoc
@Olaren15
@OptimisticPeach
@payload
@Philipp-M
@Plecra
@PrototypeNM1
@r00ster91
@Ratysz
@Raymond26
@RedlineTriad
@refnil
@reidbhuntley
@Restioson
@RichoDemus
@rmsc
@rmsthebest
@RobDavenport
@robertwayne
@rod-salazar
@rparrett
@ryanleecode
@sapir
@saveriomiroddi
@sburris0
@schell
@sdfgeoff
@ShadowMitia
@simensgreen
@simlay
@simpuid
@SmiteWindows
@smokku
@StarArawn
@stefee
@superdump
@svents
@sY9sE33
@szunami
@tangmi

Carter Anderson · Answer 9 · Tue Jun 22 2021 11:18:35 GMT+0800 (China Standard Time)

@tarkah
@TehPers
@Telzhaak
@termhn
@the-notable
@thebluefish
@themilkybit
@TheNeikos
@TheRawMeatball
@thirdsgames
@Tiagojdferreira
@tigregalis
@TomBebb
@Toniman20
@toothbrush7777777
@TotalKrill
@tristanpemble
@trolleyman
@turboMaCk
@undinococo
@verzuz
@Veykril
@VitalyAnkh
@w1th0utnam3
@W4RH4WK
@walterpie
@Waridley
@Weibye-Breach
@wilk10
@will-hart
@willcrichton
@WilliamTCarroll
@woubuc
@wyhaya
@Xavientois
@YohDeadfall
@yrns
@zaszi
@zgotsch
@zicklag
@Zooce

Duncan · Answer 10 · Tue Jun 22 2021 11:18:57 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Adam Bates · Answer 11 · Tue Jun 22 2021 11:19:12 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Corey Farwell · Answer 12 · Tue Jun 22 2021 11:19:56 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Patrik Buhring · Answer 13 · Tue Jun 22 2021 11:20:25 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

wyhaya · Answer 14 · Tue Jun 22 2021 11:20:29 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Aevyrie · Answer 15 · Tue Jun 22 2021 11:20:43 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Rob · Answer 16 · Tue Jun 22 2021 11:20:48 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Alice Cecile · Answer 17 · Tue Jun 22 2021 11:22:41 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Zach Gotsch · Answer 18 · Tue Jun 22 2021 11:22:46 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Will Hart · Answer 19 · Tue Jun 22 2021 11:23:10 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

邻二氮杂菲 · Answer 20 · Tue Jun 22 2021 11:23:26 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Gregory Oakes · Answer 21 · Tue Jun 22 2021 11:24:38 GMT+0800 (China Standard Time)

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."

Joshua J. Bouw · Answer 22 · Tue Jun 22 2021 11:25:23 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Oscar · Answer 23 · Tue Jun 22 2021 11:25:46 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Nathan Stocks · Answer 24 · Tue Jun 22 2021 11:26:12 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Waridley · Answer 25 · Tue Jun 22 2021 11:27:24 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Jonathan Behrens · Answer 26 · Tue Jun 22 2021 11:30:29 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

John Doneth · Answer 27 · Tue Jun 22 2021 11:30:50 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

jak6jak · Answer 28 · Tue Jun 22 2021 11:30:56 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Cory Forsstrom · Answer 29 · Tue Jun 22 2021 11:31:20 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Denis Laprise · Answer 30 · Tue Jun 22 2021 11:31:30 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Grayson Burton · Answer 31 · Tue Jun 22 2021 11:32:00 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

freylint · Answer 32 · Tue Jun 22 2021 11:34:34 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Al M. · Answer 33 · Tue Jun 22 2021 11:36:12 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Lee-Orr · Answer 34 · Tue Jun 22 2021 11:37:04 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

…

On Mon., Jun. 21, 2021, 11:36 p.m. Al M., ***@***.***> wrote: I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2373 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPFHUENJ4HQ4VFLB3I6RADTUAAL7ANCNFSM47CY33HA> .

Gray Olson · Answer 35 · Tue Jun 22 2021 11:37:06 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

…

On Mon, Jun 21, 2021, 8:34 PM Frey ***@***.***> wrote: I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2373 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGYXHZHYMVCSRITE7ZRHKDTUAAFRANCNFSM47CY33HA> .

Ilja Kartašov · Answer 36 · Tue Jun 22 2021 11:37:39 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Philip Degarmo · Answer 37 · Tue Jun 22 2021 11:38:48 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Christopher Durham · Answer 38 · Tue Jun 22 2021 11:39:37 GMT+0800 (China Standard Time)

I license past and future contributions (to this and other bevyengine repositories) under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

I've also only contributed a version bump so far, so I probably didn't even need to okay this.

Don't forget to mute the issue once you've agreed to the relicense!

mfrancis107 · Answer 39 · Tue Jun 22 2021 11:39:54 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Christopher Durham · Answer 40 · Tue Jun 22 2021 11:41:59 GMT+0800 (China Standard Time)

(I don't think @dependabot[bot] will be replying, btw)

thebluefish · Answer 41 · Tue Jun 22 2021 11:43:09 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

0x22fe · Answer 42 · Tue Jun 22 2021 11:43:36 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Nathan Ward · Answer 43 · Tue Jun 22 2021 11:46:46 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Hans W. Uhlig · Answer 44 · Tue Jun 22 2021 11:49:41 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

jngbsn · Answer 45 · Tue Jun 22 2021 11:53:35 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Griffin · Answer 46 · Tue Jun 22 2021 12:03:51 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Lucas Rocha · Answer 47 · Tue Jun 22 2021 12:05:14 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Incipium · Answer 48 · Tue Jun 22 2021 12:09:39 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

…

On Tue, Jun 22, 2021 at 6:05 AM Lucas Rocha ***@***.***> wrote: I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2373 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVNNRBSXPJNONDGGHHQYRTTUADYXANCNFSM47CY33HA> .

CGMossa · Answer 49 · Tue Jun 22 2021 12:09:47 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

…

On Tue, Jun 22, 2021, 06:05 Lucas Rocha ***@***.***> wrote: I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2373 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIDVSBE6XBAR2WTSNPCHZDTUADYTANCNFSM47CY33HA> .

Cameron Hart · Answer 50 · Tue Jun 22 2021 12:09:48 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Spencer · Answer 51 · Tue Jun 22 2021 12:10:09 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

James Leflang · Answer 52 · Tue Jun 22 2021 12:12:10 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Alec Deason · Answer 53 · Tue Jun 22 2021 12:12:27 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Mike · Answer 54 · Tue Jun 22 2021 12:14:45 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

simlay · Answer 55 · Tue Jun 22 2021 12:14:57 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Aaron Housh · Answer 56 · Tue Jun 22 2021 12:25:38 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

MGlolenstine · Answer 57 · Tue Jun 22 2021 12:27:02 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Good luck with the license change!
I've done nothing but fix a few typos, but I think that a license change, especially a choice might not be such a bad idea.

Nick · Answer 58 · Tue Jun 22 2021 12:46:52 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Forest Anderson · Answer 59 · Tue Jun 22 2021 12:51:29 GMT+0800 (China Standard Time)

This is a pretty cool Bevy meetup,

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Nathan Jeffords · Answer 60 · Tue Jun 22 2021 12:57:26 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

reidbhuntley · Answer 61 · Tue Jun 22 2021 12:59:54 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Anselmo Sampietro · Answer 62 · Tue Jun 22 2021 13:04:20 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

RedlineTriad · Answer 63 · Tue Jun 22 2021 13:05:35 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Alexander Krivács Schrøder · Answer 64 · Tue Jun 22 2021 13:08:04 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

bjorn3 · Answer 65 · Tue Jun 22 2021 13:12:02 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

nil · Answer 66 · Tue Jun 22 2021 13:12:07 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Wojciech Olejnik · Answer 67 · Tue Jun 22 2021 13:27:45 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Léo Gillot-Lamure · Answer 68 · Tue Jun 22 2021 13:30:21 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Halfwhit · Answer 69 · Tue Jun 22 2021 13:34:19 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Jonathan Cornaz · Answer 70 · Tue Jun 22 2021 13:36:19 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Amber · Answer 71 · Tue Jun 22 2021 13:42:20 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Utkarsh · Answer 72 · Tue Jun 22 2021 13:45:47 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Federico Rinaldi · Answer 73 · Tue Jun 22 2021 13:47:08 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Gab Campbell · Answer 74 · Tue Jun 22 2021 13:47:56 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Will Crichton · Answer 75 · Tue Jun 22 2021 13:51:44 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Hugo · Answer 76 · Tue Jun 22 2021 13:51:44 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

TehPers · Answer 77 · Tue Jun 22 2021 13:54:46 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Glad to see this change :D

Théo Degioanni · Answer 78 · Tue Jun 22 2021 13:55:49 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Alexander Sepity · Answer 79 · Tue Jun 22 2021 13:57:11 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Mariusz Kryński · Answer 80 · Tue Jun 22 2021 13:57:43 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. wt., 22 cze 2021, 05:06 użytkownik Carter Anderson ***@***.***> napisał:

…

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 <https://github.com/bevyengine/bevy/blob/latest/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: I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. 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: 1. People and companies generally know and trust the MIT license more than any other license. Apache 2.0 is less known and trusted. 2. It is short and easy to understand 3. Many people aren't familiar with the "multiple license options ... choose your favorite" approach. I didn't want to scare people away unnecessarily. 4. Other open source engines like Godot have had a lot of success with MIT-only licensing However there were a variety of issues that have come up that make dual-licensing Bevy under both MIT and Apache-2.0 compelling: 1. The MIT license (arguably) requires binaries to reproduce countless copies of the same license boilerplate for every MIT library in use. MIT-only engines like Godot have complicated license compliance rules as a result <https://docs.godotengine.org/en/stable/tutorials/legal/complying_with_licenses.html> 2. The Apache-2.0 license has protections from patent trolls and an explicit contribution licensing clause. 3. The Rust ecosystem is largely Apache-2.0. Being available under that license is good for interoperation and opens the doors to upstreaming Bevy code into other projects (Rust, the async ecosystem, etc). 4. The Apache license is incompatible with GPLv2, but MIT *is* compatible. 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: ### License Licensed under either of * Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0) * MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT) at your option. ### Contribution Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions. 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 - @cart <https://github.com/cart> - @mockersf <https://github.com/mockersf> - @jakobhellermann <https://github.com/jakobhellermann> - @NathanSWard <https://github.com/NathanSWard> - @dependabot <https://github.com/dependabot>[bot] - @CleanCut <https://github.com/CleanCut> - @TheRawMeatball <https://github.com/TheRawMeatball> - @memoryruins <https://github.com/memoryruins> - @MinerSebas <https://github.com/MinerSebas> - @smokku <https://github.com/smokku> - @mrk-its <https://github.com/mrk-its> - @DJMcNab <https://github.com/DJMcNab> - @mtsr <https://github.com/mtsr> - @bjorn3 <https://github.com/bjorn3> - @StarArawn <https://github.com/StarArawn> - @blunted2night <https://github.com/blunted2night> - @Ratysz <https://github.com/Ratysz> - @multun <https://github.com/multun> - @stefee <https://github.com/stefee> - @alice-i-cecile <https://github.com/alice-i-cecile> - @zicklag <https://github.com/zicklag> - @alec-deason <https://github.com/alec-deason> - @OptimisticPeach <https://github.com/OptimisticPeach> - @joshuajbouw <https://github.com/joshuajbouw> - @lberrymage <https://github.com/lberrymage> - @aclysma <https://github.com/aclysma> - @YohDeadfall <https://github.com/YohDeadfall> - @TehPers <https://github.com/TehPers> - @Davier <https://github.com/Davier> - @julhe <https://github.com/julhe> - @jamadazi <https://github.com/jamadazi> - @amberkowalski <https://github.com/amberkowalski> - @BoxyUwU <https://github.com/BoxyUwU> - @Frizi <https://github.com/Frizi> - @Bobox214 <https://github.com/Bobox214> - @FlyingRatBull <https://github.com/FlyingRatBull> - @AngelOnFira <https://github.com/AngelOnFira> - @lachlansneff <https://github.com/lachlansneff> - @karroffel <https://github.com/karroffel> - @Moxinilian <https://github.com/Moxinilian> - @NiklasEi <https://github.com/NiklasEi> - @aevyrie <https://github.com/aevyrie> - @enfipy <https://github.com/enfipy> - @BafDyce <https://github.com/BafDyce> - @ashneverdawn <https://github.com/ashneverdawn> - @rmsc <https://github.com/rmsc> - @rparrett <https://github.com/rparrett> - @svents <https://github.com/SvenTS> - @simpuid <https://github.com/simpuid> - @willcrichton <https://github.com/willcrichton> - @reidbhuntley - @rod-salazar - @msklywenn - @Neo-Zhixing - @Byteron - @bitshifter - @frewsxcv - @Nilirad - @lassade - @lukors - @Veykril - @refnil - @mnmaita - @PrototypeNM1 - @ndarilek - @Jerald - @robertwayne - @superdump - @SmiteWindows - @tigregalis - @MGlolenstine - @adam-bates - @BimDav - @CGMossa - @nside - @GrantMoyer - @termhn - @Grindv1k - @dallenng - @guimcaballero - @Halfwhit - @jakerr - @ColdIce1605 - @Fishrock123 - @MarekLg - @nic96 - @RobDavenport - @Telzhaak - @joejoepie - @Xavientois - @blamelessgames - @caelunshun - @follower - @forbjok - @sdfgeoff - @thebluefish - @verzuz - @wyhaya - @ifletsomeclaire - @MichaelHills - @cart <https://github.com/cart> - @mockersf <https://github.com/mockersf> - @jakobhellermann <https://github.com/jakobhellermann> - @NathanSWard <https://github.com/NathanSWard> - @dependabot <https://github.com/dependabot>[bot] - @CleanCut <https://github.com/CleanCut> - @TheRawMeatball <https://github.com/TheRawMeatball> - @memoryruins <https://github.com/memoryruins> - @MinerSebas <https://github.com/MinerSebas> - @smokku <https://github.com/smokku> - @mrk-its <https://github.com/mrk-its> - @DJMcNab <https://github.com/DJMcNab> - @mtsr <https://github.com/mtsr> - @bjorn3 <https://github.com/bjorn3> - @StarArawn <https://github.com/StarArawn> - @blunted2night <https://github.com/blunted2night> - @Ratysz <https://github.com/Ratysz> - @multun <https://github.com/multun> - @stefee <https://github.com/stefee> - @alice-i-cecile <https://github.com/alice-i-cecile> - @zicklag <https://github.com/zicklag> - @alec-deason <https://github.com/alec-deason> - @OptimisticPeach <https://github.com/OptimisticPeach> - @joshuajbouw <https://github.com/joshuajbouw> - @lberrymage <https://github.com/lberrymage> - @aclysma <https://github.com/aclysma> - @YohDeadfall <https://github.com/YohDeadfall> - @TehPers <https://github.com/TehPers> - @Davier <https://github.com/Davier> - @julhe <https://github.com/julhe> - @jamadazi <https://github.com/jamadazi> - @amberkowalski <https://github.com/amberkowalski> - @BoxyUwU <https://github.com/BoxyUwU> - @Frizi <https://github.com/Frizi> - @Bobox214 <https://github.com/Bobox214> - @FlyingRatBull <https://github.com/FlyingRatBull> - @AngelOnFira <https://github.com/AngelOnFira> - @lachlansneff <https://github.com/lachlansneff> - @karroffel <https://github.com/karroffel> - @Moxinilian <https://github.com/Moxinilian> - @NiklasEi <https://github.com/NiklasEi> - @aevyrie <https://github.com/aevyrie> - @enfipy <https://github.com/enfipy> - @BafDyce <https://github.com/BafDyce> - @ashneverdawn <https://github.com/ashneverdawn> - @rmsc <https://github.com/rmsc> - @rparrett <https://github.com/rparrett> - @svents <https://github.com/SvenTS> - @simpuid <https://github.com/simpuid> - @willcrichton <https://github.com/willcrichton> - @reidbhuntley - @rod-salazar - @msklywenn - @Neo-Zhixing - @Byteron - @bitshifter - @frewsxcv - @Nilirad - @lassade - @lukors - @Veykril - @refnil - @mnmaita - @PrototypeNM1 - @ndarilek - @Jerald - @robertwayne - @superdump - @SmiteWindows - @tigregalis - @MGlolenstine - @adam-bates - @BimDav - @CGMossa - @nside - @GrantMoyer - @termhn - @Grindv1k - @dallenng - @guimcaballero - @Halfwhit - @jakerr - @ColdIce1605 - @Fishrock123 - @MarekLg - @nic96 - @RobDavenport - @Telzhaak - @joejoepie - @Xavientois - @blamelessgames - @caelunshun - @follower - @forbjok - @sdfgeoff - @thebluefish - @verzuz - @wyhaya - @ifletsomeclaire - @MichaelHills - @naithar - @Waridley - @woubuc - @0x22fe - @8bit-pudding - @Dispersia - @Adamaq01 - @ElArtista - @yrns - @akiross - @alexb910 - @W4RH4WK - @gfreezy - @alexschrod - @DivineGod - @ak-1 - @anchpop - @Weibye-Breach - @andrewhickman - @andreheringer - @AngelicosPhosphoros - @wilk10 - @Archina - @Boiethios - @Kurble - @trolleyman - @Olaren15 - @kokounet - @CAD97 - @FuriouZz - @ColonisationCaptain - @tarkah - @AmionSky - @DGriffin91 - @dburrows0 - @Incipium - @Dash-L - @mccludav - @themilkybit - @ShadowMitia - @Cupnfish - @bonsairobo - @eliaspekkala - @MrEmanuel - @EthanYidong - @w1th0utnam3 - @freylint - @liufuyang - @GabLotus - @payload - @ocornoc - @Gregoor - @gcoakes - @huhlig - @HyperLightKitsune - @Lowentwickler - @Ixentus - @no1hitjam - @jihiggins - @jleflang - @iwikal - @JohnDoneth - @fintelia - @jcornaz - @Josh015 - @JCapucho - @J-F-Liu - @kedodrill - @logannc - @CaelumLaron - @navaati - @sY9sE33 - @TheNeikos - @marcusbuffett - @turboMaCk - @M2WZ - @mjhostet - @MatteoGgl - @Lythenas - @FSMaxB - @tangmi - @blaind - @mkhan45 - @hymm - @MilanVasko - @Jbat1Jumper - @ncallaway - @AlisCode - @Philipp-M - @Plecra - @WilliamTCarroll - @Raymond26 - @RedlineTriad - @Restioson - @RichoDemus - @Git0Shuai - @ryanleecode - @saveriomiroddi - @schell - @sburris0 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2373>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHAVDHVNY7JCMVVFFJW4FDTT744XANCNFSM47CY33HA> .

guim · Answer 81 · Tue Jun 22 2021 13:59:41 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Wooster · Answer 82 · Tue Jun 22 2021 14:00:32 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Weibye · Answer 83 · Tue Jun 22 2021 14:01:43 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Loukas Agorgianitis · Answer 84 · Tue Jun 22 2021 14:07:12 GMT+0800 (China Standard Time)

Inspired by recent wgpu relicensing I suppose?
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Marek Legris · Answer 85 · Tue Jun 22 2021 14:11:17 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Fabian Löschner · Answer 86 · Tue Jun 22 2021 14:13:06 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

verzuz · Answer 87 · Tue Jun 22 2021 14:18:44 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

lambdagolem · Answer 88 · Tue Jun 22 2021 14:19:18 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

TotalKrill · Answer 89 · Tue Jun 22 2021 14:28:22 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Logan Magee · Answer 90 · Tue Jun 22 2021 14:31:42 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Wouter Buckens · Answer 91 · Tue Jun 22 2021 14:38:35 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Vladyslav Batyrenko · Answer 92 · Tue Jun 22 2021 14:40:34 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Marcel Müller · Answer 93 · Tue Jun 22 2021 14:42:08 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Andre Kuehne · Answer 94 · Tue Jun 22 2021 14:43:22 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Olivier Pinon · Answer 95 · Tue Jun 22 2021 14:43:22 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Ixentus · Answer 96 · Tue Jun 22 2021 14:46:58 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

the-notable · Answer 97 · Tue Jun 22 2021 14:48:53 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Adam Thibert · Answer 98 · Tue Jun 22 2021 15:07:46 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Gilbert Röhrbein · Answer 99 · Tue Jun 22 2021 15:09:59 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

François Mockers · Answer 100 · Tue Jun 22 2021 15:12:11 GMT+0800 (China Standard Time)

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.