Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Message-ID: <005601c1dfa9$c45079c0$670004c0@PC103>
Reply-To: "Nicola Ken Barozzi" <nicolaken@apache.org>
From: "Nicola Ken Barozzi" <nicolaken@apache.org>
To: <forrest-dev@xml.apache.org>
References: <3CAF13D0.1000008@koberg.com> <3CB18DFE.1D135826@apache.org>
Subject: [ROADMAP] Forrest 0.1
Date: Tue, 9 Apr 2002 11:33:02 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I think we gotta start rolling Forrest 0.1
This is what I propose:

==========================
                  ROADMAP
==========================

[nicolaken] update Forrest to Centipede 1.0-dev

[all] decide how to enhance bool.xml if needed

[nicolaken + all] see if the new xml definitions of Centipede are ok and
make final DTDs

[open] make an index aggregation stuff; see if Gianugo's stuff solves the
problem

[open] make a forrest skin

[all] add documentation to our site

[open] make a converter that changes automatically the old docs into the new
DTD. Basically, we just need to do a search and replace of the DTD
declarations and change s1|s2|s3|s4 to section. I did this by hand for
Jakarta POI, that is currently using the Forrest DTD.

[all] decide how to schedule site update runs - on which machine will it
run? when?

[nicolaken + all] make a forrest specific configuration file, where we have
the names of the projects that want to Forrest.

[nicolaken + open] make a target that collects the docs from the CVSs and
publishes them

[nicolaken] implement basic nagging system with the code used for Cocoon
nags

--
Nicola Ken Barozzi                   nicolaken@apache.org
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------