Noel J. Bergman wrote:
Wouldn't it also mean that more resources was coming here?? And I don't
only
mean "Howard" (I assume the original author), but also the "user base"
of
which some will dig in...
The Avalon project has already seen a devided development
which really hurt us. That is why we are trying to focus
on one way of doing things, and evolve that.
... "and evolve that." Stephen, for example, has said that Merlin is
designed to be not just a container, but a means for building containers.
He has said that there are aspects of HiveMind that he likes, and would like
to build into Merlin. For that matter, there is possibly some code in
Phoenix, e.g., JMX related, that could be moved over to Merlin.
So I get back to the question of whether there aren't good opportunities for
collaboration and merger of the communities.
I believe that there are. In another mail, I stated that in order for the
two communities to mesh, there has to be something done in both communities.
We have to make a conscious effort to educate each other on what design points
are different and why those choices were made. During this education time,
we can't get defensive if someone disagrees with a pet concept/implementation.
So would it be in everyones best interest to evolve Merlin to support HiveMind
style components--at least as much as can be reasonably done? I think so.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
