> -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > > > What if that person and his friends choose to bring all > > their enthusiasm and energy to a new fortress top-level-project? > > What if they expect to be able to change Avalon-Framework, and > > find that some of the developers of that framework are not even > > on speaking terms with some of the fortress people?
Leo, How does moving to Codehaus.org as opposed to another project in Apache solve this problem? Won't you have the same issues? Or is the understanding that if ECM/Fortress moves to Codehaus there will be no expectation of changing the Avalon-Framework? > If there is to be any hope of having any degree of compatibility, then > this issue must be addressed. Otherwise, just take the code, fork it, > change its name, and do whatever you want with it but it cannot be Avalon > if we give up on some concept of what that means. Peter Royal and I were > just discussing this issue on the PMC list in response to yet another > posting there on this topic. This is a matter which will have to be solved regardless of any containers staying in Avalon or moving out. In other words, it's a separate issue from moving Fortress and I don't believe solving it will completely remove the motivations for Leo et al.'s proposal. Imagine, if you will, that we come out with a complete set of specifications for Avalon as suggested by Niclas. Would that suddenly alleviate the problem? Would Leo's Gang be willing to drop suggestions of a fork and join development in Avalon? Would Stephen support continued development of another container thus making Avalon a single platform (via the specs) with multiple products? > I just posted my consent for Peter to post our discussion on that private > list to this public one. Basically, though, there appears to be an > agreement and a desire to have a defined set of contracts, which does mean > that wherever the containers would be hosted, we MUST address your concern > above (which is not just your concern, but also shared by others). As you said, regardless of "wherever the containers would be hosted" the issue of Avalon compatibility needs to be addressed. The question for us right now is will "wherever" be Avalon? Will we allow continued development of multiple containers? Stephen? jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
