cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diana Shannon <>
Subject Re: [docs] opensource and quality control
Date Wed, 15 May 2002 10:31:58 GMT

On Wednesday, May 15, 2002, at 05:20  AM, Stephan Michels wrote:

> The best way to do this, is to implement the CVS support in cocoon.

But you still need some form of webapp front-end to address all CMS 
concerns. CVS versioning is insufficient, IMO.
> I were glad to see a CVSSource and a CVSSourceFactory, but if it too
> difficult to map the parameters like revision, cvs repository, and file
> into an URI, we could implement this into a generator and transformer?!
> Something like this
>  <generator src="src/documentation/xdocs/overview.xml">
>   <parameter name="cvsroot"
>              value=":pserver:****"/>
>   <parameter name="password" value="****"/>
>   <parameter name="revision" value="1.2"/>
>  </generator>
> And the combination with slash-edit were ultimative ;-)

I agree. The sooner Forrest has a community-based CMS component, the 
better. Just think how wonderful it would be, to build in community 
contributions at the moment software is released (or before). Perhaps 
you might consider joining Forrest to work on building this dream ;).


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

View raw message