incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject cvs commit: incubator-site/build/site/drafts glossary.html glossary.pdf
Date Tue, 03 Dec 2002 19:20:26 GMT
coar        2002/12/03 11:20:26

  Modified:    build/site/drafts glossary.html glossary.pdf
  Log:
  update the generated files for the site
  
  Revision  Changes    Path
  1.10      +93 -23    incubator-site/build/site/drafts/glossary.html
  
  Index: glossary.html
  ===================================================================
  RCS file: /home/cvs/incubator-site/build/site/drafts/glossary.html,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -u -r1.9 -r1.10
  --- glossary.html	3 Dec 2002 18:44:36 -0000	1.9
  +++ glossary.html	3 Dec 2002 19:20:26 -0000	1.10
  @@ -224,7 +224,24 @@
   </dt>
           
   <dd>The nine-person legal governing body of the ASF,
  -        elected by the members.  [duties?]</dd>
  +        elected by the
  +        <a href="#Member">members</a>.
  +        The board provides the oversight of the Foundation's
  +        activities and operation, and has the responsibility of
  +        applying and enforcing the ASF's
  +        <a href="#Bylaws">bylaws</a>.
  +        Among other things, the board approves or rejects resolutions
  +        brought before it, such as for the creation or dissolution of
  +        ASF
  +        <a href="#Project">projects</a>,
  +        funding requests, legal concerns, and disciplinary
  +        actions.  As an open and non-profit corporation, the minutes
  +        of the board's meetings are publicly available at
  +        &lt;URL:<a href="http://www.apache.org/foundation/records/minutes/">http://www.apache.org/foundation/records/minutes/</a>&gt;.
  +        These minutes include all decisions not made in
  +        <a href="#ExecutiveSession">executive session</a>.
  +        Also see
  +        <em><a href="#Director">Director</a></em>.</dd>
   
           
   <dt>
  @@ -237,7 +254,9 @@
           are legally binding and have significance outside the
           organisation.  Others, such as the
           <a href="http://jakarta.apache.org/site/management.html">Jakarta bylaws</a>,
  -        are only meaningful within the community and are only
  +        are only meaningful within the
  +        <a href="#Community">community</a>
  +        and are only
           as binding as the community itself makes them.  The
           bylaws of an organisation within the ASF may not
           contradict those of the ASF proper; any such conflicting
  @@ -274,14 +293,22 @@
   <a name="Codebase"></a><strong>Codebase</strong>
   </dt>
           
  -<dd>TBD</dd>
  +<dd>Generally, a standalone
  +        <a href="#CVS">CVS</a>
  +        module for a particular package.  For example, the sources
  +        for the Xerces-C and Xerces-J packages represent separate
  +        codebases.  Some
  +        <a href="#Project">projects</a>
  +        involve only a single codebase, while others have several.</dd>
   
           
   <dt>
   <a name="CommitAccess"></a><strong>Commit access</strong>
   </dt>
           
  -<dd>Currently, ASF projects use <a href="#CVS">CVS</a>
  +<dd>Currently, ASF
  +        <a href="#Project">projects</a>
  +        use <a href="#CVS">CVS</a>
           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 <emphasis>commit access</emphasis>
  @@ -295,14 +322,15 @@
   </dt>
           
   <dd>An individual who has been granted the privilege of being
  -        able to directly commit changes to an Apache codebase
  +        able to directly commit changes to an Apache
  +        <a href="#Codebase">codebase</a>
           (<a href="#CommitAccess">commit access</a>).</dd>
   
           
   <dt>
   <a name="CommitThenReview"></a>
             <strong>
  -            Commit-then-Review
  +            Commit-Then-Review
             </strong>
           
   </dt>
  @@ -320,8 +348,7 @@
           <a href="#ReviewThenCommit">R-T-C</a> alternative.  Compare
           <em><a href="#ReviewThenCommit">Review-Then-Commit</a></em>,
           and see the description of the
  -        <a href="voting.html">voting process</a>
  -</dd>
  +        <a href="voting.html">voting process</a>.</dd>
   
           
   <dt>
  @@ -400,7 +427,15 @@
   <a name="Director"></a><strong>Director</strong>
   </dt>
           
  -<dd>TBD</dd>
  +<dd>One of nine individuals elected by the
  +        <a href="#Member">members</a>
  +        to the Foundation's
  +        <a href="#Board">board of directors</a>.
  +        Directors may or may not have individual responsibilities,
  +        but all are generally expected to stay informed about as
  +        much of the Foundation's operations and activity as possible,
  +        since the Board provides oversight for the Foundation as
  +        a whole.</dd>
   
           
   <dt>
  @@ -411,7 +446,8 @@
           but still entitled to all of the rights and privileges of the
           position.  For example, an ASF member who hasn't attended
           any membership meetings for a long time is declared emeritus;
  -        someone who no longer has time to work on a particular project
  +        someone who no longer has time to work on a particular
  +        <a href="#Project">project</a>
           may declare itself emeritus.  Emeritus status indicates
           interest but not activity, as opposed to having resigned.</dd>
   
  @@ -426,6 +462,18 @@
   
           
   <dt>
  +<a name="ExecutiveSession"></a><strong>Executive Session</strong>
  +</dt>
  +        
  +<dd>A portion of a
  +        <a href="#Board">board</a>
  +        meeting which concerns confidential matters and which therefore
  +        cannot be publicly minuted.  Examples include salary
  +        discussions, areas covered by non-disclosure agreements,
  +        disciplinary actions, and some types of funding decisions.</dd>
  +
  +        
  +<dt>
   <a name="Graveyard"></a><strong>Graveyard</strong>
   </dt>
           
  @@ -476,7 +524,9 @@
           Yo Mega karma to the foo-bar CVS module.")
           <strong>2.</strong> Respect and
           <a href="#Merit">merit</a>
  -        in the community.  ("Al Faa has good karma because of the
  +        in the
  +        <a href="#Community">community</a>.
  +        ("Al Faa has good karma because of the
           careful and tactful way he makes his points and the quality
           of his technical contributions.")
           <strong>3.</strong> Any combination of senses 1 and two; they are
  @@ -544,7 +594,9 @@
   </dt>
           
   <dd>The concept of 'merit' is central to the Apache
  -        philosophy and community methodology.  Merit is a qualitative
  +        philosophy and
  +        <a href="#Community">community</a>
  +        methodology.  Merit is a qualitative
           and subjective term, referring essentially to attributes
           such as those below; however, it can probably be summed up
           as the combination of the worth of one's accomplishments
  @@ -575,7 +627,9 @@
   <dd>Meritocracy is one of the principles underlying the
           ASF and its philosophy.  As it has been put, 'the more you do
           the more you are allowed to do.'  As a person acquires merit,
  -        his or her stature in the community grows, and (to a certain extent)
  +        his or her stature in the
  +        <a href="#Community">community</a>
  +        grows, and (to a certain extent)
           the weight given to his or her opinions.</dd>
   
           
  @@ -599,7 +653,9 @@
             attitudes, and issues, as well as existing rules for
             acceptable behaviour</li>
             
  -<li>be aware of the project's/list's guidelines (such as on
  +<li>be aware of the
  +          <a href="#Project">project</a>'s/list's
  +          guidelines (such as on
             voting), and don't violate them</li>
             
   <li>if you have a question, search the list archives and
  @@ -630,8 +686,10 @@
   </dt>
           
   <dd>Project Management Committee, the group of people
  -        with formal oversight of a project.  The chair of a
  -        PMC is always an <a href="#Officer">officer</a>
  +        with formal oversight of a
  +        <a href="#Project">project</a>.
  +        The chair of a PMC is always an
  +        <a href="#Officer">officer</a>
           of the Foundation.  As the PMC has official oversight
           responsibilities assigned by the
           <a href="#Board">Board</a>,
  @@ -645,7 +703,11 @@
   <a name="Podling"></a><strong>Podling</strong>
   </dt>
           
  -<dd>A codebase and its community while in the process of being
  +<dd>A
  +        <a href="#Codebase">codebase</a>
  +        and its
  +        <a href="#Community">community</a>
  +        while in the process of being
           incubated.  See the description of the
           <a href="../process.html#Podling">incubation process</a>.</dd>
   
  @@ -664,7 +726,9 @@
   </dt>
           
   <dd>In the Apache Software Foundation, the term '<em>project</em>'
  -        typically refers to a community focussed on one or more
  +        typically refers to a
  +        <a href="#Community">community</a>
  +        focussed on one or more
           <a href="#Codebase">codebases</a>, overseen by
           a <a href="#PMC">PMC</a>.</dd>
   
  @@ -697,7 +761,8 @@
           Originally described by James Duncan Davison in his
           'Rules for Revolutionaries,' the concept has been
           adopted, formally or informally, by at least one Apache
  -        project.  Essentially, a revolution occurs when a group
  +        <a href="#Project">project</a>.
  +        Essentially, a revolution occurs when a group
           of committers decides to fork the current main branch
           in order to work on problematic code or concepts.  This
           permits them to pursue it without disturbing the evolutionary
  @@ -772,8 +837,9 @@
           
   <dd>According to the Apache methodology, a change which
           has been made or proposed may be made moot through the
  -        exercise of a veto by a committer to the codebase in question.
  -        If the
  +        exercise of a veto by a committer to the
  +        <a href="#Codebase">codebase</a>
  +        in question.  If the
           <a href="#ReviewThenCommit">R-T-C</a>
           commit policy is in effect, a veto prevents the change from
           being made.  In either the R-T-C or
  @@ -801,7 +867,8 @@
           <a href="#PMC">PMC</a>
           <a href="#Chair">chairs</a>
           are vice-presidents given charge of the proper operation
  -        of their projects.</dd>
  +        of their
  +        <a href="#Project">projects</a>.</dd>
   
           
   <dt>
  @@ -817,7 +884,10 @@
             is -1 because foo smells bad.')
             <p>
   <strong>Binding votes</strong> are those cast by
  -          committers in the project or on the codebase to which
  +          committers in the
  +          <a href="#Project">project</a> or on the
  +          <a href="#Codebase">codebase</a>
  +          to which
             the decision applies.  Votes cast by others are
             advisory or indicative only.</p>
             See also
  
  
  
  1.8       +1174 -615 incubator-site/build/site/drafts/glossary.pdf
  
  	<<Binary file>>
  
  

Mime
View raw message