Bennett, Timothy (JIS/Applications) wrote:
-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 13, 2004 4:18 PM
To: Avalon Developers List
Subject: Re: [PROPOSAL] End the drama
First off - there is plenty of room for enhancing existing docs that are presented as part fo the mainstream Avalon specification - for example - clearly detailing the artifact version (e.g. framework-api 4.1.3, framework-api 4.1.5, framework-api 4.2.0, avalon-meta-api, 1.1.1, etc.).
Agreed.
However, irrespective of the technical integrity of this approach - it seems to me that some people also want an off-ramp. I.e. a doc entry point to avalon-framework 4.1 that presents the framework without reference to the things like meta, javadoc tags, injection semantics and so on. Both are achievable without compromising Avalon aims and objectives.
I also believe this, and my hope is that it will satisfy both the Avalon traditionalists and the avant-garde, by clearly preserving the Avalon dependency of legacy containers and their customer/developer/client base, and by providing a launching point for an attempt to standardize Avalon component and container development.
There are also really interesting things we can do automatically generate documentation covering the full suite. These and other options can be pursued if the drama goes away. The alternative approach of demands for changes here on this list and on the PMC are not sustainable propositions simply because the members of this community would not be acting in the interest of the community but would instead simply be responding with actions aimed at reducing the noise level.
I've got a different idea. Why don't we stop using words like *drama* and
*noise level* and adopt a different spirit here. Honoring the Avalon
foundation laid by the traditionalists is a good and right thing, and
getting their blessing for the future is also important. Making changes to
how we present things in order to honor the past and get a blessing on the
future is not a waste of effort, but a cornerstone towards future success
IMO.
If I take this suggestion on its technical merit what you are describing is documentation that provides the reference points from the past, the reference points to the present, and the context of evolution - all presented from a clear technical perspective.
If that's correct then yes - I'm right behind you.
Cheers, Steve.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
