On Sun, 23 Mar 2003, Stefano Mazzocchi wrote: > As I think most of the people here knows, Forrest is a Cocoon spin-off > project that focuses on static-snapshots of publishing-intensive web > sites with complex needs. > > Cocoon now self-generates its own static website, but given the amount > of time/effort/energy that has gone into Forrest since it was created, I > think it only makes sense if Cocoon moves its documentation system onto > forrest. > - o - > > This said, here are the actions you should vote: > > 1) cocoon moves to forrest for its documentation production > > 2) if so, cocoon does it before releasing 2.1 > > 3) if so, I'd like a 'fast-yet-potentially-disruptive' move rather > than a 'slow-yet-carefully-planned-not-to-disrupt-anything' one.
It's seems that we have a consensus here. So what to do? Does it mean that we will concentrate us on the samples? Shipping only a samples webapp, producing the docs with separate installation of Forrest? If we upgrade the docs to v11 we will break the orginal docs target. Or does anyone have a other solution? BTW, that does save us much effort for maintaining the doc generation process. Stephan.
