> > One slight suggestion: let's create a CVS branch of Merlin instead of > > pushing things off into the sandbox. This way our focus will be to > change > > > Merlin for the better presenting these ideas. Then coming to a > consensus > on > > the feature and injecting it back into the trunk. > > I disagree. > I think that we should first know where we are, then we can go with a > clear > direction of refactoring merlin or whatever we choose in the future. > > Lets first agree/have a common denominator, then we decide what to do with > it.
You have some valid technical points. My reason for suggesting this approach is two fold and revolves around community dynamics here as well as code. First it makes others get more involved with Merlin and makes Merlin people try to understand the ideas of others. That leads to more communication, dialog and hopefully more comradery. Secondly let's not freak people out into thinking yet another container effort is underway or there is potential for one. People should not give in to the fight or flight response thinking yet another effort is going to occur instead of refining the current one. Don't forget the social engineering tasks in front of us are much harder to deal with than the code which in my opinion is trivial. With this perspective on the situation I hope you agree if not I ask that you at a minimum entertain the idea since it's really not much of a big deal. Or is it? Thanks in advance, Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
