Return-Path: Mailing-List: contact gump-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list gump@jakarta.apache.org Received: (qmail 88512 invoked from network); 7 Nov 2003 22:27:42 -0000 Received: from unknown (HELO nyx.stonecobra.com) (66.139.79.201) by daedalus.apache.org with SMTP; 7 Nov 2003 22:27:42 -0000 Received: (qmail 6446 invoked from network); 7 Nov 2003 22:44:29 -0000 Received: from gw000001.80211.net (HELO ?10.80.211.54?) (63.230.4.33) by nyx.stonecobra.com with SMTP; 7 Nov 2003 22:44:29 -0000 Mime-Version: 1.0 (Apple Message framework v606) In-Reply-To: <0af301c3a3c5$33ad3520$c38b1f43@tsws1> References: <0af301c3a3c5$33ad3520$c38b1f43@tsws1> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <928C176E-1171-11D8-808D-000A959FF68E@dotnot.org> Content-Transfer-Encoding: 7bit From: Scott Sanders Subject: Re: Gump Site/Documentation Date: Fri, 7 Nov 2003 14:27:29 -0800 To: "Gump code and data" X-Mailer: Apple Mail (2.606) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > All > > I'd really like to start updating the documentation for Gump. Sadly, > I'm not > familiar with the xdoc to site generator that has been used. Would it > be ok > if I attempted to convert Gump documentation to using forrest, and then > attempt to update the site? Is this a good way to do things these > days, or > ought I attempt to learn the existing mechanism? > I believe it has been built with Anakia, a small subproject of velocity. It is relatively simple to master, but if you want to upgrade to Forrest, feel free. I would assume this is going to fall under 'lazy concensus', so just go for it unless someone outright objects. Scott