> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > > Personally, I am not sure why the Avalon Community, which is > now a TLP, > doesn't want to foster common components such as AvalonDB. But if the > Community doesn't want to support AvalonDB, so it is going to > move, I'd just > as soon as soon see it move to someplace like tigris (axion is already > there, which might be fertile ground for collaboration) or > krysalis, where > there is an "Apache adjunct" community.
AvalonDB isn't a component, but a server or application--much the same way JAMES is. As such, it doesn't really fit the charter of what we do. I am sure that the whole community has mixed feelings about the move. I believe the current consensus is to move it to the Krysalis project. In the end, I think it will be better for both communities because AvalonDB has been languishing for support. By exposing it to a new community it might pick up new developers. By taking it from this community we can put the focus on what we need to. I really hope that what I think does come true. I personally would love for us to have the greatest native Java database, but in the end, the community is just not at a place where it needs to be to support such an application. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
