[Xapian-devel] Licensing
Richard Boulton
richard at tartarus.org
Tue Aug 11 15:23:16 BST 2009
2009/8/7 James Aylett <james-xapian at tartarus.org>
> To get the ball rolling: all code and modifications I have contributed
> to Xapian may be licensed under either the GPL (as stands) or LGPL (if
> this is practical for the code in question). Similarly, both the GPL
> and LGPL may be used for my future contributions.
I discussed this this morning with the other directors of Lemur Consulting,
and we're happy to change the license for the contributions we have made.
We actually think that LGPL may be too restrictive, so it would be useful to
keep the option of using the MIT or Apache2 licenses, too. The MIT license
is about as unrestrictive as you can get (other than Public Domain, or
attempts to replicate Public Domain with a license), and Apache2 is similar
to MIT but with a "mutual annihilation" patent clause. Therefore, Lemur
says:
All code and modifications that Lemur has contributed to Xapian may be
licensed under either the GPL version 2 or later (as stands), or the LGPL
version 2.1 or later, or the Apache2 license, or the MIT license, where this
is practical for the code in question (ie, except where Lemur does not hold
the copyright on the code submitted, and is therefore unable to change the
license). Similarly, any of these licenses may be used for future Lemur
modifications, unless explicitly stated to the contrary.
For the text of these licenses, see (respectively)
http://www.opensource.org/licenses/gpl-2.0.php
http://www.opensource.org/licenses/lgpl-2.1.php
http://www.opensource.org/licenses/apache2.0.php
http://www.opensource.org/licenses/mit-license.php
--
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xapian.org/pipermail/xapian-devel/attachments/20090811/f436f950/attachment.htm
More information about the Xapian-devel
mailing list