>As for the general usefulness of a wiki, I agree that the format may not be >as pretty as the main website (or PDF documents); however, I would rather >have some documentation than none. The wiki allows myself and others >(ANYONE!) to create tutorials, answer questions, etc. Right now I'm most >concerned about capturing the documentation and getting it out there >faster. >Then I can work on making it pretty and better organized and polishing it.
That's perfect. Gather all the information somewhere and then organize and polish it and put it in regular webpages or pdf or whatever. And also keep the "Developing with Avalon" article in mind. It needs to be updated with the latest concepts of Avalon. Avalon brings lots of new concepts with it, that programmers may not be typically used to work with and one arrow in the wrong direction is all that may be required to frustrate them. Thanks for your efforts, keep up the good work. Vikas -----Original Message----- From: Farr, Aaron [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 02, 2004 10:39 AM To: 'Avalon framework users' Subject: RE: PowerPoint presentation > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > >I don't know too much abt wikis etc but I think pointing a beginner to > the > mailing list archive is not so good. You could very easily get lost. > > I agree 100%. For a true beginner, or someone who is exploring the > technology (comparing vs other solutions etc) they are most likely looking > for an example and description that is well organized that they can print > out. > > There is a wealth of info in the mail archives but sometimes it is mass > chaos and drives people away who might otherwise start trying the > technology. And that was my point too (which perhaps I didn't communicate well enough) -- use the wiki to store useful mailing list posts so they don't get lost in the archive. As for the general usefulness of a wiki, I agree that the format may not be as pretty as the main website (or PDF documents); however, I would rather have some documentation than none. The wiki allows myself and others (ANYONE!) to create tutorials, answer questions, etc. Right now I'm most concerned about capturing the documentation and getting it out there faster. Then I can work on making it pretty and better organized and polishing it. FYI: All Apache wiki's can be found at: http://wiki.apache.org/ http://nagoya.apache.org/wiki Feel free to contribute! J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
