Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 1049 invoked from network); 2 Mar 2005 20:20:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Mar 2005 20:20:34 -0000 Received: (qmail 86368 invoked by uid 500); 2 Mar 2005 20:20:33 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 86329 invoked by uid 500); 2 Mar 2005 20:20:32 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 86307 invoked by uid 99); 2 Mar 2005 20:20:32 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of jta@bristowhill.com designates 66.75.162.135 as permitted sender) Received: from ms-smtp-03-qfe0.socal.rr.com (HELO ms-smtp-03-eri0.socal.rr.com) (66.75.162.135) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 02 Mar 2005 12:20:30 -0800 Received: from [192.168.15.53] (cpe-204-210-23-212.san.res.rr.com [204.210.23.212]) by ms-smtp-03-eri0.socal.rr.com (8.12.10/8.12.7) with ESMTP id j22KKRuY024193 for ; Wed, 2 Mar 2005 12:20:27 -0800 (PST) Message-ID: <4226200A.1010800@bristowhill.com> Date: Wed, 02 Mar 2005 12:20:26 -0800 From: "Jean T. Anderson" User-Agent: Mozilla Thunderbird 0.9 (X11/20041127) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: Re: [doc] Where should the DITA source files be checked in? References: <20050302200005.59625.qmail@web81605.mail.yahoo.com> In-Reply-To: <20050302200005.59625.qmail@web81605.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Jeff Levitt wrote: > --- "Jean T. Anderson" wrote: > > When I contribute the dita files for the tools and > utilities guide (very soon), we can start building > html for the DITA sources now, and you could have > Forrest build a nav for them, just like the current > implementation. > I prefer to not continue building the docs with each web site update like we do now. It might help to separate out these doc issues: 1) Where the DITA source files should live 2) What product(s) should be built and in what format Let's stick to issue #1 in this email thread and move #2 to another email topic. -jean