I don't follow your entire message, I don't know about developers "protecting code" issue and I suspect it was a "backstage's talk".
But as you wanted opnions I would like to say that I (and I don't know if I'm speaking only for myself) don't know how to help. Avalon# for instance should be a concrete implementation of a container, or should be the framework from which someone will develop a Fortress#, Merlin.net, etc? I could claim for a document but I don't believe in this approach. Talking is the most clever way of handle issues/doubts. As a personal opnion I think I - and a lot of silent readers - could help more, but seems that not everyone would like contributions. To me should be great to be part of a team that builds so powerfull projects and I'll be proud for each line of code, or each design suggestion that I'd give. hammett MCAD Meet Polyethylene at http://polyethy.sourceforge.net/ ----- Original Message ----- From: "Berin Loritsch" <[EMAIL PROTECTED]> To: "Avalon Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, July 30, 2003 1:44 PM Subject: [RRT] Getting back to the basics (long) > RRT = Radical Random Thought > > The body of this entire RRT includes my views on the subject, but that does not > mean we all agree to it. The bottom line is that as long as we have code that > certain developers feel they need to protect from other developers we have no > basis for cooperation. One way to address this issue is to equalize the playing > field and put everyone in the same boat. Another way to address it is for us > to put down our pride and learn to work with everyone here. Nothing is sacred. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
