forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-forrest/src/documentation/content/xdocs forrest-contract.xml
Date Sun, 13 Jul 2003 12:34:47 GMT
jefft       2003/07/13 05:34:47

  Modified:    src/documentation/content/xdocs forrest-contract.xml
  Update contract
  Revision  Changes    Path
  1.8       +8 -17     xml-forrest/src/documentation/content/xdocs/forrest-contract.xml
  Index: forrest-contract.xml
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/forrest-contract.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- forrest-contract.xml	24 Apr 2003 04:27:18 -0000	1.7
  +++ forrest-contract.xml	13 Jul 2003 12:34:47 -0000	1.8
  @@ -2,7 +2,8 @@
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
  -    <title>Our Contract</title><authors><person name="Marc Portier"
  +    <title>Our Contract</title>
  +    <authors><person name="Marc Portier" email=""/></authors>

       <notice>The legal tone of this document is just a gimmick, this is not a
         legal document in any sense. At all times: since this is open source: the real
         contract is described in the implementation details of the full distribution.
  @@ -23,7 +24,7 @@
           <li>provide DTDs, skins, cocoon-pipelines, and a willing team of
             supporting developers at the forrest-dev
             <link href="site:mail-lists">mail list</link></li>
  -      <li>use Cocoon to generate the HTML documentation for TheProject</li>

  +      <li>use Cocoon to generate the HTML and PDF documentation for TheProject</li>

  @@ -36,15 +37,12 @@
           <li>provide XML content in <code>{docroot}/content/xdocs</code>
             according to the forrest DTDs,</li> 
           <li>provide content navigation metadata by adding
  -          <code>book.xml</code> and <code>tabs.xml</code> files
in there as well.
  -          (Forrest is working on a libre alternative to the book.xml approach).</li>

  +          <code>site.xml</code> and <code>tabs.xml</code> files
in there as
  +          well.</li>
         <li>provide own xml project descriptor files in the directory <code>{projecthome}</code></li></ul>

  -      <title>TheProject Can (accidentally):</title> 
  -      <warning>Use the following features at your own risk. These are only
  -        <em>side-effects</em> of the current implementation. Perhaps this shouldn't
  -        documented at all.</warning> 
  +      <title>TheProject Can:</title> 
           <li>provide its own skin in a directory
             <code>{docroot}/skins/{your-skin-name}</code> (check the current
Forrest skins
  @@ -58,17 +56,10 @@
             </ul> </li> 
           <li>provide its own overwriting versions of
  -          <code>{docroot}/sitemap.xmap</code>, <code>{docroot}/cocoon.xconf</code>
  +          <code>{docroot}/sitemap.xmap</code> (and other *.xmap files),
  +          <code>{docroot}/cocoon.xconf</code> etc
             ... (be sure you know what you are doing since you're leaving the area where
             other Forresters can help you out.</li> 
  -      </ul> 
  -    </section> 
  -    <section> 
  -      <title>TheProject Cannot (currently)</title> 
  -      <ul> 
  -        <li>provide own Java classes or libraries needed in the generation
  -          process,</li> 
  -        <li>provide mountable sub-sitemaps.</li> 

View raw message