Re: Change License

If you read the page you linked to, they're saying that *Apache Foundation
products* can not use LGPL licenses. They are not talking about users of
the Apache license.

If you want Hue to be an Apache Foundation product at some point, it sounds
like the Apache Foundation would want it to be licensed with the Apache
license before accepting it. Having said that, nothing in either license
prohibits you (as maintainers of Hue) from linking against the psycopg2
python library from your Apache-licensed library.

On Wed, Dec 11, 2013 at 3:10 AM, Abraham Elmahrek <abe(at)cloudera(dot)com> wrote:

> I think the correct page to reference would have been
> http://www.apache.org/legal/resolved.html. Sorry about that...
>
> My understanding is that the third-party licensing policy page is simply
> guidelines for how to interpret ASLv2. The resolved page insists that LGPL
> shouldn't be included in apache projects. I do think that extends to any
> project with ASLv2 license since it seems like an interpretation of the
> license itself.
>
> LGPL is a great license. I can understand why LGPL was chosen for
> postgresql and its various subprojects. It makes perfect sense to control
> the rights of a project and guide users to contribute back to the original
> code base. psycopg2 is, how ever, a client. It seems less likely that a
> client would be forked than the postgresql code base itself. Also, making a
> client packageable in every other project seems like a great goal,
> irrespective of licensing.
>
> Also, thanks for all the responses. It's great to see so much involvement
> from the community. I definitely appreciate it!
> -Abe
>
>
> On Wed, Dec 11, 2013 at 12:57 AM, Federico Di Gregorio <fog(at)dndg(dot)it>wrote:
>
>> On 11/12/2013 03:47, Daniele Varrazzo wrote:
>> > On Tue, Dec 10, 2013 at 10:10 PM, Abraham Elmahrek <abe(at)cloudera(dot)com>
>> wrote:
>> >> > Hey Guys,
>> >> >
>> >> > Thanks for the speedy responses. I work on the Hue project at
>> Cloudera. Hue
>> >> > is an ASLv2 licensed project and according too
>> >> > http://www.apache.org/legal/3party.htm LGPL is excluded from the
>> list of
>> >> > shippable licenses. The end goal is to be able to ship psycopg2
>> since it's a
>> >> > complete client for postgresql that django fully supports.
>> > Note: the correct url above is <http://www.apache.org/legal/3party.html
>> >.
>> >
>> > I didn't know the Apache Software Foundation was in open war with the
>> > GPL. Well, too bad: it seems you chose the wrong license for your
>> > software.
>> >
>> > We could be able to provide a personal, non-transferable license for
>> > projects whose lawyers insist to require it; however your license
>> > seems to forbid this option too.
>> >
>> > I'm afraid the chance to see psycopg released with a non-LGPL license
>> > are quite low.
>>
>> I'd say they are 0. :)
>>
>> federico
>>
>> --
>> Federico Di Gregorio federico(dot)digregorio(at)dndg(dot)it
>> Di Nunzio & Di Gregorio srl http://dndg.it
>> Non vi sono certezze, solo opportunità. -- V
>>
>
>