On Fri, 2002-11-15 at 10:08, Stephen McConnell wrote: > Leo Simons wrote: > > >On Fri, 2002-11-15 at 08:48, Stephen McConnell wrote: > > > > > >>Maybe it would be a good idea to include in this document some links to > >>some of the other Avalon containers. The current content suggests > >>Phoenix as a starting point which is a little like learning to swim at > >>the deep end of the pool. It could be interesting to reference Tweety > >>and the entry point, followed by Merlin and Fortress dealing with cause > >>grained components, and wrapping up Phoenix at the application level. > >> > >>Thoughts? > > > >I don't really like it. I feel our documentation should point to > >released and easily downloadable software; atm, the only containers with > >that status are phoenix and ECM, and I feel it is a good idea to not > >stimulate usage of ECM. > > Totally agree on the ECM point - however - I concerned about the very > high learning curve the Phoenix represents in terms of an entry point.
yup. It's got a bit of an 'enterprise' feel to it doesn't it ;) > Ok - on Fortress and Merlin there isn't a trealease status for good > reasons. On Tweety I think the scenario is different bacause I don't > think Tweety should be released - it should be part of the getting > started with Avalon walk though. I.e. is about eduction and delivering > concrete examples. Does the publication of good informative and > eductional content require that we go through a product release > procedure? Surely not. my idea here is that a release cycle makes sure everything is bugfree. Also, tweety is so far a model example of the way development of an avalon component can go and the release thing is only part of that. > I'm in favour of making things understandable based on useful examples > and demonstrations. me too. I'm kinda stuck in my avalon-for-beginners howto though. I think the approach I chose is wrong and am reworking to do things more concept-by-concept. The example application for that should be something real like infomover :D help welcome........doc-writing is hard....... cheers, - Leo -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
