Skip to Content.
Sympa Menu

freetds - Re: tsql infected with GPL

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: Re: tsql infected with GPL
  • Date: Fri, 27 Sep 2002 13:04:34 -0400


> From: Shanmugham, Abilash (London)
> [mailto:ShanmAbi AT exchange.uk.ml.com]
> Sent: September 27, 2002 12:08 PM
>
> Why the GPL promotes more open source
>
> http://www.gnu.org/licenses/why-not-lgpl.html
>
> -Abhi

Abhi,

There's a case for making FreeTDS GPL. It meets RMS's criterion of having
no competition, for instance.

Two countervailing arguments:

1. Vendors of proprietary systems contribute to FreeTDS because they can
use it. That makes for a better library for the likes of Perl and PHP. I
for one would rather accept their help, so we can pass it on to everyone
else.

2. Brian wrote the code and chose the license. Nowadays we have a lot of
non-Brian code, which is wonderful, leading to many important improvements!
But the originator chooses a license at the outset, when the project is a
one-man band, until it (he) achieves critical mass. His choice is normally
kept, partly because the project attracts like minds, partly inertia, and
partly out of deference. Even, sometimes, because it was the right choice.


As things stand, FreeTDS can help everyone and accept help from everyone,
and can focus on getting the job done. Speaking for myself, that's how I
like to work.

Regards,

--jkl



The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page