Subject: Re: ruby-postgres module needs work, maintainer
From: Jeff Davis <pgsql@j-davis.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: "Joshua D. Drake" <jd@commandprompt.com>, pgsql-interfaces@postgresql.org
In-Reply-To: <200701252018.l0PKIhd15596@momjian.us>
References: <200701252018.l0PKIhd15596@momjian.us>
Content-Type: text/plain
Date: Thu, 25 Jan 2007 14:10:45 -0800
Message-Id: <1169763045.20694.147.camel@dogma.v10.wvs>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Thu, 2007-01-25 at 15:18 -0500, Bruce Momjian wrote:
> > ruby-postgres != plruby
> 
> Oops, sorry.  I got confused.  I also have not heard from the
> ruby-postgres guy, but as a community we are less likely to have heard
> from him because interfaces are more independent.
> 

I finally did reach the ruby-postgres guy. He said he would incorporate
my patches. 

I'd like a real release (that becomes a gem), because the current ruby-
postgres release is not sufficient (in a number of ways), and I got at
least one response from someone who literally skipped PostgreSQL support
in their app because of it:

http://groups.google.com/group/comp.lang.ruby/msg/450c15cb3848129b

I expect there will be more patches also. Hopefully we can get this up
to speed.

I've been informed that the Ruby community's gem releases are heavily
dependent on rubyforge. Without involvement of the rubyforge ruby-
postgres project, releases would have to be under a different name
(which would mean changing client code -- not desirable). This is my
understanding, anyway.

Regards,
	Jeff Davis