[HACKERS] GPL License

2002-07-29 Thread Rod Taylor

Given the GPL isn't wanted in the contrib directory, it may be wise to
take care of src/interfaces/odbc/license.txt




---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster



Re: [HACKERS] GPL License

2002-07-29 Thread Dave Page



 -Original Message-
 From: Rod Taylor [mailto:[EMAIL PROTECTED]] 
 Sent: 29 July 2002 14:39
 To: PostgreSQL-development
 Subject: [HACKERS] GPL License
 
 
 Given the GPL isn't wanted in the contrib directory, it may 
 be wise to take care of src/interfaces/odbc/license.txt

Take care of it how? It can't be just removed as everything under
src/interfaces/odbc *is* LGPL.

Regards, Dave.

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster



Re: [HACKERS] GPL License

2002-07-29 Thread Rod Taylor

  -Original Message-
  From: Rod Taylor [mailto:[EMAIL PROTECTED]] 
  Sent: 29 July 2002 14:39
  To: PostgreSQL-development
  Subject: [HACKERS] GPL License
  
  
  Given the GPL isn't wanted in the contrib directory, it may 
  be wise to take care of src/interfaces/odbc/license.txt
 
 Take care of it how? It can't be just removed as everything under
 src/interfaces/odbc *is* LGPL.

Generally you have to track down all contributors to the code and ask
them 1) to assign the copyright to the group, and 2) if its ok to change
the license on their bit.

Doing 1 helps doing 2 later.




---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly



Re: [HACKERS] GPL License

2002-07-29 Thread Dave Page



 -Original Message-
 From: Rod Taylor [mailto:[EMAIL PROTECTED]] 
 Sent: 29 July 2002 14:44
 To: Dave Page
 Cc: PostgreSQL-development
 Subject: RE: [HACKERS] GPL License
 
 
   -Original Message-
   From: Rod Taylor [mailto:[EMAIL PROTECTED]]
   Sent: 29 July 2002 14:39
   To: PostgreSQL-development
   Subject: [HACKERS] GPL License
   
   
   Given the GPL isn't wanted in the contrib directory, it may
   be wise to take care of src/interfaces/odbc/license.txt
  
  Take care of it how? It can't be just removed as everything under 
  src/interfaces/odbc *is* LGPL.
 
 Generally you have to track down all contributors to the code 
 and ask them 1) to assign the copyright to the group, and 2) 
 if its ok to change the license on their bit.
 
 Doing 1 helps doing 2 later.

Yeah, I tried to do that with about 10 developers on pgAdmin I when I
wanted to reuse some of the code on pgAdmin II (which has it's own
licence). I eventually had to give up.

psqlODBC has been LGPL much longer than it's has been in the main CVS.
Originally it was written by Christian Czezatke and Dan McGuirk (1996),
following them, Insight Distribution Systems (1996 - 1998 - Byron
Nikolaidis + others iirc), then numerous PostgreSQL developers. Tracking
down all the developers since Christian  Dan would be a nightmare I
suspect - especially as we don't (to my knowledge) have CVS logs prior
to Apr 13 15:01:38 1998.

I would like to see it under BSD licence though...

Regards, Dave.

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])



Re: [HACKERS] GPL License

2002-07-29 Thread Tom Lane

Dave Page [EMAIL PROTECTED] writes:
 From: Rod Taylor [mailto:[EMAIL PROTECTED]] 
 Given the GPL isn't wanted in the contrib directory, it may 
 be wise to take care of src/interfaces/odbc/license.txt

 Take care of it how? It can't be just removed as everything under
 src/interfaces/odbc *is* LGPL.

You're failing to distinguish GPL from LGPL.  The consensus as I recall
it was that we wanted to remove GPL-license stuff from our standard
distribution, but LGPL is okay (it's not so fundamentally incompatible
with the project's own BSD license).

I would rather see ODBC under BSD, sure, but I can live with LGPL.

regards, tom lane

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly