Re: JDBC 4 Compliance - Mailing list pgsql-jdbc
From | Andreas Joseph Krogh |
---|---|
Subject | Re: JDBC 4 Compliance |
Date | |
Msg-id | OrigoEmail.14b.aa508b773eb7f688.13f7b9c551b@prod2 Whole thread Raw |
In response to | Re: JDBC 4 Compliance (Dave Cramer <pg@fastcrypt.com>) |
List | pgsql-jdbc |
<div>På tirsdag 25. juni 2013 kl. 15:44:49, skrev Dave Cramer <<a href="mailto:pg@fastcrypt.com" target="_blank">pg@fastcrypt.com</a>>:</div><blockquotestyle="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">Here's the way I see this from my POV. <div> </div><div style="">First someperspective. </div><div style=""> </div><div style="">There are approx. 5 people actively participating in this discussion.1000's of other people are happy just downloading the driver. In my mind they are the market.</div><div style=""> </div><divstyle="">Now some reality.</div><div style=""> </div><div style="">I have been maintaining the driversince around 2000. Since that time others have contributed greatly. Namely Kris Jurka and Oliver Jowett stand out aspeople who have stepped up in a big way and in fact taken over much of the work when I was unavailable</div><div style=""> </div><divstyle="">At the moment I am the only one left. I have never been paid for any of this. I am not expectingto, but this reality means that I have limited time to work on it.</div><div style=""> </div><div style="">Otherthan Kris and Oliver, there have been others who have expressed interest in donating their time and effort,for whatever reason they do not remain active. </div><div style=""> </div><div style="">In the case of Kevin's 10month old patch Craig Ringer originally reviewed that patch and I left him in charge of it. As a result it became staleand Kevin decided his time was better spent writing a whole new driver. </div><div style=""> </div><div style="">Inmost open source projects people get involved slowly. Patches which involve large changes to the codebase arenot accepted by people who are not going to take future responsibility for them. </div><div style=""> </div><div style="">Keepin mind that I have considerable knowledge of how the code works right now. If I were to accept a huge change,then I become responsible for it. Unless I see some continued commitment from someone how do I know they will continueto be responsible for this new code ?</div><div style=""> </div><div style=""> </div><div style="">Moving forward.As I see it the number one problem is lack of resources. Instead of opting for wholesale change the project needsresources. Someone else to review patches, someone to work on the website. Someone to deploy to maven.</div><div style=""> </div><divstyle="">Anyone feel like volunteering ?</div></div></blockquote><div> </div><div>As a developer, amongthose other 1000s of people, having used PG from JVM-based languages for the past 13 years I'm really starting to missbetter support for UDT and BLOBs. As development seems to have stagnated in the standard-driver I very much welcome Kevin'snew driver (impressive work man!) and hope it will be the start of "pgjdbc-NG" driver.</div><div> </div><div>Thereare a lot of people who don't care for JAVA < 7</div><div> </div><div class="origo-email-signature">--<br/> Andreas Joseph Krogh <andreak@officenet.no> mob: +47 909 56 963<br /> SeniorSoftware Developer / CTO - OfficeNet AS - http://www.officenet.no<br /> Public key: http://home.officenet.no/~andreak/public_key.asc</div><div> </div>
pgsql-jdbc by date: