As a Cocoon newbie, I totally share your concerns but I'm not sure that it is necessary to stop coding while writing documentation. But it would be great if there were two teams, one for coding the next version and one for writing the documentation, with a few Cocoon experts (the ones who know the system the best) to synchronize efforts between both teams. Or even for each block for example, there could be coders and documenters working in parallel and talking with each other to keep documentation and code in sync.
But whatever the solution I think that the key is organization (something that is not easy to achieve in Open Source projects :oS ) and that one should avoid alternating coding and documenting because documenting is (by experience) not very agreeable, and all the less so when you have to write new documentation for great bunches of code. And this is a debate that would fit both dev and doc mail lists as it's a matter of coordinating both kinds of efforts. But maybe this organization still exists... Does it ? On Apr 12, 2005 12:44 PM, Nicolas Maisonneuve <[EMAIL PROTECTED]> wrote: > Hy, > > I would like to know the state of the documentation effort. > Actually I'm afraid that after the development the new documentation > system (another excuse for not beginning the documentation ;-)) , > there won't be a real effort to build a new documentation (= all > committers will stop to code et will create a good documentation) > > Nicolas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Sebastien ARBOGAST --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
