Responding out of order. Berin Loritsch wrote: > > Get off your high horse on this.
Relax. I give everybody the same hard time. My goal is simply to get more people to work together. It is also worth noting that my level of participation in Avalon and Commons is roughly the same. > I am still trying to convince the Axis group that it is more beneficial to > use a tried and tested architecture instead of reinventing their own--which > is frustrating as hell. I can't *make* them do it, but I can *help* them > do it. Note that this is the same Berin Loritsch who is concerned about depending on componentry outside of the Avalon family due to perceived loss of control. > Could you more expound on these fears toward Avalon that you are aware of, > since I was honest and forthcoming enough to share the ones I have toward > Commons? There are quite a few projects under the Apache umbrella that I see as simultaneously unwilling to depend on others, and puzzled that more people are not willing to depend on them. > Do I want to increase the Avalon community? Definitely! I don't see how > moving Avalon code outside of Avalon increases *Avalon's* community. I can > see how it increases *Commons* community. Sigh. Turbine and Struts are generally polar opposites, but at least they can share a set of collections classes. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
