Berin Loritsch wrote:
Stephen McConnell wrote:
<issue>
Concerned has been raised that Avalon Framework has lost visibility on the new web site.
</issue>
Personally, I am willing to either place a "AF4.1" link under Central, pointing to the old docs, or including Framework in the Products column on the home page pointing to the relevant current section of the component specification, i.e. LifeCycle specification and/or the javadocs. PROVIDED, that all this hoo-haa settles down and instigation stops from all sides (I'm glad I'm not on PMC anymore).
I'm ok with putting a AF4.1 link under Central. I'm not ok with Framework under Products. I am also ok with updating existing docs with information that clearly associates versions with sementic descriptions.
Why not Products?
First and foremost its a conflict in terminology:
* A product implements zero or more specifications, is typically used by a user, provides certain features and benefits, and at the end of the day represents a certain value proposition.
* A specification will typically incorporate an api and documentation detailing semantics.
Secondly, it is in conflict with Avalon's objectives - a complete, consistent, and portable component model and reference implementation.
Keep in mind that the framework in isolation does not define a complete, consistent, nor portable component model. Achieving that definition involves a bunch of other things - some that exist, some that don't. But this project is about achieving that objective. In the process we have the responsibility of managing a number of apis that are exposed to users at different levels:
To the component author Avalon specifications of interest include:
* avalon-framework-api#4.2.0 * avalon-util-lifecycle#1.1.1
For developers of component based systems that leverage component management, the area of concern expands to the following:
* avalon-util-extension-api#1.2.0 * avalon-composition-api#2.0.0 * avalon-repository-api#2.0.0 * avalon-repository-spi#2.0.0 * avalon-logging-api#1.0.0 * avalon-meta-api#1.4.0 * avalon-meta-spi#1.4.0 * avalon-logging-spi#1.0.0 * avalon-composition-spi#2.0.0 * avalon-merlin-api#3.3.0
Developers of advanced embedded systems may also leverage the Avalon runtime activation contract:
* avalon-activation-api#2.0.0
A product is a system that provides an end-user solution that is consistent with one or more of the specifications described above. For example, Fortress is a product that for the time being is consistent with avalon-framework-api#4.1.X and probably avalon-util-lifecycle#1.X. Merlin is our reference implementation - a product that implements all of the above specifications.
Is framework a product - no - it's just part of the specification of a evolving component model.
Stephen.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
