David Crossley wrote:
Sure, David - fully aware of that. My 'big hidden agenda' (duh) was to add a first step to the main cocoon build, so that others could jump in and expand. That doc makes reference to a trail-run-F target which was buried somewhere in Forrest and since it is only of limited concern to Forrest, I wonder why it should be there. Also, I figured a mass-convert to the new format would make it easier to start the clean-up work.I thought that "square one" was working out the proposal to use Forrest to process the Cocoon docs. That conversion from docv10->docv11 is a part of the process. http://wiki.cocoondev.org/Wiki.jsp?page=ForrestProposal
On the subject of a separate CVS repository & getting rid of branches for maintaining versions of documentation, this is a personal feeling. For developers who want to maintain documentation, checking out a separate module isn't a big burden, and it would also allow us to give pure-documentation-people CVS commit access. I think splitting out things will provide people with a cleaner (less daunting) work environment. That's at least what the Wiki is teaching me. All IMHO, of course.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
