|[eigen] moving forward with MPL2|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen <eigen@xxxxxxxxxxxxxxxxxxx>
- Subject: [eigen] moving forward with MPL2
- From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Date: Wed, 13 Jun 2012 06:47:16 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=J15I1aY3ukiTAAsne3qR2Sha3Al/tZBQundhLc9fqvw=; b=ajPmlCiJBAXzKLBCv8/7Np3zp23lJfAMLm4qfZZjA7jD6BWpsSNxLainJ9p75kQIot obTpF4zqiIzgYnq6xSCb9kXqMKjy9WJeQaksyJwFwqK1z2VaioVglgkHOh8FVVSsepX2 WfbJLQGxujYGkYrdKCEJRP43fpinhlZ3QSjfwprJU7OU3eiL4G3lUKpp98QGrd9QgUHu 2iQMnggFF+x7eYdIksdRkO0xJ1zovCIipHBmKh/DAXCqz875JjB0yivnC8O+wz6Ja5Ll 5stkftRQx4KYrzIOglfEa3XwkWZfbiii0PaDts5sid6Bs4eJtjpYGu4+1pBLNzHtczrQ MkdQ==
Can't believe it's been 6 months already!
Anyway, the MPL2 relicensing effort has stalled out. I gather that the
main hesitations about it were:
1. MPL2 is a new untested license
2. status of GPL/LGPL compatibility not fully obvious from the license or FAQ
Regarding 1. notice that since then, Mozilla has effectively
relicensed most of its code to MPL2, and all new code should be MPL2,
so there is in fact quite a bit of MPL2 code around now. But still,
not nearly as much as established licenses, of course.
In my original proposal, I said that we should relicense to MPL2-only
instead of tri-licensing, as tri-licensing had proved a weak choice
for Mozilla, as it opened the door to GPL-only back-contributions that
we wouldn't be able to incorporate in the original product.
However, 6 months after, it seems like a good time to ease corners a
bit to make at least something happen, as the statu quo (LGPL/GPL
only) is really not great.
So how about this: relicense to MPL2 + existing LGPL3+/GPL2+ licenses
(i.e. tri-license)? At least this doesn't have a lot of possible
disadvantages compared to the current situation. The above-mentioned
loophope already exists with our present dual-license.
Keeping the existing LGPL+GPL licenses should remove the above
concerns 1. and 2.