cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: closing cocoon-docs? (was: Cocoon Project Report)
Date Tue, 18 Feb 2003 05:06:33 GMT
Steven Noels wrote:
> Sylvain Wallez wrote:
> >David Crossley wrote:
> >> Actually, the cocoon-docs list has had pathetic uptake.
> >> Is that because people are leaving documentation to be done
> >> by the mysterious "other people"?
> >>
> > 
> > So what about closing cocoon-docs ? This would avoid believing some 
> > mysterious entities are writing the docs for us...
> 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:
>   - 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.

We do need a better foundation for future doc development.
However, i do not think that we need separate versions of
docs for different releases. A consistent note in each doc
about which version it relates to, might be better.

> 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*

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.


To unsubscribe, e-mail:
For additional commands, email:

View raw message