incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: incubator-site/src/documentation/content/xdocs/drafts glossary.xml
Date Tue, 05 Nov 2002 14:04:25 GMT
jim         2002/11/05 06:04:25

  Modified:    src/documentation/content/xdocs process.xml
               src/documentation/content/xdocs/drafts glossary.xml
  Some docs updates
  Revision  Changes    Path
  1.4       +18 -4     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.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- process.xml	4 Nov 2002 18:55:39 -0000	1.3
  +++ process.xml	5 Nov 2002 14:04:25 -0000	1.4
  @@ -6,6 +6,7 @@
         <person name="Rodent of Unusual Size" email="" />
  +      <person name="Jim Jagielski" email="" />
       <abstract>What it means to go through the Incubator.</abstract>
  @@ -24,10 +25,10 @@
         or be born there.  Here are some of the ways a codebase might
         get here:</p>
  -        <li>Some group external to the Foundation wants to donate a
  -        codebase;</li>
  +        <li>Some group external to the Foundation wants to donate an
  +        existing codebase;</li>
           <li>Some existing Foundation [sub]project wants to build up
  -        viability and a community;</li>
  +        viability and a community around a codebase;</li>
           <li>Some group of people within the Foundation want to start
           a new codebase and build a community around it;</li>
  @@ -73,7 +74,6 @@
           <li>All software in the codebase will need to be licensed
           (or multi-licensed) under the
           <link href="">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>
  @@ -91,6 +91,20 @@
           is otherwise following the Apache guidelines;</li>
           <li>The community has decided on a policy for the
           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>
  +          <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>
  +          <li>The expected timeframe that the incubated project will
  +          stay in the incubator. This is determined by mutual consent
  +          among the codebase, the graduation PMC and the Incubator.</li>
  +          <li>The "graduation requirements" before the codebase can
  +          leave the Incubator. Basically, what are the pre-defined goals
  +          that must be met before the codebase can leave the Incubator</li>
  +         </ol>
  +        </li>
           <li>[what else?]</li>
         <p>TBD.  Licensing, copyright, steering ctte, voting, guidelines, ..</p>
  1.6       +15 -4     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.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- glossary.xml	5 Nov 2002 12:40:02 -0000	1.5
  +++ glossary.xml	5 Nov 2002 14:04:25 -0000	1.6
  @@ -7,9 +7,10 @@
       <title>Apache Glossary</title>
  -      <person name="Rodent of Unusual Size" email="" />
         <person name="Aaron Bannert" email="" />
  +      <person name="Rodent of Unusual Size" email="" />
         <person name="Vadim Gritsenko" email="" />
  +      <person name="Jim Jagielski" email="" />
         <person name="Andrew C. Oliver" email="" />
         <person name="Sam Ruby" email="" />
  @@ -35,7 +36,7 @@
           <link href="http://ApacheCon.Com/">ApacheCon Web site</link>).</dd>
           <dt><strong><anchor id="ASF"/>ASF</strong></dt>
  -        <dd>The Apache Software Foundation.</dd>
  +        <dd>The Apache Software Foundation, a non-profit organization.</dd>
           <dt><strong><anchor id="Attic"/>Attic</strong></dt>
           <dd>A special directory in a
  @@ -83,7 +84,12 @@
           <dt><strong><anchor id="CommitAccess"/>Commit access</strong></dt>
  -        <dd>TBD.  Also see <em><link href="#Karma">Karma</link></em>.</dd>
  +        <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
  +        patches the actual offical code.
  +        Also see <em><link href="#Karma">Karma</link></em>.</dd>
           <dt><strong><anchor id="Committer"/>Committer</strong></dt>
           <dd>An individual who has been granted the privilege of being
  @@ -103,7 +109,12 @@
           <dt><strong><anchor id="Contributor"/>Contributor</strong></dt>
  -        <dd>TBD</dd>
  +        <dd>Someone who makes consistent improvements to the entities
  +        under an ASF PMC, 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
  +        such access.</dd>
           <dt><strong><anchor id="CVS"/>CVS</strong></dt>
           <dd>The Concurrent Versioning System, a code management system

View raw message