>>105571520>they are free to close those whenever they feel like.This is a half-truth, you can make a GPL program closed-source if
>You wrote it entirely by yourselfor
>Contributors are bound by a CLA (Basically a document that says "We won't accept your contributions unless you hand over all rights to us)Naturally, this only applies to future versions, if Program 1.0 is GPL, and you suddenly decide that Program 2.0 is proprietary, Program 1.0 is still gonna be bound by the GPL. All of this also applies to MIT/BSD, the only thing that changes is that you don't need permission from contributors, because their contributions are under MIT/BSD, and naturally can be included in Program 2.0 even if it's proprietary
>If Linux would have used GPLv3, this wouldn't be an issueThe only thing Linux being GPLv3 would cause is every phone having an unlocked bootloader (Which would be great, but that's beyond the scope of this discussion).
Linux's license doesn't really matter because it only interacts with other parts of the OS via syscalls, if it mattered, GNU/Linux wouldn't be possible, as the GPLv2 is incompatible with GPLv3 or later; and when GNU switched to v3 or later, companies didn't stop shipping Linux, they kept using Linux and replaced GNU with stuff like Busybox