Stefano Mazzocchi wrote: <snip/> > We are also planning to start using Forrest to build our own > documentation, even if this will make it a circular dependency (cocoon > depends on forrest and forrest depends on cocoon). But this is something > the cocoon documentation team will decide with the forrest developers > (most of which are also cocoon developers). > <snip/> > > As a special note, I would like to mention how the introduction of the > Cocoon wiki (hosted personally by Steven Noels' web site > www.cocoondev.org) has been seen by the user community as a great tool > and has generated very high-quality and useful documentation. The cocoon > wiki was also patched to sends diffs to the [EMAIL PROTECTED] > mail list (the documentation team), providing ownership and oversight. > This is seen as a very useful tool by the documentation team.
Would people please stop referring to a "documentation team". There is no such separate thing. All that has happened is that there is a new mailing list where people should be able to discuss issues that are directly related to core documentation. Actually, the cocoon-docs list has had pathetic uptake. Is that because people are leaving documentation to be done by the mysterious "other people"? All developers and users should be helping with building docs. So that means that the documentation team is comprised of everyone, not just those few who have bothered to subscribe to cocoon-docs. *************************************************************** ********** ********** ********** There is no separate "documentation team" ********** ********** ********** *************************************************************** --David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
