Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 95895 invoked from network); 9 Nov 2005 17:35:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Nov 2005 17:35:15 -0000 Received: (qmail 32739 invoked by uid 500); 9 Nov 2005 17:35:14 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 32703 invoked by uid 500); 9 Nov 2005 17:35:13 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 32694 invoked by uid 99); 9 Nov 2005 17:35:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 09:35:13 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [143.43.222.207] (HELO mail.wiu.edu) (143.43.222.207) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 09:35:03 -0800 Received: from scanner0.wiu.edu (scanner0 [143.43.222.140]) by mail.wiu.edu (8.9.3/8.9.3) with SMTP id LAA03757 for ; Wed, 9 Nov 2005 11:34:46 -0600 (CST) Received: from srv1.wiu.edu ([143.43.222.31]) by scanner0.wiu.edu (SAVSMTP 3.1.1.32) with SMTP id M2005110911344501821 for ; Wed, 09 Nov 2005 11:34:45 -0600 Received: from [192.168.1.100] (143-43-234-173.as3.modems.wiu.edu [143.43.234.173]) by srv1.wiu.edu (8.12.6/8.12.6) with ESMTP id jA9HYUQj019388 for ; Wed, 9 Nov 2005 11:34:39 -0600 (CST) Message-ID: <43723325.7070504@wiu.edu> Date: Wed, 09 Nov 2005 11:34:29 -0600 From: scott hutinger User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: [doc] ditaot in derby svn base feedback / external docs doc Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I wanted to get the build of the docs finished so everyone can build what is currently being used. Jeff Levit has some changes he made that are not incorporated in the dita toolkit. Also, I would like to get the build up with the current svn number etc. I had one method of doing this, but think possibly Andrew was thinking of another method. I also think I had ant do most of it in one version of this. What I would like to do is get some feedback on the direction that everyone thinks should be taken. 1) Since the Dita OT has an apache license, some or all of the source can be put in svn. If we used a Maven build, maven could download and we could patch with Derby changes to the ot, or we could just bring the whole code base into svn and make changes this way. I normally don't think this way, so wasn't sure what the current best method would be. Any ideas? This could also be done without maven another way... Is maven the prefered build or is this not an issue at this point in time? 2) The latest alpha files on the website always have an old build date. I am uncertain if they don't get built after changes, if they go through a build daily, or if they don't go through a build at all. It might also be that a hard coded date is in the dita ot. Any feedback is very welcome, as DITAOT changed the license quite some time ago; and this should be used. I think the main feedback is: how should the DITAOT source be handled with Jeffs and any other changes that are not within the DITAOT source base yet? Also not releated, it might be nice to get some type of external reference document. I noticed that Army had some external docs on the wiki on DRDA(from The Open Group) etc.. I think some other good external docs exist too. I think it would be nice to gather all of these in a document with a bit of information on the documents themselves etc... (i.e. to download 'The Open Group' documents for DRDA, you need to do x/y/z to get them etc...). Myself being one of those typical developers that get's a lot of help from those external docs. I think a lot of developers don't really know that much about SQL standards etc (myself being one), so those external docs are VERY helpful. thanks, scott