I personally would prefer if we could keep Fortress somewhere at Apache. Apart from other things (visibility etc.), I would like to keep the current package names for compatibility. I guess if Fortress moves out of Apache this isn't possible.
It it moves outside of Avalon it isn't possible either. The Avalon PMC is responsible for the content in the org.apache.avalon and org.apache.excalibur namespace - period.
And I don't see a real problem having it at Avalon if
we clearly indicate that the "official" Avalon container is Merlin bla bla.
Agreed.
As far as I am concerned the entire subject of "where should Fortress go" is completely academic. There is still work needed in getting the fortress suite up to spec. in terms of build, gump, etc. Independently of that anyone can fork the code base to anywhere - but reality is that the codebase is getting attention from the yourself and the core developers - and anything outside of Avalon is *not* going to get the same attention in the short term.
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
