From general-return-6279-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Fri Nov 04 06:33:00 2005 Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 64043 invoked from network); 4 Nov 2005 06:32:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Nov 2005 06:32:58 -0000 Received: (qmail 48864 invoked by uid 500); 4 Nov 2005 06:32:56 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 48216 invoked by uid 500); 4 Nov 2005 06:32:53 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 48198 invoked by uid 99); 4 Nov 2005 06:32:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2005 22:32:52 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [65.77.211.84] (HELO www2.kc.aoindustries.com) (65.77.211.84) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2005 22:32:47 -0800 Received: from fo2.kc.aoindustries.com (www2.kc.aoindustries.com [65.77.211.84]) by www2.kc.aoindustries.com (8.13.1/8.13.1) with ESMTP id jA46WTYt031897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 4 Nov 2005 00:32:30 -0600 Received: from localhost (localhost [[UNIX: localhost]]) by fo2.kc.aoindustries.com (8.13.1/8.13.1/Submit) id jA46WTtL031822 for general@incubator.apache.org; Fri, 4 Nov 2005 00:32:29 -0600 X-Authentication-Warning: fo2.kc.aoindustries.com: indexgeo set sender to crossley@apache.org using -f Date: Fri, 4 Nov 2005 17:31:58 +1100 From: David Crossley To: general@incubator.apache.org Subject: simplifying the generation of Incubator website Message-ID: <20051104063158.GA932@igg.indexgeo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I would like to try again to make it easier to build the Incubator website. Next week i will ugrade the configuration to use the current release of Forrest (Incubator is one behind). Along with creating a better procedure document, might make it easier. I also want to have a discussion about why we are using Forrest and whether something else might be more relevant, or if continuing with Forrest then how to improve. First a digression about the content ... The website could use a lot more instructions. Some procedural documentation is incorrect, out-of-date, misleading, non-existent. The current pages could also be enhanced and corrected. The source content is in html format at "site-author" directory. Please edit it and view the html document directly in your web browser. Looks okay? Then do your normal svn procedure 'svn diff, svn commit' etc. Done. Later someone will build the documents with Forrest. That is probably me, but can be any other committer with Forrest installed. Yes we would all love to have the better infrastructure for generating, staging, and publishing all project sites using whatever software they like. However that is not happening yet. See the site-dev list. ---oOo--- Now on to the issues with using Forrest. Yes we know that it is a little cumbersome and needs to be installed. I am concerned that this might be contributing to the hold-up with editing the docs. Not trying to make excuses, but Forrest is pre-1.0 so it should be expected to be a little difficult. Anyway, lets try to either find out what can be improved or look at using something else. Incubator started before i joined, so can someone tell what was the reason for choosing Forrest. It is a publishing framework, and perhaps the simple needs of Incubator do not warrant its use. One beauty is that the content can be edited as simple html docs, rather than an xml format. My guess about the stumbling block for some people is the need to check the final result into svn. Also the need to copy files from build/site into site-publish and then do svn add or svn remove files. I think that we can get Cocoon to generate the files directly into site-publish directory if that helps. Another trouble is that for just changing one little document, then Cocoon needs to generate everything. Sorry not much we can do about that at this stage. There is a trick which i will document. There is also "local forrestbot" which i will explain after the upgrade. Can people define any other issues? Probably best to keep specific stuff until i have upgraded to 0.7 next week. -David --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org