On Mon, 04 May 2015 11:41:10 -0700
Mike Easter <Mi...@ster.invalid> wrote:
> I'm not crystal clear on how the LO licensing works; it is in part
> LPGLv3 and part MPL while dealing with the ASF OO code license
> ownership issue.
Instead of switching back and forth between "LO" and "TDF", I'll just
mostly just use "LO". Also IANAL, but I have the arrogance of one. ;)
LO includes a lot of stuff from different upstreams licensed under a
variety of free software licenses. Hunspell, fontconfig, libpng, on
and on. That kind of stuff they may or may not have modified, and they
don't change the license. But the bulk of LO, the code that's really
under the umbrella of TDF, they offer under the MPLv2.
I'm pretty far from crystal clear about most of the nitty-gritty,
but FWIW, here's the way I understand how the relicensing went:
At its inception, LibreOffice just offered its code under the the LPGL,
same as OOo. If they'd wanted to, they could have continued that
forever, but the LPGL does not have strong enough copyleft to make LO
happy.
When Oracle gave control of the OOo code to Apache, Apache then offered
the OOo code under the Apache 2 license. LO then ditched the (Oracle)
OOo codebase it had started and accepted the Apache OO codebase with the
Apache 2 terms. They ported all the changes they had made over to the
Apache OOo codebase and went from there. At that time, the Apache OOo
codebase was substantially the same the Oracle OOo codebase LO had
started out with, so the transition was not as awful as one might
imagine -- in most cases, 'porting' boiled down to changing a
file's headers.
From its inception, LO had been getting new contributions under an
MPL/GPL3+ license.
Apache 2 is permissive enough to let people who accept that license
modify and release the code under the MPLv2, which is what
essentially what LO did.
For a while, LO were using the phrase "MPLv2 on top of Adobe 2". AIUI,
Adobe 2 allows only modified files to be distributed under a new
license -- unmodified files must not have their licenses changed. So
the files LO had modified were offered under the MPLv2 and the ones
they hadn't were under Apache 2. Anyone accepting those license terms
and wanting to re-distribute under the MPLv2 would just need to change
the license of any Apache 2 file they modified, same as LO itself. So
for most practical purposes, at least ones LO cared about, this
situation was okay.
For ideological reasons, it was not okay -- LO didn't want to
redistribute *any* files without copyleft. I think all the files have
been modified and relicensed by now, but I'm not completely sure. The
Apache 2.0 license still appears in the big list of licenses that may
or may not apply to some of the files, but AFAIK licenses are never
removed from such a big may-or-may-not list.
You mentioned LPGLv3. I've left that part out entirely because I don't
understand it at all. I think it had something to do with Apache 2.0
being compatible with LPGL3 but not LPGL2.1, whereas the MPLv2 is
compatible with LPGL2.1+.