commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin van den Bemt <>
Subject Re: [Vote] Moving commons-sql to (repost)
Date Tue, 14 Dec 2004 18:03:49 GMT
Although I hope I can still have karma on it..
I am pretty much moving towards a big dependency on commons sql, with
almost all my projects. Since sql is a far from finished item, I only
chose it because I had the karma to actually change things that were not
finished (or broken).
Let me know :)


On Wed, 2004-12-08 at 21:32, Thomas Dudziak wrote:
> (This is a repost from a vote that I started earlier today, but where I 
> did not include commons-dev. This omission has been pointed out to me, 
> and I agree that including commons-dev is important, so I repost the 
> vote hereby)
> Hi all,
> I'd like to start a cross-vote (Jakarta PMC and commons-dev, DB PMC) 
> about moving the jakarta sandbox project commons-sql 
> ( over to, 
> for instance into the currently vacant db-commons space 
> (
> The reasons why we want to move commons-sql, are twofold:
> * The two active committers (Martin Kalén and myself) are DB comitters, 
> but not comitters to another Jakarta project. As a result we would 
> rather not subscribe to commons-dev/commons-user because very few mails 
> there deal with commons-sql (one or two per month). Also, db-commons 
> already has all setup'd (mailing lists, CVS space etc.), not to mention 
> that the exposure of the project would be much greater.
> * No other Jakarta project that I'm aware of, uses commons-sql. In 
> contrast, OJB will do so (beginning with the upcoming 1.1 version), and 
> so it would be good to provide access to the commons-sql repository to 
> the OJB comitters. The same might also be true for Torque as 
> commons-sql's functionality overlaps in some parts with Torque 
> functionality, which opens up an opportunity to combine this 
> functionality into a base component which both OJB and Torque could use.
> Please post your opinion until next wednesday, the 15th of december, and 
> please reply to all recipients.
> Votes cast so far:
> +1 Brian McCallister
> +1 Henri Yandell
>     (though with objections regarding moving it into db-commons,
> +1 Henning Schmiedehausen
> regards,
> Thomas Dudziak
> PS: I'm not sure if this is the correct procedure, but I thought a vote 
> is at least a good way to get the ball rolling, so to speak. If there is 
> a defined way to handle movement of projects, then please let me know.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message