You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by si...@avalon.apache.org on 2004/03/17 19:20:09 UTC
[Apache Avalon Wiki] Updated: AvalonStandards
Date: 2004-03-17T10:20:08
Editor: AaronFarr <fa...@apache.org>
Wiki: Apache Avalon Wiki
Page: AvalonStandards
URL: http://wiki.apache.org/avalon/AvalonStandards
added leo's email response. hammett has a good memory -farra
Change Log:
------------------------------------------------------------------------------
@@ -6,6 +6,30 @@
* Build consensus on a set of standards which will be held by all Avalon containers (ie- a TCK)
This is not an attempt to build from scratch new standards. It is an attempt to identify existing approaches and develop a responsible way to both support our existing users (via backwards compatibility or migration tools) and to offer a consistent platform for the future of Avalon.
+A reminder of how to approach this process: http://marc.theaimsgroup.com/?l=avalon-dev&m=105965430911547&w=2
+{{{
+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.
+
+If anything, this is what we need to work on. Learning not to lock
+ourselves into our own idea just because we like it the most.
+
+/LS
+}}}
+
== Standardization Areas ==
''Niclas, you had a list at one point...''
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org