Leo Sutic wrote:
-----Original Message-----reusable
From: Stephen McConnell [mailto:[EMAIL PROTECTED]
In addition, as a project is it dedicated to pushing back core
technologies into a common container architecture - something that impacts everyone here.
This is a good goal - try things out in separate containers and then merge back the code into the core.
The problem is that such merges often take on the form:
"This code works well in X. So we'll just put it in the core as it is, and no changes are allowed."
Instead of looking at the concepts of that code, and, allowing it to change, get merged into the core:
"These ideas works well in X, let's see if and when and in what form we can get them into the core."
I think this was what caused the last eruption.
Historical correction:
Lots of changes were mode to code in question as part of moving it out of Merlin and into Avalon Meta to accommodate everyone’s interests. A lot of time was spent refactoring the Merlin base to incorporate those changes. One particular proposal for change by Berin was block by veto from me on the grounds that it would be detrimental to the object model. If Berin really things that his proposed change must go through - then he can fork the project, pull a community around the fork, and propose something different. Alternatively, he can relax a little and accept that there is a perfectly good solution that meets 90% of needs. That's a decision that Berin needs to make.
Maybe we could let this drop. I think its been thrash over more than it deserves. Apache have rules about this sort of stuff. Lets respect those rules and move on.
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
