Return-Path: Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 81416 invoked from network); 23 Feb 2002 09:43:52 -0000 Received: from unknown (HELO bluebox.betaversion.org) (62.110.41.207) by daedalus.apache.org with SMTP; 23 Feb 2002 09:43:52 -0000 Received: from apache.org (ppp-62-11-55-73.dialup.tiscali.it [62.11.55.73]) by bluebox.betaversion.org (Postfix) with ESMTP id CCDBF4DFED for ; Sat, 23 Feb 2002 10:44:03 +0100 (CET) Message-ID: <3C769393.6B81F38F@apache.org> Date: Fri, 22 Feb 2002 19:53:07 +0100 From: Stefano Mazzocchi X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Apache Forrest Subject: [phases] Forrest Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I've placed lots of irons in the fire with my dream-list, now it's time to plan an incremental way to build it. Here is my proposal: [Phase 1] static - documentation - javadocs - logs graphs - calendar - RSS feed [Phase 2] dynamic - weblogs - dynamic docs [Phase 3] search - mail archive - search engine The first phase can be statically generated, it would be easier to accept at first and will eventually lead to a more diverse community (currently, we are all cocooners, more or less) - o - For the first phase we need: for docs: 1) collect all the various documentation from CVS 2) adapt them to our DTD 3) generate the docs for logs: 1) collect all the data we need 2) analyze it 3) collect the event data 4) aggregate with the analyzed logs 5) generate the graphics for javadocs: 1) collect all the sourcecode 2) run javadoc with the XML doclet 3) generate the docs for calendar and newsfeeds: 1) collect all the event data 2) generate the calendar pages (or stubs for aggregation into docs) 3) generate the newsfeed pages (global and subproject-specific) In order to do this we need to: 1) have a 'subproject descriptor' that indicates:X-Mozilla-Status: 0009e code is located - where the documentation is located - what format (schema) the docs are written with 2) define a DTD for 'events' and expect 'events.xml' in the root of each subproject [past events can be used for news, future events can be used for calendaring] 3) define a URI space for the generated docs -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche --------------------------------------------------------------------