On Tuesday, February 18, 2003, at 03:56 AM, Steven Noels 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.This was based on very helpful advice Nicola Ken provided me off-list as I was working on the transition. Because the Forrest transition work was a WIP, it seemed inappropriate to place them in Cocoon's CVS. Given the fact that Forrest's ability to mount "external" xdocs is fundamental, it seemed appropriate to place the transition files there.
Also, I figured a mass-convert to the new format would make it easier to start the clean-up work.I guess I don't understand what you mean by a mass-convert. We've already done that, haven't we? All that remains are tweaking a few configuration files. Have you tried using the existing files David and I developed?
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.I find it a PITA to have to update my HEAD **and** release cvs branches for simple document updates. It's frustrating to have doc updates dependencies on a HEAD branch that doesn't reliably build. I think a separate CVS branch/block/module would be a definite improvement of the existing situation, but I still think Wiki should remain the way a majority of people contribute/patch docs. In fact, I think we should consider moving all existing Cocoon docs straight to Wiki, so people can patch them there. I proposed it early, when Cocoon's Wiki started, but I backed off, given the fact it looked like a way to run around Forrest -- which I didn't want to do. However, now with Wiki's increasing integration to Forrest (and Steven's ideas of converting wiki docs via site.xml or similar), it makes increasing sense to me.
Diana
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
