Sylvain Wallez wrote:
Naah - I don't know. Even worse, I have been playing with the idea of proposing a separate CVS module for docs, in httpd-docs-style. Stuff to be moved and developed there:So what about closing cocoon-docs ? This would avoid believing some mysterious entities are writing the docs for us...Actually, the cocoon-docs list has had pathetic uptake. Is that because people are leaving documentation to be done by the mysterious "other people"?
- the Cocoon public website
- the docs for the different releases, presumably with each branch being brought in its own directory (instead of being managed using CVS branches)
- the framework for building docs & website, which might as well become dynamic if we can abuse Pier's presence to have it hosted on nagoya.
I know such thoughts can be regarded as debatable, and it's only based on 'belly-thoughts' [BT], but I would bet some Euros on it that this could foster a better documentation biosphere.
The previous week, I wanted to bring in a massive docv10->docv11 stylesheet into the Cocoon build.xml. But that thing is daunting, the Ant 'style' task didn't work as documented, so I was rapidly back at square one :-(
I know I could go and fix things, but the amount of existing loose threads that need to be taken into account is so damn *huge*
</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]
