On Wednesday 03 March 2004 01:16, Pawel X Karendys wrote: > You can > NOT expect newcomers to start writing a lot of documentation without > knowing well a fairly large framework like Avalon, this approach will add > even more to the existing confusion around this project.
I AM very well aware of this. As I said, the trick is how to make "documentation more central" to project development. Aaron is working really hard to fill endless holes. Stephen wants to drop everything that is not documented (and that is quite a lot in Avalon), and only allow for well-documented parts to be released. I am trying to document (to some degree) whatever I modify and add myself to the codebase, because I know it won't happen later. Others are more laxed and mean that it isn't a problem :o( Your feedback, even though it is pointing at problems without really solving them, is welcome since it will fuel the current debate internal among the developers. As for you PP presentation, I think it is by itself a very nice piece of work, and definately very valuable to the Avalon Community. I saw a few mistakes, perhaps some misundertstanding, and I/Aaron will get to these in due time. If you have the interest in putting in as much effort for Merlin as you have done on ECM/Phoenix/Fortress, but feel you don't understand, I want you to know that I will supply you with any details you require. It is easier to communicate that over ICQ, and I am on #7643698 almost all the time. As for putting the PP on the Avalon site, I think it is just a matter of committing it into CVS and update the site. I doubt there is any need for legal procedure... Cheers and thanks again for a great presentation. Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
