Given the project is inviable under Apache rule (3 active committers et al), I propose AvalonDB should go to SourceForge. The same viability rules govern db.apache.org as they do here. It will of course respect the wish that Avalon as a brand/package name is dropped. It will credit its roots in a footnote though.
I look forward to welcoming committers to that projects (ye all have SF IDs right ;-)
I'll wait a couple of days before the CVS removal, because the for overwhelming vote in favor of a move was not explicitly for a move to SourceForge.
Comments..... ?
Regards,
- Paul
Noel J. Bergman wrote:To be clear, when I said "there seems to be some feeling that there isn't
much interest in it", I meant AvalonDB. I was commenting on what was said
here, not asking about the health of db.apache.org.
Ah, didn't get that. sorry.
I wasn't suggesting anything, I was just pointing out an information that might not have been available here.
One thing is for sure, AvalonDB is not in scope on this project nor happens to have a healthy development community (no offense, please, just stating the facts).
As long as it doesn't abuse the name "avalon", I'm happy to let it go whereever its developers think it's best. db.apache.org might be an option they were not aware of, so that's why I said something about it. That's all.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
