[prev in list] [next in list] [prev in thread] [next in thread] 

List:       incubator-cvs
Subject:    cvs commit: incubator-site/src/documentation/content/xdocs/drafts glossary.xml
From:       coar () apache ! org
Date:       2002-11-05 20:09:43
[Download RAW message or body]

coar        2002/11/05 12:09:43

  Modified:    src/documentation/content/xdocs process.xml
               src/documentation/content/xdocs/drafts glossary.xml
  Log:
  some xml fixups and other minor tweaks (like xrefs)
  
  Revision  Changes    Path
  1.5       +2 -1      incubator-site/src/documentation/content/xdocs/process.xml
  
  Index: process.xml
  ===================================================================
  RCS file: /home/cvs/incubator-site/src/documentation/content/xdocs/process.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -u -r1.4 -r1.5
  --- process.xml	5 Nov 2002 14:04:25 -0000	1.4
  +++ process.xml	5 Nov 2002 20:09:43 -0000	1.5
  @@ -74,6 +74,7 @@
           <li>All software in the codebase will need to be licensed
           (or multi-licensed) under the
           <link href="http://www.apache.org/LICENSE">Apache licence</link>.</li>
  +      </ol>
         <p>This means that the codebase will need to be examined to ensure
         that, if and when the Foundation begins distributing it, it has
         clear title to do so and isn't infringing on anyone's rights.</p>
  @@ -93,7 +94,7 @@
           composition of its 'steering committee';</li>
           <li>The exit strategy for the codebase must be defined up front.
           In particular, the incubated codebase needs to know:
  -         <ol>
  +        <ol>
             <li>What ASF PMC it will be graduating to. This implies
             that the PMC is question is sponsoring, at least in part,
             the incubated codebase.</li>
  
  
  
  1.7       +10 -5     incubator-site/src/documentation/content/xdocs/drafts/glossary.xml
  
  Index: glossary.xml
  ===================================================================
  RCS file: /home/cvs/incubator-site/src/documentation/content/xdocs/drafts/glossary.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -u -r1.6 -r1.7
  --- glossary.xml	5 Nov 2002 14:04:25 -0000	1.6
  +++ glossary.xml	5 Nov 2002 20:09:43 -0000	1.7
  @@ -84,10 +84,12 @@
           <dd>TBD</dd>
   
           <dt><strong><anchor id="CommitAccess"/>Commit access</strong></dt>
  -        <dd>Currently, ASF projects use <code><link href="#CVS">CVS</link></code>
  -        to handle the collaborative versioning control over the code. The ability
  -        to make direct changes to the code that exists under cvs is called
  -        commit access (from the <code>cvs commit</code> command) This process
  +        <dd>Currently, ASF projects use <link href="#CVS">CVS</link>
  +        to handle the collaborative versioning control over the code.
  +        The ability to make direct changes to the code that exists under
  +        CVS control is called
  +        <link href="#CommitAccess">commit access</link>
  +        (from the <code>cvs commit</code> command) This process
           patches the actual offical code.
           Also see <em><link href="#Karma">Karma</link></em>.</dd>
   
  @@ -110,7 +112,10 @@
   
           <dt><strong><anchor id="Contributor"/>Contributor</strong></dt>
           <dd>Someone who makes consistent improvements to the entities
  -        under an ASF PMC, either code or documentation or otherwise.
  +        under an
  +        <link href="#ASF">ASF</link>
  +        <link href="#PMC">PMC</link>,
  +        either code or documentation or otherwise.
           This does not, in and of itself, imply
           <link href="#CommitAccess">commit access</link>, though
           frequent and valued contributors are readily voted on for
  
  
  

[prev in list] [next in list] [prev in thread] [next in thread]