From: Peter Harvey <pharvey@codebydesign.com>
Cc: pgsql-interfaces@postgreSQL.org
Subject: RE: [INTERFACES] hacked unixodbc driver..
Date: Sun, 13 Jun 1999 16:07:33 -0400
Message-ID: <000d01beb5d8$5f91b2e0$0208de0a@laptop> (raw)
In-Reply-To: <38778776.7E9CBEB3@perio.unlp.edu.ar>
Hi,
Relax. OpenSource maintainers can simply say that we only accept patchs and
we only give out cvs write access to those who have submitted some quality
patchs. Thomas said as much to me.
Any developer who feels that creating a code fork is easier than dealing
with the maintainer than they should go ahead and do so. I say this, not
because I like code forks, but because I know of projects (this is not one
of them) which have maintainers who continue to control code long past when
they are really able to commit any time to do the job.
re. unixODBC
I prefer to 'mirror' some driver source. This way I can make any changes and
enhancements to ensure it meets some tests (ie works with StarOffice) and
ensure that it is availible to unixODBC users while I wait for changes to be
accepted by the source maintainers.
The problem with ODBC is that nonone has been handling it holistically... at
least no OpenSource developers and this is exactly what is required to get
ODBC moving on UNIX/Linux. This is why I started unixODBC.
The plan is to be less holistic when unixODBC 1.0 comes out. In other words;
the focus will return to things like the DM and drivers will go through
compliance tests. The compliance tests will be sent to driver source
maintainers and they can do what they want with the info... unixODBC
developers will not try to fix all drivers out there.
Having said all of that... I have offered to do the patch submissions when
asked (ie when PostgreSQL folks are ready).
Also note; a number of iODBC and unixODBC developers are currently working
on actual code changes and enhancements to get ODBC into KDE. This should be
very healthy and will likely see something of a merge between the two.
Peter Harvey
BTW: Please do not discourage George, or any other developer, from spending
time on PostgreSQL or any other project. Developers such as George deserve
some lee-way because they spend a great deal of their time on this stuff for
free. I often have to remind myself that I am working with a group of
volunteers... not paid employees... it always changes the tone of my emails.
> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Sergio
> Kessler
> Sent: Saturday, January 08, 2000 1:53 PM
> To: George Henry C. Daswani
> Cc: pgsql-interfaces@postgreSQL.org
> Subject: Re: [INTERFACES] hacked unixodbc driver..
>
>
>
> is that nobody who hack the ODBC driver know how to make
> diffs files ?
>
> This is getting annoying, first the guy (from UnixODBC, I think)
> who introduces itself on this list saying:
>
> "Hey, I want write cvs access on the tree or I will make
> a fork of the odbc driver ..."
>
> without even asking who is the driver mantainer, etc ...
> very, very polite ...
>
> Now, there is Daswani, who say (more or less):
>
> "I've hacked the odbc driver, you want the changes ?,
> download this..." (the whole driver)
>
> Please, people, this is not how the Open Source work, there
> must be a _little_ more cooperation, if anybody will make their
> own with the driver, things will go crazy, really crazy.
>
> Just a:
>
> "Hi, I've hacked the driver, the changes are ..., here is
> the patch."
>
> would be excellent.
>
> btw, I would like to see Byron (the current maintainer) to say
> something about their situation with respect to the driver
> (last time he was a little complicated with their personal
> situation, hope he is better now).
>
> Sergio
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: pharvey@codebydesign.com
Subject: RE: [INTERFACES] hacked unixodbc driver..
In-Reply-To: <000d01beb5d8$5f91b2e0$0208de0a@laptop>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox