On Monday, October 21, 2002, at 05:26  AM, Tim Bunce wrote:

Frankly I doubt it's practical to be a DBI driver developer without
being on the DBI driver developer mailing list.
I think this is true, and in discussing this issue with Bruce, I realized that there was a mistaken perception about the role he wishes to play in the continuing development of DBD::Pg.

Bruce created the GBorg project for DBD::Pg so that there'd be easy CVS access for interested parties to download the source and make patches, not to take over development himself. My understanding is that he's more interested in being a kind of administrator for DBD::Pg while allowing others (i.e., dbi-dev folks and interested DBD::Pg users) to continue development in a collaborative manner.

I think that part of the misunderstanding comes out of the different cultures of the PostgreSQL and Perl communities. The PostgreSQL developers have no maintainer, no Pumpking, no Poobah. They work together on issues that interest them, come to consensus, and then commit changes. This is the kind of approach that Bruce wants to encourage for DBD::Pg development, in part to get away from DBD::Pg's historically slow development under a single developer who might lack the time to respond to patches and get out new releases.*

So I'd like to propose this plan going forward: All patches and discussion of DBD::Pg should continue on dbi-dev, Cc'ing Bruce and/or the PostgreSQL interfaces list when it makes sense to get feedback on our use of the PosgreSQL API. Once consensus is reached with regard to proposed patches and development directions, someone with commit access to the CVS repository will make the necessary commits (a list of such folks is on the DBD::Pg GBorg page, http://gborg.postgresql.org/project/dbdpg/projdisplay.php?172). And again, when consensus comes together that we're ready for release, I'll function as a release manager of sorts, create a distribution, and upload it to the CPAN. Bruce will announce releases and such on the GBorg dbdpg-general list.

Ultimately, I think that this approach will facilitate future DBD::Pg development, because many more people can now easily participate and, as a PostgreSQL core developer, Bruce can offer a wealth of knowledge regarding the the PostgreSQL API.

I hope that this clears things up enough that we can all work together to make DBD::Pg the best written, best-supported DBI driver on the CPAN.

Regards,

David

* This is not intended as a slam against the previous DBD::Pg developers -- hey, we owe it to them that DBD::Pg exists in the first place! Thanks, guys!

--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]


--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]



Reply via email to