Thread: Re: [pgsql-www] change to interfaces.html
[ Discussion moved to "interfaces" list.] I think the unspoken complaint is why you would license an ODBC driver as GPL rather than LGPL, especially if you are not trying to enforce a burden on linked software. Frankly I thought the LGPL was the GPL without the linking clause, so why use the GPL in that case? Of course, you can license it however you want, but my bet is that is the underlying complaint, and the fact that ODBCng is kind of a fork of the psqlODBC driver that can't really be used because of the GPL, no matter how much you say there is no link/source burden. It feels like a GPL splinter project, kind of like taking the Postgres backend code and trying to release a GPL version (which you also could do, but community members aren't going to be thrilled about it). --------------------------------------------------------------------------- Joshua D. Drake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 16 Nov 2007 13:37:21 -0400 > "Marc G. Fournier" <scrappy@hub.org> wrote: > > > > Just because a company does the primary development that does not > > > mean it is not community code. Command Prompt is "core" on the > > > ODBCng project. Nothing more. > > > > These arguments I do agree with ... maybe some sort of 'feature > > matrix' is needed where we're dealing with multiple versions ... have > > an ODBC.html page and allow other 'versions' of ODBC include their > > products, commercial and open source ... > > To be clear (again). > > I do not care that ODBCng is placed under psqlODBC. I do agree with > Marc's argument that Alphabetical would be better, but I really don't > care other than that. > > What I do care about is the argument above. ODBCng "is" a community > project. What set me off, and what continues to raise my ire is the > obvious bias, ignorance and bigotry against an Open Source project that > is a community project, just because a company, which happens to be one > of the most prevalent supporters of the PostgreSQL community is the > primary developer. > > Sincerely, > > Joshua D. Drake > > - -- > > === The PostgreSQL Company: Command Prompt, Inc. === > Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 > PostgreSQL solutions since 1997 http://www.commandprompt.com/ > UNIQUE NOT NULL > Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate > PostgreSQL Replication: http://www.commandprompt.com/products/ > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFHPdlPATb/zqfZUUQRAlvxAJ9vKGy9gNFjBLB+xnLE2b19iXCrlQCeNwg+ > pMemuAEJ2oSLyvIAOXeKt1g= > =snm4 > -----END PGP SIGNATURE----- > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 16 Nov 2007 22:07:56 -0500 (EST)
Bruce Momjian <bruce@momjian.us> wrote:
>
> [ Discussion moved to "interfaces" list.]
>
> I think the unspoken complaint is why you would license an ODBC driver
> as GPL rather than LGPL, especially if you are not trying to enforce a
> burden on linked software. Frankly I thought the LGPL was the GPL
> without the linking clause, so why use the GPL in that case
Exactly why does it matter to you how we license our software? The only
thing that matters is that it is open source. That's it. Nothing more.
>
> Of course, you can license it however you want, but my bet is that is
> the underlying complaint, and the fact that ODBCng is kind of a fork
> of the psqlODBC driver that can't really be used because of the GPL,
The ODBCng driver is *not* a fork in any way shape or form of the
psqlODBC driver.
> no matter how much you say there is no link/source burden. It feels
> like a GPL splinter project, kind of like taking the Postgres backend
> code and trying to release a GPL version (which you also could do,
> but community members aren't going to be thrilled about it).
The analogy makes less than zero sense. We didn't take psqlODBC code.
We started from scratch. When ODBCng started, psqlODBC was dead and no
development had happen for a long time, psqlODBC was also libpq based
which we wanted nothing to do with.
(yes I am fully aware that psqlODBC no longer needs libpq except for
auth methods).
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHPl4BATb/zqfZUUQRAtcxAKCPXC6/rMo4SCPNNb/3pa6eBVxcigCfYuYt
Ghda0bTsUqeT9QtQnd3LsCw=
=npkx
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 16 Nov 2007 19:20:30 -0800
"Joshua D. Drake" <jd@commandprompt.com> wrote:
> The analogy makes less than zero sense. We didn't take psqlODBC code.
> We started from scratch. When ODBCng started, psqlODBC was dead and no
> development had happen for a long time, psqlODBC was also libpq based
> which we wanted nothing to do with.
>
> (yes I am fully aware that psqlODBC no longer needs libpq except for
> auth methods).
>
> Sincerely,
>
> Joshua D. Drake
Bruce pinged me on IRC about this and rightfully pointed out that he
was just trying to analyze the situation. I want to publicly apologize
to Bruce as I obviously came off hostile.
So hats off with a bow, I am sorry. I should have taken a breath before
I responded.
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHPmuxATb/zqfZUUQRAmS9AKCcD7F8vhpgec6fHfb/X53IpV5hSACcCzwE
Sb8VkXrvDjwDVGbmnFTEvxI=
=uUxa
-----END PGP SIGNATURE-----