Mpl 1.0 , 1.1 licenses are outdated and shouldn't be used for new code
http://opensource.org/licenses/do-not-use.html

The old versions had issues with gpl licenses
https://www.gnu.org/philosophy/license-list.html#GPLIncompatibleLicenses
http://oss-watch.ac.uk/resources/mpl2#what-makes-the-mpl-2-different-from-mpl-11
https://www.mozilla.org/MPL/2.0/differences.html

http://www.eionet.europa.eu/software/licenseexplained.html

On Thu, Mar 5, 2015 at 2:47 PM, Dmitry Yemanov <firebi...@yandex.ru> wrote:

> 05.03.2015 15:38, marius adrian popa wrote:
>
> > Ok understand, what i ask is that new code to be under MPL 2.0
>
> What is our benefit?
>
> > This will simplify the license understanding
>
> Nope, it will only complicate understanding. Old modules have to remain
> IPLed/IDPLed, so actually we'll be claiming three licenses instead of two.
>
>
> Dmitry
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> Firebird-Devel mailing list, web interface at
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to