6 ms·

Heh. Honestly, I'm not sure. IANAL, but I think it would be okay considering MPL version 2 is a GPL compatible license https://en.wikipedia.org/wiki/GPL#Compat

Heh. Honestly, I'm not sure. IANAL, but I think it would be okay considering MPL version 2 is a GPL compatible license https://en.wikipedia.org/wiki/GPL#Compatibility_and_multi-licensing https://en.wikipedia.org/wiki/GPL#Compatibility_and_multi-li... That said, I tend to just pick MPL by default for my projects, but am not opposed to changing to make it compatible (not to mention there's hardly any code in the repo anyways)

zeckalpha 13y ago
IANAL either, but I believe. MPL can be imported by a GPL project, but not the other way around, as the importer would need to be licensed as GPL, too.
- belorn 13y ago
  FSF has a rather lengthy text regarding using MPL with GPL at http://www.gnu.org/licenses/license-list.html#MPL-2.0 http://www.gnu.org/licenses/license-list.html#MPL-2.0 I would agree with the above statement that MPL can be licensed as GPL, but not the other way around. However, I would follow the FSF advice in keeping MPL code MPL through dual licensing.