Thread: Licensing issues including another projects source code into the jdbc driver

Licensing issues including another projects source code into the jdbc driver

From
"Dave Cramer"
Date:
I am contemplating including log4jme source code into the jdbc driver.
Who would be the best person to contact wrt ironing out the licensing
issues?

Dave




Re: Licensing issues including another projects source code

From
Bruce Momjian
Date:
> 
> I am contemplating including log4jme source code into the jdbc driver.
> Who would be the best person to contact wrt ironing out the licensing
> issues?

Can you tell us what license it uses?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


Re: Licensing issues including another projects source code into the jdbc driver

From
"Dave Cramer"
Date:
It is using the apache licence

http://www.qos.ch/log4jME/LICENSE.txt

It appears that they allow the code to be used in either binary or
source as long as their licence remains intact

Dave

-----Original Message-----
From: Bruce Momjian [mailto:pgman@candle.pha.pa.us] 
Sent: November 1, 2001 2:49 PM
To: dave@fastcrypt.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Licensing issues including another projects
source code into the jdbc driver


> 
> I am contemplating including log4jme source code into the jdbc driver.
> Who would be the best person to contact wrt ironing out the licensing
> issues?

Can you tell us what license it uses?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania190
 



Re: Licensing issues including another projects source

From
Peter Eisentraut
Date:
Dave Cramer writes:

> It is using the apache licence
>
> http://www.qos.ch/log4jME/LICENSE.txt
>
> It appears that they allow the code to be used in either binary or
> source as long as their licence remains intact

The apache license has an advertising clause, which is not acceptable.
Getting someone to relicense the software is difficult to impossible if
there is a multitude of outside contributors.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



Re: Licensing issues including another projects source code into the jdbc driver

From
"Dave Cramer"
Date:
Peter,

I presume you are referring to the 3rd clause? What is the issue with
this clause?

Dave

-----Original Message-----
From: Peter Eisentraut [mailto:peter_e@gmx.net] 
Sent: November 4, 2001 8:05 AM
To: Dave Cramer
Cc: 'Bruce Momjian'; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Licensing issues including another projects
source code into the jdbc driver


Dave Cramer writes:

> It is using the apache licence
>
> http://www.qos.ch/log4jME/LICENSE.txt
>
> It appears that they allow the code to be used in either binary or
> source as long as their licence remains intact

The apache license has an advertising clause, which is not acceptable.
Getting someone to relicense the software is difficult to impossible if
there is a multitude of outside contributors.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter




Re: Licensing issues including another projects source

From
Peter Eisentraut
Date:
Dave Cramer writes:

> I presume you are referring to the 3rd clause? What is the issue with
> this clause?

It would require everyone that ships a product based on the JDBC driver to
mention this acknowledgement in advertisements, which is annoying and
impractical.  More generally, it would introduce a divergence in licensing
in PostgreSQL, which should be avoided.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter