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 22467 invoked from network); 12 Jul 2002 21:40:04 -0000 Received: from mail.datazug.ch (212.4.65.100) by daedalus.apache.org with SMTP; 12 Jul 2002 21:40:04 -0000 Received: from yahoo.de [212.4.77.228] by mail.datazug.ch with ESMTP (SMTPD32-7.11) id ACD3388801C6; Fri, 12 Jul 2002 23:40:35 +0200 Message-ID: <3D2F4CFA.8090706@yahoo.de> Date: Fri, 12 Jul 2002 23:41:14 +0200 From: "J.Pietschmann" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: forrestbot: security and trust References: <3D2EDCDF.6090800@outerthought.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 170 Steven Noels wrote: > We are going to do remote project docs building, presumably for Apache > and non-Apache projects alike (Gump-style). The big difference however > between Gump and Forrest is that Gump only reports (on a central > location) and nags, whereas Forrest will distribute its results to other > locations as well for updating those websites. Is "remote" really such an important requirement? Don't the other servers have cron and other infrastructure or is local building considered to eat up too much ressources? If my website was important enough, I'd rather use local doc building rather than depend on trusted third parties and the security of machines I don't control. This doesn't mean forrest shouldn't do remote building. J.Pietschmann