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.
Cheers, Steve.
Berin Loritsch wrote:
Development Plan 1:
We continue to support our existing projects while we start fresh
on a new effort. The new effort will be a scalable container that
follows a "profile". Basically the container will only use the
features that are part of that profile and ignore everything else.
Development Plan 2:
We adapt our current projects to the three/four tiered approach
(Tutorial, Micro, Standard, Enterprise). This is probably an easier
migration path, and it would leverage the existing code that we
already have.
-- Stephen J. McConnell
OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
