You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Andrew McIntyre <mc...@gmail.com> on 2005/11/16 02:20:57 UTC
Re: [doc] DITA-OT in Derby svn
On 11/12/05, Jean T. Anderson <jt...@bristowhill.com> wrote:
> Jeff Levitt wrote:
> > I am attaching
> > the files I needed to change in the DITA-OT1.0.2
> > build. I would have created a patch but I dont think
> > we've checked these in yet under the Apache ASL? Is
> > that what the plan is?
>
> No DITA files have been committed yet.
>
> Could you attach your new files to DERBY-687?
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.
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
Re: [doc] DITA-OT in Derby svn
Posted by scott hutinger <s-...@wiu.edu>.
Hi Jean,
Could you modify the:
The binary download of the DITA Toolkit
<http://prdownloads.sourceforge.net/dita-ot/DITA-OT1.1.2.1_bin-ASL.zip?download>
Version 1.2.1.1 from SourceForge. Use ONLY this version.
The ONLY this version should be something along the lines of download to
the /lib area otherwise a:
BUILD FAILED
/home/srh/src/derby-d/doc/trunk/build.xml:31: Error while expanding
/home/srh/src/derby-d/doc/trunk/lib/DITA-OT1.1.2.1_bin-ASL.zip
I think the ONLY this version could be removed and replaced with putting
the .zip (I understand the .zip format), in the lib area.
Or whatever everyone thinks fit for this....
thanks,
scott
Jean T. Anderson wrote:
> Andrew McIntyre wrote:
>
>> On 11/16/05, Jean T. Anderson <jt...@bristowhill.com> wrote:
>>
>> ...
>>
>>> At any rate, I don't feel comfortable committing the DITA-OT to the
>>> derby repo and I think for now our instructions should simply tell
>>> developers to download and install it.
>>
>>
>>
>> That's fine, I've committed the changes to both the doc build files
>> and updated the website.
>>
>> Mind if I ask about this on repository@? That seems like the best
>> place to ask.
>
>
> that's a terrific idea -- go for it.
>
>>
>>> Is anyone else going to the hackathon at ApacheCon? I'll be there.
>>> That
>>> would be a good opportunity to talk to other project teams about how
>>> these things get handled. (And I promise to summarize whatever is
>>> learned for the derby-dev list.)
>>
>>
>>
>> Maybe. Do you have a link to info on the hackathon? Either way, I'll
>> see you there. :-)
>
>
> handy details were posted to women@ :
>
> http://mail-archives.apache.org/mod_mbox/www-women/200511.mbox/%3c43691AD6.9070404@shanecurcuru.org%3e
>
>
> -jean
>
Re: [doc] DITA-OT in Derby svn
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Andrew McIntyre wrote:
> On 11/16/05, Jean T. Anderson <jt...@bristowhill.com> wrote:
>
> ...
>>At any rate, I don't feel comfortable committing the DITA-OT to the
>>derby repo and I think for now our instructions should simply tell
>>developers to download and install it.
>
>
> That's fine, I've committed the changes to both the doc build files
> and updated the website.
>
> Mind if I ask about this on repository@? That seems like the best place to ask.
that's a terrific idea -- go for it.
>
>>Is anyone else going to the hackathon at ApacheCon? I'll be there. That
>>would be a good opportunity to talk to other project teams about how
>>these things get handled. (And I promise to summarize whatever is
>>learned for the derby-dev list.)
>
>
> Maybe. Do you have a link to info on the hackathon? Either way, I'll
> see you there. :-)
handy details were posted to women@ :
http://mail-archives.apache.org/mod_mbox/www-women/200511.mbox/%3c43691AD6.9070404@shanecurcuru.org%3e
-jean
Re: [doc] DITA-OT in Derby svn
Posted by Andrew McIntyre <mc...@gmail.com>.
On 11/16/05, Jean T. Anderson <jt...@bristowhill.com> wrote:
> Looking more closely at your list, all I see are jar's, and I don't see
> anyone who includes entire distributions. For example, Beehive's
> http://svn.apache.org/repos/asf/beehive/trunk/external/derby/ just
> includes the derby jar, and not the entire binary Derby distribution.
This is true, but there's no way to separate out a single artifact
from the DITA toolkit like a single jar. Because it's a set of DTDs
and XSL transforms, you need everything in the toolkit (minus docs,
demo, and samples dirs) for it to function.
> But I'm also not looking closely at all the source for these projects.
> Did you spot any that included the distribution for one of the products
> it uses?
No, but as I said, it's a slightly different animal than a Java
library in a jar.
> At any rate, I don't feel comfortable committing the DITA-OT to the
> derby repo and I think for now our instructions should simply tell
> developers to download and install it.
That's fine, I've committed the changes to both the doc build files
and updated the website.
Mind if I ask about this on repository@? That seems like the best place to ask.
> Is anyone else going to the hackathon at ApacheCon? I'll be there. That
> would be a good opportunity to talk to other project teams about how
> these things get handled. (And I promise to summarize whatever is
> learned for the derby-dev list.)
Maybe. Do you have a link to info on the hackathon? Either way, I'll
see you there. :-)
andrew
Re: [doc] DITA-OT in Derby svn
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Andrew McIntyre wrote:
>
> On Nov 16, 2005, at 11:00 AM, Jean T. Anderson wrote:
>
>> Andrew McIntyre wrote:
>>
>>> On Nov 16, 2005, at 10:22 AM, Jean T. Anderson wrote:
>>>
>>>> Andrew McIntyre wrote:
>>>>
>>>>> Hmm, but we include the entire javacc and jakarta-oro
>>>>> distributions in the code tree, in tools/java. Should we not be
>>>>> doing that?
>>>>
>>>>
>>>>
>>>> oh. :-) It'd be good to follow-up on that. If another Apache
>>>> project does the same, then I wouldn't worry about it -- precedent
>>>> is good. Also this topic may have been raised before on
>>>> infrastructure@ .
>>>
>>> Well, here's precedent, FWIW:
>>> http://svn.apache.org/repos/asf/xalan/java/trunk/tools/
>>> http://svn.apache.org/repos/asf/lenya/trunk/lib/
>>> http://svn.apache.org/repos/asf/forrest/trunk/lib/core/
>>> http://svn.apache.org/repos/asf/db/ddlutils/trunk/lib/
>>> http://svn.apache.org/repos/asf/beehive/trunk/external/
>>> I could go on, but I won't. :-) Note that the last one has
>>> junit.jar, which I thought was a no-no?
>>
>>
>> I think you have found adequate precedent. :-)
>
> So, to bring it back around again - do you think it would be ok to
> check in the binary distribution of the DITA toolkit into the lib
> directory in the Derby docs tree?
>
> andrew
>
I spoke in haste when I said "I think you have found adequate precedent".
Looking more closely at your list, all I see are jar's, and I don't see
anyone who includes entire distributions. For example, Beehive's
http://svn.apache.org/repos/asf/beehive/trunk/external/derby/ just
includes the derby jar, and not the entire binary Derby distribution.
(Beehive is an exception because it includes beehive-antext, which is
obvious associated.)
But I'm also not looking closely at all the source for these projects.
Did you spot any that included the distribution for one of the products
it uses?
At any rate, I don't feel comfortable committing the DITA-OT to the
derby repo and I think for now our instructions should simply tell
developers to download and install it.
Is anyone else going to the hackathon at ApacheCon? I'll be there. That
would be a good opportunity to talk to other project teams about how
these things get handled. (And I promise to summarize whatever is
learned for the derby-dev list.)
-jean
p.s. If anyone is going to ApacheCon who is not a committer but would
like to go to the hackathon, let me know. Committers can bring
non-committers as guests.
Re: [doc] DITA-OT in Derby svn
Posted by Andrew McIntyre <mc...@gmail.com>.
On Nov 16, 2005, at 11:00 AM, Jean T. Anderson wrote:
> Andrew McIntyre wrote:
>> On Nov 16, 2005, at 10:22 AM, Jean T. Anderson wrote:
>>> Andrew McIntyre wrote:
>>>
>>>> Hmm, but we include the entire javacc and jakarta-oro
>>>> distributions in the code tree, in tools/java. Should we not
>>>> be doing that?
>>>
>>>
>>> oh. :-) It'd be good to follow-up on that. If another Apache
>>> project does the same, then I wouldn't worry about it --
>>> precedent is good. Also this topic may have been raised before
>>> on infrastructure@ .
>> Well, here's precedent, FWIW:
>> http://svn.apache.org/repos/asf/xalan/java/trunk/tools/
>> http://svn.apache.org/repos/asf/lenya/trunk/lib/
>> http://svn.apache.org/repos/asf/forrest/trunk/lib/core/
>> http://svn.apache.org/repos/asf/db/ddlutils/trunk/lib/
>> http://svn.apache.org/repos/asf/beehive/trunk/external/
>> I could go on, but I won't. :-) Note that the last one has
>> junit.jar, which I thought was a no-no?
>
> I think you have found adequate precedent. :-)
So, to bring it back around again - do you think it would be ok to
check in the binary distribution of the DITA toolkit into the lib
directory in the Derby docs tree?
andrew
Re: [doc] DITA-OT in Derby svn
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Andrew McIntyre wrote:
>
> On Nov 16, 2005, at 10:22 AM, Jean T. Anderson wrote:
>
>> Andrew McIntyre wrote:
>>
>>> Hmm, but we include the entire javacc and jakarta-oro
>>> distributions in the code tree, in tools/java. Should we not be
>>> doing that?
>>
>>
>> oh. :-) It'd be good to follow-up on that. If another Apache project
>> does the same, then I wouldn't worry about it -- precedent is good.
>> Also this topic may have been raised before on infrastructure@ .
>
>
> Well, here's precedent, FWIW:
>
> http://svn.apache.org/repos/asf/xalan/java/trunk/tools/
> http://svn.apache.org/repos/asf/lenya/trunk/lib/
> http://svn.apache.org/repos/asf/forrest/trunk/lib/core/
> http://svn.apache.org/repos/asf/db/ddlutils/trunk/lib/
> http://svn.apache.org/repos/asf/beehive/trunk/external/
>
> I could go on, but I won't. :-) Note that the last one has junit.jar,
> which I thought was a no-no?
I think you have found adequate precedent. :-)
My understanding about junit.jar is it's OK to use (and many apache
projects do), but not OK to commit to an asf repo because it's licensed
under the CPL. Junit came up during the DITA* discussions, because both
are under CPL, and that's when we were told we could not commit anything
under CPL to the ASF repos.
-jean
*DITA: for anyone stumbling onto this post out of context, DITA is now
dual licensed under CPL and ASL.
Re: [doc] DITA-OT in Derby svn
Posted by Andrew McIntyre <mc...@gmail.com>.
On Nov 16, 2005, at 10:22 AM, Jean T. Anderson wrote:
> Andrew McIntyre wrote:
>> Hmm, but we include the entire javacc and jakarta-oro
>> distributions in the code tree, in tools/java. Should we not be
>> doing that?
>
> oh. :-) It'd be good to follow-up on that. If another Apache
> project does the same, then I wouldn't worry about it -- precedent
> is good. Also this topic may have been raised before on
> infrastructure@ .
Well, here's precedent, FWIW:
http://svn.apache.org/repos/asf/xalan/java/trunk/tools/
http://svn.apache.org/repos/asf/lenya/trunk/lib/
http://svn.apache.org/repos/asf/forrest/trunk/lib/core/
http://svn.apache.org/repos/asf/db/ddlutils/trunk/lib/
http://svn.apache.org/repos/asf/beehive/trunk/external/
I could go on, but I won't. :-) Note that the last one has junit.jar,
which I thought was a no-no?
andrew
Re: [doc] DITA-OT in Derby svn
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Andrew McIntyre wrote:
>
> On Nov 16, 2005, at 10:06 AM, Jean T. Anderson wrote:
>
>> If we were just committing a jar file or two, like we do with the
>> jakarta-servlet jar for the derby code build, I wouldn't see any
>> problem at all with it. But by committing the entire software
>> distribution we're providing alternate distribution (in addition to
>> SourceForge), even if to just a small number of developers. It would
>> be as if we included the entire jakarta-servlet distribution, which
>> we don't do (lest I cause confusion) and wouldn't do.
>
> Hmm, but we include the entire javacc and jakarta-oro distributions in
> the code tree, in tools/java. Should we not be doing that?
oh. :-) It'd be good to follow-up on that. If another Apache project
does the same, then I wouldn't worry about it -- precedent is good. Also
this topic may have been raised before on infrastructure@ .
>> My intuition says this wouldn't fly, but if you feel strongly about
>> it, I suggest you close the loop with infrastructure@.
>
> The thing is that I *don't* feel strongly about it. :-) If it's an
> issue, then we continue to point to Sourceforge.
let's point to SourceForge then.
>> My preference would be to look into a tool that can automate the
>> software fetch, like maven does; and, in the meantime, instruct the
>> developers who want to build the derby DITA docs to download the tool
>> kit from SourceForge.
>
>
> I'll look into maven, but in the interest of getting this going, I'll
> just commit everything mentioned in my previous mail but the toolkit zip.
that sounds good.
-jean
Re: [doc] DITA-OT in Derby svn
Posted by Andrew McIntyre <mc...@gmail.com>.
On Nov 16, 2005, at 10:06 AM, Jean T. Anderson wrote:
> If we were just committing a jar file or two, like we do with the
> jakarta-servlet jar for the derby code build, I wouldn't see any
> problem at all with it. But by committing the entire software
> distribution we're providing alternate distribution (in addition to
> SourceForge), even if to just a small number of developers. It
> would be as if we included the entire jakarta-servlet distribution,
> which we don't do (lest I cause confusion) and wouldn't do.
Hmm, but we include the entire javacc and jakarta-oro distributions
in the code tree, in tools/java. Should we not be doing that?
> My intuition says this wouldn't fly, but if you feel strongly about
> it, I suggest you close the loop with infrastructure@.
The thing is that I *don't* feel strongly about it. :-) If it's an
issue, then we continue to point to Sourceforge.
> My preference would be to look into a tool that can automate the
> software fetch, like maven does; and, in the meantime, instruct the
> developers who want to build the derby DITA docs to download the
> tool kit from SourceForge.
I'll look into maven, but in the interest of getting this going, I'll
just commit everything mentioned in my previous mail but the toolkit
zip.
andrew
Re: [doc] DITA-OT in Derby svn
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Andrew McIntyre wrote:
>
> On Nov 16, 2005, at 7:49 AM, Jean T. Anderson wrote:
>
>> so, it sounds more like you want the ease-of-use of a maven plug-in
>> where it's acquired and expanded on demand.
>
> Yes and no. It has to be expanded simply because Ant can't access the
> xml files while they're in the jar. And we have to merge our modified
> file into the expanded toolkit.
>
>> Actually, I suggest first that you check with infrastructure@ (since
>> you're already subscribed) to see if they're ok with distribution --
>> how big is the zip file? Is this a case where we should consider
>> using maven instead?
>
>
> The zip is 2.5MB. Since we'd be distributing it, at best, to a subset
> of Derby developers (some set of less than 47 people, judging by the
> registered JIRA users) I wouldn't think that bandwidth/load would be an
> issue. It's not as though Derby users would be checking it out from
> subversion, where the number of downloads would be open-ended and quite
> possibly a high number.
>
> Is maven the right answer? I don't know. If you think so, I'll look
> into it.
If we were just committing a jar file or two, like we do with the
jakarta-servlet jar for the derby code build, I wouldn't see any problem
at all with it. But by committing the entire software distribution we're
providing alternate distribution (in addition to SourceForge), even if
to just a small number of developers. It would be as if we included the
entire jakarta-servlet distribution, which we don't do (lest I cause
confusion) and wouldn't do. My intuition says this wouldn't fly, but if
you feel strongly about it, I suggest you close the loop with
infrastructure@.
My preference would be to look into a tool that can automate the
software fetch, like maven does; and, in the meantime, instruct the
developers who want to build the derby DITA docs to download the tool
kit from SourceForge.
-jean
Re: [doc] DITA-OT in Derby svn
Posted by Andrew McIntyre <mc...@gmail.com>.
On Nov 16, 2005, at 7:49 AM, Jean T. Anderson wrote:
> so, it sounds more like you want the ease-of-use of a maven plug-in
> where it's acquired and expanded on demand.
Yes and no. It has to be expanded simply because Ant can't access the
xml files while they're in the jar. And we have to merge our modified
file into the expanded toolkit.
> Actually, I suggest first that you check with infrastructure@
> (since you're already subscribed) to see if they're ok with
> distribution -- how big is the zip file? Is this a case where we
> should consider using maven instead?
The zip is 2.5MB. Since we'd be distributing it, at best, to a subset
of Derby developers (some set of less than 47 people, judging by the
registered JIRA users) I wouldn't think that bandwidth/load would be
an issue. It's not as though Derby users would be checking it out
from subversion, where the number of downloads would be open-ended
and quite possibly a high number.
Is maven the right answer? I don't know. If you think so, I'll look
into it.
andrew
Re: [doc] DITA-OT in Derby svn
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Andrew McIntyre wrote:
>
> On Nov 15, 2005, at 8:13 PM, Jean T. Anderson wrote:
>
>> 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.
>
>
> Note that I'm planning on checking the ASL-licensed 'bin' zip file into
> the repo, and not source files, and as such I was hoping that we could
> treat it like a library. Obviously the NOTICE (and possibly COPYRIGHT)
> file in the docs tree would need to be updated accordingly. Ant would
> expand the zip file at build time, because there is not currently a way
> to use the files in the toolkit while they're still in the jar.
so, it sounds more like you want the ease-of-use of a maven plug-in
where it's acquired and expanded on demand.
>> The process for handling the two DITA files that were originally at
>> issue, xsl/dita2fo-shell.xsl and resource/commonltr.css, is simple.
>
>
> Right, and I propose that only Jeff's modified dita2fo-shell.xsl into
> the repository as a source file, the rest of the toolkit as a binary
> file. The intention is that dita2fo-shell.xsl will be the only file we
> would modify.
>
>> 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.
>
>
> Should I start a thread on legal-discuss? Or would you like to take the
> lead on that, since you're on the PMC and have already led discussions
> on this topic?
Actually, I suggest first that you check with infrastructure@ (since
you're already subscribed) to see if they're ok with distribution -- how
big is the zip file? Is this a case where we should consider using maven
instead?
-jean
Re: [doc] DITA-OT in Derby svn
Posted by Andrew McIntyre <mc...@gmail.com>.
On Nov 15, 2005, at 8:13 PM, Jean T. Anderson wrote:
> 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.
Note that I'm planning on checking the ASL-licensed 'bin' zip file
into the repo, and not source files, and as such I was hoping that we
could treat it like a library. Obviously the NOTICE (and possibly
COPYRIGHT) file in the docs tree would need to be updated
accordingly. Ant would expand the zip file at build time, because
there is not currently a way to use the files in the toolkit while
they're still in the jar.
> The process for handling the two DITA files that were originally at
> issue, xsl/dita2fo-shell.xsl and resource/commonltr.css, is simple.
Right, and I propose that only Jeff's modified dita2fo-shell.xsl into
the repository as a source file, the rest of the toolkit as a binary
file. The intention is that dita2fo-shell.xsl will be the only file
we would modify.
> 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.
Should I start a thread on legal-discuss? Or would you like to take
the lead on that, since you're on the PMC and have already led
discussions on this topic?
andrew
Re: [doc] DITA-OT in Derby svn
Posted by Andrew McIntyre <mc...@gmail.com>.
On Nov 15, 2005, at 8:13 PM, Jean T. Anderson wrote:
> 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.
Hit the send button before finishing all my thoughts.
If the answer is no, or it turns out that it is more trouble than it
is worth, then we can simply amend the instructions to be "download x
version of the DITA-OT bin distribution and place it in the lib
directory where the doc tree was checked out." It still simplifies
the setup process for building the documentation and everyone can be
on the same page with their doc build.
My hope is that we can treat the DITA toolkit like a third-party ASL-
licensed library and check it into the repo, once any necessary
checks have been done.
andrew
Re: [doc] DITA-OT in Derby svn
Posted by Jeff Levitt <de...@mylevita.com>.
--- "Jean T. Anderson" <jt...@bristowhill.com> wrote:
> 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
> applicable.
>
> 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.
>
> -jean
>
>
>
> > 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
>
>
Thanks Andrew and Jean,
When this is all done (whatever process you work out),
I'd be happy to update the instructions on the DITA
manuals page to whatever ends up being required
(number 4 in Andrew's list of to-do's above).
Jeff
Re: [doc] DITA-OT in Derby svn
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
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
applicable.
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.
-jean
> 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