Joshua D. Drake wrote:
>
> > Well, GPL is certainly a minus for a lot of PostgreSQL folks. The
> > current ODBC driver is LGPL and that seems OK, though not ideal. Seems
> > we will have to live with two drivers, one GPL and one LGPL.
>
> We are taking a very similar road as TrollTech with QT on this
> particular project. We want to deliver the highest quality driver
> possible which means we need to insure a revenue stream from those who
> would need to use ODBC in a closed sourced environment.
>
> The driver is still Open Source and still free to those who will be
> using or creating software that is GPL compatible.
I hear MySQL calling you. Please pick up the phone. :-)
> > When you say "commercial licenses", I assume you just mean commercial
> > support, not non-GPL versions, because if you do that,
>
> I do mean non-GPL versions and commercial support. However there isn't
> any real commercial support with ODBC. If you correctly code the driver
> it will work without the need for support except in the very rare
> circumstances.
>
> > you can't take
> > contributions from anyone (unless you want them to sign ownership over
>
> This is something that we are still trying to figure out.
Nothing to figure out. You have to get signed contracts giving you
rights to the code changes.
> > to CP) and you might as well yank it off pgfoundry.
>
> Are you forgetting community mailing lists? Community documentation?
> Community discussion of API? Bug reporting? Community support? All the
> things that make pgfoundry and the PostgreSQL community great?
Pgfoundry is for community development of software. Yours is not that
so doesn't belong there. The things that make the PostgreSQL community
great are not part of your project, it seems.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
