| > you'd need to prevent the people you're granting the license to from changing it in derivative works No you don't need to. People cannot change the license of code they don't own nilly-willy, only the owner(s) of code can (which can get hairy when a codebase has multiple owners). However a license can allow sublicensing, aka sharing the code or software under a different license, but this right must be explicitly granted by the license (or by the code owner directly), and they may be conditions attached (such as attribution) MIT: "[...] Permission is hereby granted,[...] to use, copy, modify, merge, publish, distribute, sublicense, [...] subject to the following conditions: The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software." GPL: "[...] You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License." So the MIT license grants you the right to redistribute the code under GPL (under attribution condition), but GPL does not grant you the right to redistribute the code under MIT. (Note that all of this applies to redistributing the code or the software, not about your own internal use of the code or the software) |