@bevy Is there anything in the Bevy Foundation Legal structure that prevents it from ever changing bevy's licensing model to something that requires purchasing? Unity was able to change their license freely and in the process screw devs and i don't want that to ever happen to bevy, im talking wayyy down the line when the current team has been long replaced and the people might not have the best interests of bevy users in mind.
@Rin3d nope there is nothing we could do to change the license of the code that is already written. Because we don't do CLAs, re-licensing Bevy's code would require sign-off from every Bevy contributor. Given that contributors would not sign off on shady re-licenses, this is not a risk.
@bevy@Rin3d Since both Apache 2.0 and MIT are permissive licenses it is entirely possible to include the code in more restrictively licensed projects – copyleft licensed such as well as proprietary stuff.
The only thing that can't be done is to eg. relicense from MIT to 0BSD as 0BSD does not enforce the attribution that MIT requires.
Eg. the Bevy Foundation chose a new license for all new contributions, but people will be free to remain using the old code and eg. fork it.
Add comment