Berin Loritsch wrote:
As this affects the whole of Avalon, I would like to know your thoughts,
comments, concerns on this subject. If we would like to adopt it as our future
direction, let's do it. If there are any concerns, let's lay them on the table.
We have a charter that states what Avalon is about - "service and component management".
Within that scope there an infinite number of possibilities. However, when we consider community dynamics, the interests of different users, and personal objectives, we see a tendency of people to move towards concepts that interest them. And from time-to-time we move from one center-of-gravity to another. In effect, this represent the migration of interests drawn by the emergence of new ideas, solutions or opportunities.
Here are my thoughts about the big picture from this perspective:
Stop the process of *forced* convergence. -----------------------------------------
* Nobody here wants to be forced to do anything. * Its driving people away. * Its not focussing on needs.
Instead - let thing evolve because this community wants them to evolve. As you know, I'm quite keen on seeing the development here in Avalon of a common containment API but I'm also opposed to the notion of one container. In fact the vision I like is the ability to pull in a container matching your own needs - dynamically. Its a vision with lots of commonality with your own thoughts. But if we put down a rule that said there must one and only one container - we would immediately in conflict. The problem here is that rules force us into directions which we may not want to go. Underlying this is the problem that rules can used to coerce members of the community in unforeseen ways.
Another approach is to encourage and foster the contributions of developers here at Avalon based on shared objectives - and through this, facilitate the evolution of best-of-breed solutions. To enable adventure, good times, and great results.
There are some things we can do to facilitate this:
* get rid of the notion of managing the community (less stress) * introduce a vibrant release process (frequent releases) * encourage experiments (more surprises) * capture and promote the best of breed (recognition)
Cheers, 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]
