Currently, we have three community concerns:

1. Support our Users
2. Work together
3. Create kick-a** stuff and have fun.

These are goals that I think we can all agree to.  Our actual positions (to
borrow Leo's terms) have been the points of contentions and causing us to
fail on two of our community concerns.

So keeping in mind *all* three of our concerns (goals) above I suggest the
following course of action:

1) We do a quick beta release of Merlin.

1) We outfit Merlin to support Phoenix users and Fortress users.  I believe
   90% of the hard stuff has been done.

2) We release Merlin as our one container for current users.  I.e. Avalon
   Container codenamed "Merlin".

Why Merlin and not Fortress or Phoenix?

Primarily because most of the work to support our users has already been
done in Merlin.  Fortress would have much too far to go to support Phoenix
components, and Merlin can already host the most used features/components
for Phoenix (i.e. it can run JAMES).  The only things required to make
Merlin fully Phoenix/Fortress compatible is to incorporate the other container
specific code as compatibility modules.

The proposed course of action will provide one container codebase for us
to support our users, and then we can naturally divide our efforts as we
see fit.  Some of us are refactoring fiends and like the guts of stuff to
be clean and well understood.  Some of us are more into components.  Others
like to try some completely new ideas.

WIth our current users supported--through a container compatible with Phoenix
and Fortress--we don't have to actually have the Phoenix and Fortress code
around forever.  We can start having fun with a nano-kernel/container-container
approach.

I give my word not to try to control development, and we can start having
fun again and address all our community concerns listed above.

Thoughts? Am I off my rocker?

--

"They that give up essential liberty to obtain a little temporary safety
 deserve neither liberty nor safety."
                - Benjamin Franklin



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to