Stephen McConnell wrote:
I completely share this view.
My preferred position is to go with plan [1]. While I think that is the worst-case-scenario concerning "Merlin",
"Fortress", or "Phoneix" centric product development, I also think
it is the only scenario for a community owned solution.
I do believe that plan [1] will enivatibly involve pulling the best of
existing containters and container related resources together, and
in that respect I see the potential for something much more valuable
comming out of the process.
I do not see this as conflicting with ongoing requirements concerning
support of the Phoenix commuity - in fact this is similar to the
requirements we have for supporting ECM user migration. End result is
the migration of all of our users to a single common container
architecture - a.k.a. everyone wins.
Note that Stephen is implying that Avalon identity is more important than its container's.
This is the attitude I like to see.
--
Stefano Mazzocchi <[EMAIL PROTECTED]>
--------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
