On Saturday 29 April 2006 02:57, Ben van Klinken wrote: > For historical reasons, CLucene is dual licensed as Apache 2.0 license > or LGPL. As I understand it, the apache license is currently is not > compatible with GPL projects and therefore GPL projects can't > distribute apache licensed software, so we would like to maintain the > LGPL license as well.
Although Apache is not about its license, there are a lot of mechanisms in Apache that assumes that there is only one license and that such license is the Apache License v2.0 Although not directly forbidden, it will be a great burden on the project (without support from the infrastructure team) and big deterent to manage to maintain a dual-licensing scheme. E.g. Apache does not work with Copyright assigns, so each contribution is still Copyrighted to the original author. Contribution via JIRA requires the contributor to actively indicate that the contribution is covered by ALv2. For a potential dual-licensing scheme, you must obtain the approval from the contributor individually and separately from the normal procedures. Furthermore, what if the contributor explicitly prohibits licensing under one or the other licenses? I doubt that the project will manage. Now, as Noel points out, the compatibility issue is from our perspective very obscure, and requires not only patents, but that the patent holder sues and is distributing the (L)GPL'd work themselves (or something along those lines)... Somehow, it doesn't stop RedHat/Debian/et al to ship ALv2 stuff as part of the GPL'd GNU/Linux platform. My personal recommendation; Drop the dual licensing scheme, as it will break if contribution numbers rises and would make less noise/problem when/if coming to the Apache Incubator. Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
