Nicola Ken Barozzi wrote:
> Here is my proposed action plan.
>
> 1) Merlin/Fortress people do not commit code to the Phoenix CVS that
> is about Merlin/Fortress stuff. Phoenix is in beta IIRC, and things
> are already fixed. Let's get on with a release.
>
> 2) With the help of Paul Hammant, Peter Royal & friends we start a
> *profitable* discussion about what Merlin has to give Avalon, what the
> proposed new DTD gives, and get an agreement to a common DTD.
> Since we already have now two Containers (Merlin/Fortress in dev and
> Phoenix stable) that can use Cornerstone, and since Peter Donald seems
> to be going in the same direction of deprecating Blockinfo, we finally
> can lay out the one and only Avalon Component Spec.
>
> 3) We write documentation on how to use Merlin/Fortress in Phoenix.
> I want to be able to run a Merlin/Fortress App in Phoenix, and I think
> it's really possible.
> What the Merlin/Fortress integration is showing is that instead of
> three containers we can simply a layered container: Phoenix contains
> Merlin contains Fortress.
> With Fortress and Merlin there is overlap that is being overcome.
> We'd have to do it with Merlin/Phoenix too.
>
+1
This is a practical and workable plan.
Let's do it!
Steve.
--
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]>
