Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of jta@bristowhill.com designates
 66.75.162.134 as permitted sender)
Message-ID: <437274A0.1060700@bristowhill.com>
Date: Wed, 09 Nov 2005 14:13:52 -0800
From: "Jean T. Anderson" <jta@bristowhill.com>
Reply-To: jta@bristowhill.com
User-Agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [doc] ditaot in derby svn base feedback / external docs doc
References: <43723325.7070504@wiu.edu> <43724EFB.9000105@bristowhill.com>
In-Reply-To: <43724EFB.9000105@bristowhill.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jean T. Anderson wrote:
> scott hutinger wrote:
> 
>> ... 1) Since the Dita OT has an apache license, some or all of the 
>> source can be put in svn.  
> 
> 
> One of the first steps is to verify the DITA ASL distribution works for 
> Derby. I logged DERBY-687 for this.

I think it'd be helpful to summarize why we (well, I) asked the DITA 
project to dual license the DITA Open Toolkit under the ASL.

Two files drove it.

The first file is resource/commonltr.css , which ideally should be put 
on the Derby web site to improve display of the html manuals. That file 
can't be on the Apache web site unless it's available under the ASL.

The second file is xsl/dita2fo-shell.xsl, an XSL style sheet for PDF 
output that Jeff Levitt modified for Derby. That file gets used when you 
build the documentation.

Instead of asking the DITA project team to contribute those two files to 
the ASF, I asked them to dual license the tool kit under the ASL. That 
way if any other files in the future need to be tweaked for Derby we can 
do so without worrying about license issues.

So that's the history as I remember it.

  -jean