At this point I think it would be futile to start up a new effort and port features to a container framework.
can you summarise why? (in a different thread, perhaps)
So, what is the next best thing? IMO, it is picking ONE of the three containers we have and we all work on that, evolving it as necessary.
I agree that is the next best thing. But I must tell you, I strongly feel like moving away from the avalon lifecycle at this point. I also have an idea how to do that in a non-radical way.
What would be preferred?
* Fortress
> * Merlin > * Phoenix
IMO: Fortress. Based on that it is the smallest code size and has the smallest public api, hence the most room for evolutionary extension.
Does this sound like a decent plan of action?
I am not sure. It sounds like a reasonable compromise between all the other options we've talked about so far. Concern: I'm wondering whether this will generate the positive energy we need: working on new code is usually more fun (again, IMO) than working on existing code.
cheers,
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
