Noel, Although we are a database related project, I don't believe we could join db.apache.org without a significant change to what db.apache.org means.
db.apache.org has its own PMC, which (AFAIK) has no knowledge of iBATIS, nor would we want to impose such burden upon them. iBATIS is a large, growing project with both Java and .NET editions (and soon, possibly a PHP edition). We have a user base that ranges into the thousands and active mailing lists and issues that require the attention of an involved and experienced PMC. We do not mind being "organized" under db.apache.org domain name, if that's all it means. I'm a fan of organizing Apache.org into broader categories, while maintaining independent project control. However, if it means sharing a PMC, source control, mailing lists, website and other key resources, then I'm afraid that simply will not work for our community. As it stands now, my (totally non-binding) vote is an enthusiastic -1. Best regards, Clinton Begin On Mon, 28 Mar 2005 22:41:18 -0500, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > Ted, > > It seems appropriate to graduate, but should iBATIS be a TLP, or go under > db.apache.org, along with Derby and related Jakarta Commons code that has > been moving, in your opinion? > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
