Noel:

I'm going to attempt an answer without getting trapped into an acceptance of the rationality of the question.

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.). 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. 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.

Stephen.


Noel J. Bergman wrote:
I don't view either the Components or the Framework as legacy


Neither do I.  And Stephen's reply was similar to yours.  None of us think
that the word "legacy" is a good choice.

OK, other than the use of the term "legacy" (yeah, like that's the first
time a word has been poorly chosen ;-)), what other issues do you have with
the proposal that Peter, Aaron and Stefano are discussing?

Please be more concrete than "solutions that are based on proper management
of the documentation to properly reflect the realities of the past and the
realities of the present."  Extra points for demonstrating clarity with
brevity.  :-)


How about giving the team some time to produce alternative views
of the site to see if we can come to some agreement and consensus.


Is your view of the "team" broad enough to realize that Peter is part of it?

        --- Noel


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--

|---------------------------------------|
| Magic by Merlin                       |
| Production by Avalon                  |
|                                       |
| http://avalon.apache.org              |
|---------------------------------------|

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to