On Tue, 2004-06-15 at 18:52, Aidan M McGuire wrote: > It's a good job the Linux community didn't adopt that strategy ;-)
And just about every other successful open source project... Seriously, the code-to-documentation and code-to-test ratios tell you a lot about a project. > > On Mon, 2004-06-14 at 17:57, Andrew Ho wrote: > > On Mon, 14 Jun 2004, Aidan M McGuire wrote: > > ... > > > Documentation is a weak point regarding Zope (although it more to do > > > with the information being hard to find than the information not being > > > there). It's a weak point and there's no excuse for that. > > > > Aidan, > > There are many reasons why the "documentation gap" exists. Simply put, > > it is the distance between available software and available documentation. > > Any mismatch in rate of software change and documentation change lead to a > > change in the gap. > > One general solution is to hold back software release until > > documentation is ready. Another is to write documentation before > > implementation. Either solution is inferior to the status-quo, IMHO. > > > > Best regards, > > > > Andrew > > --- > > Andrew P. Ho, M.D. > > OIO: Open Infrastructure for Outcomes > > www.TxOutcome.Org > > > > -- Tim C PGP/GnuPG Key 1024D/EAF993D0 available from keyservers everywhere or at http://members.optushome.com.au/tchur/pubkey.asc Key fingerprint = 8C22 BF76 33BA B3B5 1D5B EB37 7891 46A9 EAF9 93D0
