forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: Creating documentation (Re: Link to CSS howto-structurer-dsl.html)
Date Sun, 18 Dec 2005 02:19:40 GMT
Calmbach, Richard wrote:
> > -----Original Message-----
> > From: Ross Gardler:
> > 
> > (this is a general comment not at all aimed at the authors of 
> > these mails - since I'm in that group)
> > 
> > Why is it that people take the time to write clear 
> > documentation like this but nobody puts it into a document?
> I noticed that Forrest doesn't have a wiki at,
> unlike many other Apache projects. A wiki may facilitate the creation of
> documentation for new features that are still under development. There
> is close to zero overhead in adding and revising content. The additional
> benefit is that users who want to experiment with the latest code have a
> central place to go for information. It's sometimes difficult to find
> specific info in the mailing list archives. Once new features have
> stabilized, the wiki pages can be converted to xdoc and moved to the
> official documentation.

As you can imagine, this topic comes up often. We need
to document our procedure better.

Here is one such thread. It leads to some others.

Instead of putting effort into installing and managing a Wiki,
we would rather put that effort into using Apache Lenya.

However, as discussed before, what is wrong with using the
current procedure like just happened for the forrestbot.html
and is gradually happening for the Dispatcher documentation?

You talk about "central place for documentation of latest code".
That is
and for the bleeding edge, it is at:
... and top-level documents are updated too, e.g.


View raw message