|Re: [eigen] Re: Contributor approval for the MPL2 relicensing (YOUR ACTION NEEDED)|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] Re: Contributor approval for the MPL2 relicensing (YOUR ACTION NEEDED)
- From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Date: Thu, 28 Jun 2012 20:33:56 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=WzPydyWt+pNOKGIOp0wZ2hLmRehEsJfLk3GkZx93o4U=; b=kROhy5y2NvSXTWU+QVZ6h8V4wLzVIUhkDoBP3+JvDPeQfn0pIk4zmB6jRF16none8/ kHS/a1v+zGm+wc7brauh6pjilbtoF/kvSyqouC3WJsTe8wle1soCCTNkNCzkdiorFa0x tqlgYWn8DleZvei7tjZTVhWY6nfaDqOXkPQVWnH0m3D9JnRU3EQjJBRXiddVLsLOIlot YFE6YUVPnVij/OVl5kmflJWE5hZh/K5xPHJs5e1nPOOx2gJear+FxJ0Hmsr2SQmKDY4U gJwXfwes8xNi2BvqdPNTEInSGTNMXylTGMZHd51SWpNYtuMKiXiPNW1R5hTgz8O7cFZn 5aBA==
In fact, CMake code should have a license too, especially as we have
highly nontrivial CMake code.
What shall we choose?
- MPL2 for uniformity within our codebase?
- or BSD/MIT like KDE does for CMake code for maximum ease of sharing/reusing?
2012/6/28 Marcus D. Hanwell <marcus.hanwell@xxxxxxxxxxx>:
> Yes, I agree to have all the code that I contributed to Eigen
> relicensed to the MPL2 license.
> I believe all I ever contributed was a little CMake code, so perhaps
> not so important in this context ;-)
> On Thu, Jun 28, 2012 at 3:31 PM, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
>> Let me open the dance:
>> Yes, I agree to have all the code that I contributed to Eigen
>> relicensed to the MPL2 license.
>> 2012/6/28 Benoit Jacob <jacob.benoit.1@xxxxxxxxx>:
>>> Hi List,
>>> We want to relicense to the MPL2 license very soon. The explicit
>>> written agreement of every contributor is needed. It is worth replying
>>> to this thread even if you've contributed only 1 byte to Eigen. We
>>> probably won't get all the minor contributors and we'll use common
>>> sense there, but it is worth chasing everyone we can.
>>> Before going on, here are two links that you should check out before proceeding:
>>> - the MPL2 license:
>>> - the MPL2 FAQ:
>>> Notice that this is about relicensing Eigen to the MPL2 *only*. The
>>> current LGPL/GPL licensing options will be removed. Make sure that you
>>> understand this. We are currently investigating the status of MPL-GPL
>>> compatibility, as that is of course a requirement for this relicensing
>>> to be acceptable. You can help with that --- see the other thread. We
>>> will not actually relicense until we are certain that this will be
>>> acceptable by users who rely on LGPL/GPL compatibility.
>>> So, please reply to this email with either one of the following two sentences:
>>> Yes, I agree to have all the code that I contributed to Eigen
>>> relicensed to the MPL2 license.
>>> No, I do not agree.
>>> Anything else than the above "Yes" sentence will mean "No".