Henri Yandell wrote:
To repeat my objections slightly more in full:
I think commons-sql should become db.apache.org/sql or some new name. Unless there are a lot of components at db.apache.org; I think we should be careful before kicking another commons repository into action and increasing confusion.
You're right, and as I already said, for us the name is not important at all, nor the place in db-commons. All we would like to achieve is that commons-sql will be moved to db.apache.org. We don't want another commons repository in db.apache.org, we only saw that db.apache.org/commons is present but vacant. There is no problem to define a new name for commons-sql, though the db-commons place should probably be closed, as well.
If the commons part is really important, but being inside Jakarta is a problem, I think we should start thinking again about asking for TLP for Jakarta Commons, bringing Xml Commons into it and dealing with the growth/scope issues as they happen.
I agree that this would be a useful and necessary thing to discuss, but could we split that from this vote please ?
regards, Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
