MIME-Version: 1.0
References: <b8a5f718803e53f5d7e816949467e7f1e152b9d2.camel@gunduz.org>
 <CADK3HH+ZwMZrc6DGg=TPhwd=vnJZ-zP1LDjC8q-3NjCySBCk9w@mail.gmail.com>
 <ZPUaX0jLAFryE/th@paquier.xyz>
In-Reply-To: <ZPUaX0jLAFryE/th@paquier.xyz>
From: Dave Cramer <davecramer@postgres.rocks>
Date: Mon, 4 Sep 2023 07:13:07 -0400
Message-ID: 
 <CADK3HHJFd0nnr7xtu1zxsi76Kc1mq5Hj7XrzTeEkxHfgSunF7Q@mail.gmail.com>
Subject: Re: ODBC driver maintenance: PostgreSQL 16 support and other open
 items
To: Michael Paquier <michael@paquier.xyz>
Cc: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= <devrim@gunduz.org>,
	Hiroshi Saito <hiroshi@winpg.jp>, "Inoue,Hiroshi" <hinoue205@gmail.com>,
 pgsql-odbc@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000005dc29f060486998d"
Archived-At: 
 <https://www.postgresql.org/message-id/CADK3HHJFd0nnr7xtu1zxsi76Kc1mq5Hj7XrzTeEkxHfgSunF7Q%40mail.gmail.com>
Precedence: bulk

--0000000000005dc29f060486998d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Dave Cramer
www.postgres.rocks


On Sun, 3 Sept 2023 at 19:44, Michael Paquier <michael@paquier.xyz> wrote:

> On Sat, Sep 02, 2023 at 11:19:54AM -0400, Dave Cramer wrote:
> > On Sat, 2 Sept 2023 at 06:27, Devrim G=C3=BCnd=C3=BCz <devrim@gunduz.or=
g> wrote:
> >> Do you have a timeline for these? I can see that there are several
> >> people in the mailing list (not me) to step up the plate and help fix
> >> the issues. Would you consider moving project to Github, so that peopl=
e
> >> can send PR and you can merge them, if you don't have time to fix them
> >> all?
> >
> > I'd certainly be a proponent of moving to github and helping out mainta=
in
> > this.
>
> That would be like a big change, still if that helps in keeping the
> project more healthy than it is now, why not.  From what I can see,
> this driver's development has been let aside.
>

This really isn't a big change. At least I don't see it that way. It makes
it much easier to create pull requests which are significantly easier to
manage than patch files.


>
> Saito-san and Inoue-san have done a good job over the years spending
> cycles on maintaining that.  The question is who could actually take
> care of the basic maintenance of the driver?  I do have a little bit
> of experience with the ODBC code base in the history of the project in
> the 2015~2017 area with its core code and the regression tests as
> VMware was relying heavily on it back these days.  So I could handle a
> few of the compatibility changes to keep the thing able to build and
> pass the tests, but my experience feels kind of limited.  Or it's just
> that everybody has zero experience with it and I'm one with the most
> experience :)
>

I had some experience looking at it, but would take some time to get up to
speed on this. Something I am willing to do. I'm sort of hoping this is
more of a maintenance thing than active development. I'm certainly willing
to pitch in.

Dave

--0000000000005dc29f060486998d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br clear=3D"all"><div><div dir=3D"ltr" c=
lass=3D"gmail_signature"><div dir=3D"ltr">Dave Cramer<div>www.postgres.rock=
s</div></div></div></div><br></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Sun, 3 Sept 2023 at 19:44, Michael Paquier=
 &lt;<a href=3D"mailto:michael@paquier.xyz">michael@paquier.xyz</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sat, Sep =
02, 2023 at 11:19:54AM -0400, Dave Cramer wrote:<br>
&gt; On Sat, 2 Sept 2023 at 06:27, Devrim G=C3=BCnd=C3=BCz &lt;<a href=3D"m=
ailto:devrim@gunduz.org" target=3D"_blank">devrim@gunduz.org</a>&gt; wrote:=
<br>
&gt;&gt; Do you have a timeline for these? I can see that there are several=
<br>
&gt;&gt; people in the mailing list (not me) to step up the plate and help =
fix<br>
&gt;&gt; the issues. Would you consider moving project to Github, so that p=
eople<br>
&gt;&gt; can send PR and you can merge them, if you don&#39;t have time to =
fix them<br>
&gt;&gt; all?<br>
&gt; <br>
&gt; I&#39;d certainly be a proponent of moving to github and helping out m=
aintain<br>
&gt; this.<br>
<br>
That would be like a big change, still if that helps in keeping the<br>
project more healthy than it is now, why not.=C2=A0 From what I can see,<br=
>
this driver&#39;s development has been let aside.<br></blockquote><div><br>=
</div><div>This really isn&#39;t a big change. At least I don&#39;t see it =
that way. It makes it much easier to create pull requests which are signifi=
cantly easier to manage than patch files.</div><div>=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">
<br>
Saito-san and Inoue-san have done a good job over the years spending<br>
cycles on maintaining that.=C2=A0 The question is who could actually take<b=
r>
care of the basic maintenance of the driver?=C2=A0 I do have a little bit<b=
r>
of experience with the ODBC code base in the history of the project in<br>
the 2015~2017 area with its core code and the regression tests as<br>
VMware was relying heavily on it back these days.=C2=A0 So I could handle a=
<br>
few of the compatibility changes to keep the thing able to build and<br>
pass the tests, but my experience feels kind of limited.=C2=A0 Or it&#39;s =
just<br>
that everybody has zero experience with it and I&#39;m one with the most<br=
>
experience :)<br></blockquote><div><br></div><div>I had some experience loo=
king at it, but would take some time to get up to speed on this. Something =
I am willing to do. I&#39;m sort of hoping this is more of a maintenance th=
ing than active development. I&#39;m certainly willing to pitch in.=C2=A0</=
div><div><br></div><div>Dave=C2=A0</div></div></div>

--0000000000005dc29f060486998d--