Gunnar R|nning <gunnar@candleweb.no> writes:
> Other things that might also help is consider the structure of the
> project. Maybe one should create a JDBC subproject where latest and
> greatest information abut JDBC is available. Having a mailing list
> dedicated to JDBC could be step in this direction, but FAQs, status
> information, todos, etc. would also be helpful. The idea is to create a
> "subcommunity" of PostgreSQL for the people interested in JDBC.
My two cents: I think there are already more than enough Postgres-
related mailing lists. I recommend keeping JDBC discussion on the
pgsql-interfaces list for now. When and if it threatens to overwhelm
other discussion on -interfaces, that'll be time enough to establish
a separate sublist --- but for now, I fear that'd just cause unnecessary
fragmentation of the discussions and the community.
But I do agree that it'd make sense to set up an identifiable website
and separate CVS server for JDBC, because there's no real good reason
to tie JDBC release cycles to release cycles of the core Postgres code.
There have already been some off-list discussions of this idea...
regards, tom lane
