sun xfs is zfs right ? I will check how the GLP/apache and mpl2 linking works but i know why they are using in libreoffice (practical reasons) https://wiki.documentfoundation.org/Development/Re-Basing#Why_go_with_the_MPLv2_.3F
I quote from mpl2 history and its reasons and it is to me quite sane reasons (this is the url where they worked on it https://web.archive.org/web/20130127034402/https://mpl.mozilla.org/) What's New The result of a two year revision process that included feedback and suggestions from the Mozilla community, users of the MPL (both community and corporate), and the broader open source legal community, MPL 2.0 contains several important changes from MPL 1.1. In particular, MPL 2.0: is simpler and shorter, using the past 10 years of in-practice application of the license to help better understand what is and isn't necessary in an open source license. is modernized for recent changes in copyright law, and incorporates feedback from lawyers outside the United States on issues of applicability in non-US jurisdictions. provides patent protections for contributors more in line with those of other open source licenses, and allows an entire community of contributors to protect any contributor if they are sued. provides compatibility with the Apache and GPL licenses, making code reuse and redistribution easier. On Fri, Apr 4, 2014 at 12:57 AM, Jim Starkey <[email protected]> wrote: > On 4/3/2014 5:16 AM, marius adrian popa wrote: >> I repost it here from Firebird-general >> >> Just noticed Mozilla license v1.1 >> http://opensource.org/licenses/MPL-1.1 was upgraded to v 2.0 maybe is >> time for firebird project to do so for all new code (This license has >> been superseded by the Mozilla Public License 2.0; please use the MPL >> 2.0 instead of 1.1.) >> >> http://www.mozilla.org/MPL/2.0/differences.html >> https://www.fsf.org/blogs/licensing/mpl-2.0-release >> >> The mpl 2.0 just needs a few changes as desribed in this paper >> (related to mpl1.1 vs idpl 1.0 changes) >> >> http://www.firebirdsql.org/file/documentation/papers_presentations/html/paper-fbent-manage.html#fb-management >> http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/ >> >> It should be easy doable for new code >> >> > > I've taken a quick first pass over the new Mozilla license and, frankly, > I don't understand it or how it is supposed to work with GPL. > > My understanding of the original problem is that both the original MPL > and GPL require that changes must be made available under the original > license. The problem is that GPL insists that anything that has been > under GPL must continue to be under GPL, and that anything that contains > any GPL code is subject to GPL in its entirety. This is what prevented > Linux from adopting Sun's XFS -- The Sun license requires that changes > to XFS be made available to users under the Sun license, but any changes > to XFS made for Linux would be automatically GPLed, making it impossible > to conform to the Sun license terms. So last I heard, XFS was just > rotting away. > > The problem is with GPL, not the "secondary" licenses. I don't > understand how the MPL can get around a problem intrinsic to GPL. > > Somebody probably understands this, but until the nuances of the new MPL > and its relationship to the GPL, I think caution is in order. There's no > rush. > > And from the very unpleasant brawl with Mozilla over the Firebird name, > I'm less inclined to trust them than I once was. > > > ------------------------------------------------------------------------------ > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
