db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject Re: [doc] DITA-OT in Derby svn
Date Wed, 16 Nov 2005 04:13:13 GMT
Andrew McIntyre wrote:
> ... 
> I finally had time to get back to this. Here's what I would like to do:
> 1 - check the latest ASL-licensed DITA-OT zip file into svn into the
> docs/trunk/lib dir.

Andrew, I don't think we can just commit the entire DITA Open Toolkit to 
the Derby doc repo without doublechecking what the ASF process might be.

The process for handling the two DITA files that were originally at 
issue, xsl/dita2fo-shell.xsl and resource/commonltr.css, is simple.
Back in June I verified how to handle the two DITA files once they were 
available under the ASL, and the Derby podling PMC mentors confirmed 
this handling would be correct:

    Once the SourceForge site shows that the DITA Toolkit is licensed
    under the Apache license, for those two files I'll move the IBM
    copyright into the NOTICES file, put the ASF copyright in its place,
    and commit the file.

Just to avoid any immediate misunderstanding on this derby-dev list, the 
"ASF copyright" that I was referring to is what we use for Derby code 
and docs:

    Copyright 2005 The Apache Software Foundation or its licensors, as 

I understood at the time that if we wanted to import an entire 
subproject from some other home, Apache has different processes 
depending on the size of the import.

So, if you want to import the entire DITA Open Toolkit, we need to check 
to see what that process is.


> 2 - check in Jeff's modified version of the ASL-licensed dita2fo-shell.xsl file.
> 3 - for ease of use, modify the build to unpack the DITA toolkit into
> the checked out docs directory and copy Jeff's file over.
> 4 - update the directions on the website on building the docs to
> reflect that it is no longer necessary to download the toolkit.
> I have verified that the build works with the latest DITA toolkit, and
> I would like to make the changes listed above as soon as possible if
> there are no objections.
> Scott, if you'd like to contribute maven buildfiles for the docs, feel
> free, I'll be glad to review and commit them. Most derby developers
> are familiar with Ant, so I'll make sure that the Ant targets are up
> to date.
> If anyone has any concerns about the changes above, please let me know
> as soon as possible. I would like to check them in tomorrow.
> Thanks,
> andrew

View raw message