Gang,
I have just read through all of the Fortress discussion mails. There seems to be 2 major consensus (we can agree on) in there;
1. ECM/Fortress should stay with Apache. 2. ECM/Fortress users should not be abondoned.
I also get the feeling that there are many proponents of Fortress to 'live on', and if that true, we not do that...
I think I am more and more in favour of;
1. Apache Avalon = Component contracts. 2. Place Merlin & Fortress into subprojects of Avalon.
-1
One platform, one specification, one container. Avalon made the two state decision years ago with Phoenix and ECM - and that's not role model for the future. What is clearly desired is:
* transition solutions * migration tools
3. The Fortress gang rally a community around it to show that it is really live and well, and not just "hot air".
Then said community should fork.
Cheers, Stephen.
WDYT?
Niclas
--
|------------------------------------------------| | 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]
