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/src/documentation/content/xdocs/drafts voting.xml book.xml glossary.xml
Date Tue, 05 Nov 2002 12:40:03 GMT
coar        2002/11/05 04:40:03

  Modified:    src/documentation/content/xdocs/drafts book.xml glossary.xml
  Added:       src/documentation/content/xdocs/drafts voting.xml
  Log:
  lots more glossary stuff, and the begginings of voting description
  
  Revision  Changes    Path
  1.5       +1 -0      incubator-site/src/documentation/content/xdocs/drafts/book.xml
  
  Index: book.xml
  ===================================================================
  RCS file: /home/cvs/incubator-site/src/documentation/content/xdocs/drafts/book.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -u -r1.4 -r1.5
  --- book.xml	4 Nov 2002 19:03:36 -0000	1.4
  +++ book.xml	5 Nov 2002 12:40:02 -0000	1.5
  @@ -9,6 +9,7 @@
     <menu label="Documents">
       <menu-item label="Table of Contents" href="index.html"/>
       <menu-item label="Glossary" href="glossary.html"/>
  +    <menu-item label="Voting" href="voting.html"/>
       <menu-item label="'The Apache Way'" href="theapacheway.html"/>
       <!--
             <menu-item label="ASF Structure" href="structure.html" />
  
  
  
  1.5       +177 -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.4
  retrieving revision 1.5
  diff -u -u -r1.4 -r1.5
  --- glossary.xml	4 Nov 2002 20:55:53 -0000	1.4
  +++ glossary.xml	5 Nov 2002 12:40:02 -0000	1.5
  @@ -8,6 +8,10 @@
   
       <authors>
         <person name="Rodent of Unusual Size" email="coar@apache.org" />
  +      <person name="Aaron Bannert" email="abannert@apache.org" />
  +      <person name="Vadim Gritsenko" email="vadim.gritsenko@verizon.net" />
  +      <person name="Andrew C. Oliver" email="acoliver@apache.org" />
  +      <person name="Sam Ruby" email="rubys@apache.org" />
       </authors>
   
       <notice>This document is a WIP (Work In Progress).</notice>
  @@ -33,9 +37,15 @@
           <dt><strong><anchor id="ASF"/>ASF</strong></dt>
           <dd>The Apache Software Foundation.</dd>
   
  +        <dt><strong><anchor id="Attic"/>Attic</strong></dt>
  +        <dd>A special directory in a
  +        <link href="#CVS">CVS</link>
  +        repository in which 'deleted' files are stored and from which
  +        they can be restored at need.</dd>
  +
           <dt><strong><anchor id="Board"/>Board</strong></dt>
           <dd>The nine-person legal governing body of the ASF,
  -        elected by the members.</dd>
  +        elected by the members.  [duties?]</dd>
   
           <dt><strong><anchor id="Bylaws"/>Bylaws</strong></dt>
           <dd>Bylaws are a codification of the rules that some
  @@ -53,29 +63,121 @@
           parts in the organisation bylaws are necessarily null and
           void.</dd>
   
  +        <dt><strong><anchor id="Cemetery"/>Cemetery</strong></dt>
  +        <dd>See <em><link href="#Graveyard">Graveyard</link></em>.</dd>
  +
  +        <dt><strong><anchor id="Chair"/>Chair</strong></dt>
  +        <dd><strong>1.</strong> The Chair of the
  +        <link href="#Board">Board</link>
  +        of
  +        <link href="#Director">Directors</link>
  +        of the
  +        <link href="#ASF">ASF</link>,
  +        responsible for the orderly meeting and functioning of the
  +        Board.
  +        <strong>2.</strong> The official head/leader of a committee,
  +        such as a
  +        <link href="#PMC">project management committee</link>.</dd>
  +
           <dt><strong><anchor id="Codebase"/>Codebase</strong></dt>
           <dd>TBD</dd>
   
           <dt><strong><anchor id="CommitAccess"/>Commit access</strong></dt>
  -        <dd>TBD.</dd>
  +        <dd>TBD.  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
           able to directly commit changes to an Apache codebase
           (<link href="#CommitAccess">commit access</link>).</dd>
   
  +        <dt><strong><anchor id="CommitThenReview"/>Commit-then-Review</strong></dt>
  +        <dd>(Often abbreviated 'CTR' or 'C-T-R'.)  A policy governing
  +        code changes which permits developers to make changes at will,
  +        with the possibility of being retroactively
  +        <link href="#Veto">vetoed</link>.  The C-T-R model is
  +        useful in rapid-prototyping environments, but because of the
  +        lack of mandatory review it may permit more bugs through.  Compare
  +        <em><link href="#ReviewThenCommit">Review-Then-Commit</link></em>.</dd>
  +
           <dt><strong><anchor id="Community"/>Community</strong></dt>
           <dd>TBD</dd>
   
  +        <dt><strong><anchor id="Contributor"/>Contributor</strong></dt>
  +        <dd>TBD</dd>
  +
  +        <dt><strong><anchor id="CVS"/>CVS</strong></dt>
  +        <dd>The Concurrent Versioning System, a code management system
  +        used extensively by the
  +        <link href="#ASF">ASF</link>.
  +        CVS provides the ability to track (and potentially revert)
  +        incremental changes to files, reporting them to a mailing list
  +        as they are made, and can be used concurrently
  +        by many developers.  Almost all of the Foundation's code
  +        is stored in CVS repositories.</dd>
  +
  +        <dt><strong><anchor id="Developer"/>Developer</strong></dt>
  +        <dd>TBD</dd>
  +
  +        <dt><strong><anchor id="Director"/>Director</strong></dt>
  +        <dd>TBD</dd>
  +
           <dt><strong><anchor id="Emeritus"/>Emeritus</strong></dt>
           <dd>A term used to formally designate someone as no longer active,
           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 ona particular project
  +        someone who no longer has time to work on a particular project
           may declare itself emeritus.  Emeritus status indicates
           interest but not activity, as opposed to having resigned.</dd>
   
  +        <dt><strong><anchor id="Graveyard"/>Graveyard</strong></dt>
  +        <dd>A location where discontinued, abandoned, and retired
  +        <link href="#Codebase">codebases</link>
  +        and
  +        <link href="#Project">projects</link>
  +        are stored.  The graveyard preserves the information for
  +        posterity, reference, and potential future re-activation,
  +        while keeping it clearly distinct from active work.</dd>
  +
  +        <dt><strong><anchor id="Hackathon"/>Hackathon</strong></dt>
  +        <dd>Informal event at which ASF participants can get together,
  +        network, and discuss/argue/hack/prototype according to
  +        their interests.  Hackathons are open to all
  +        <link href="#Committer">committers</link> and invited
  +        contributors, and typically take place immediately
  +        preceding or following the
  +        <link href="#ApacheCon">ApacheCon</link>
  +        events.</dd>
  +
  +        <dt><strong><anchor id="Hibernation"/>Hibernation</strong></dt>
  +        <dd>TBD</dd>
  +
  +        <dt><strong><anchor id="Indemnification"/>Indemnification</strong></dt>
  +        <dd>TBD</dd>
  +
  +        <dt><strong><anchor id="Karma"/>Karma</strong></dt>
  +        <dd><strong>1.</strong> Sufficient access to perform an operation,
  +        such as committing changes to a CVS module.  ("Please grant
  +        Yo Mega karma to the foo-bar CVS module.")
  +        <strong>2.</strong> Respect and
  +        <link href="#Merit">merit</link>
  +        in the community.  ("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
  +        indirectly related.</dd>
  +
  +        <dt><strong><anchor id="Lazy consensus"/>Lazy consensus</strong></dt>
  +        <dd>A feature of the
  +        <link href="#CommitThenReview">C-T-R</link>
  +        commit model that assumes general consent if no responses are
  +        posted within a defined period.  For example, "I'm going to
  +        commit this by lazy consensus if no-one objects within the
  +        next three days."  Also see
  +        <em><link href="#CommitThenReview">Commit-Then-Review</link></em>
  +        and
  +        <em><link href="#ReviewThenCommit">Review-Then-Commit</link></em>.</dd>
  +
           <dt><strong><anchor id="Member"/>Member</strong></dt>
           <dd>An individual who has been elected to membership in
           the ASF by the existing members.  Membership benefits
  @@ -151,13 +253,84 @@
           <link href="#Board">Board</link>,
           its actions are considered to be on behalf of the
           Foundation, with all the legal protections and
  -        responsibilities implied.</dd>
  +        responsibilities implied.  See
  +        <em><link href="#Indemnification">Indemnification</link></em>.</dd>
  +
  +        <dt><strong><anchor id="President"/>President</strong></dt>
  +        <dd>Primary executive officer of the
  +        <link href="#ASF">ASF</link>, seriving at the direction of the
  +        <link href="#Board">Board</link>.  [duties?]</dd>
   
           <dt><strong><anchor id="Project"/>Project</strong></dt>
           <dd>In the Apache Software Foundation, the term '<em>project</em>'
           typically refers to a community focussed on one or more
           <link href="#Codebase">codebases</link>, overseen by
           a <link href="#PMC">PMC</link>.</dd>
  +
  +        <dt><strong><anchor id="ReviewThenCommit"/>Review-Then-Commit</strong></dt>
  +        <dd>(Often referenced as 'RTC' or 'R-T-C'.)  Commit policy which
  +        requires that all changes be reviewed and receive at least three +1
  +        <link href="#Vote">votes</link>
  +        -- and no
  +        <link href="#Veto">vetos</link>
  +        -- in order to be committed.  Compare
  +        <em><link href="#CommitThenReview">Commit-Then-Review</link></em>.</dd>
  +
  +        <dt><strong><anchor id="Subversion"/>Subversion</strong></dt>
  +        <dd>TBD</dd>
  +
  +        <dt><strong><anchor id="SVN"/>SVN</strong></dt>
  +        <dd>See <em><link href="#Subversion">Subversion</link></em>.</dd>
  +
  +        <dt><strong><anchor id="Treasurer"/>Treasurer</strong></dt>
  +        <dd>The treasurer of the
  +        <link href="#ASF">ASF</link>
  +        is an
  +        <link href="#Officer">officer</link>
  +        of the corporation, and is responsible for
  +        managing the funds and assets of the Foundation, reporting
  +        tax information, and so on.  The treasurer
  +        need not be a
  +        <link href="#Member">member</link>
  +        of the Foundation, nor a
  +        <link href="#Director">director</link>,
  +        though the r&ocirc;le is often filled by someone who is.</dd>
  +
  +        <dt><strong><anchor id="User"/>User</strong></dt>
  +        <dd>TBD</dd>
  +
  +        <dt><strong><anchor id="Veto"/>Veto</strong></dt>
  +        <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
  +        <link href="#ReviewThenCommit">R-T-C</link>
  +        commit policy is in effect, a veto prevents the change from
  +        being made.  In either the R-T-C or
  +        <link href="#CommitThenReview">C-T-R</link>
  +        environments, a veto applied to a change that has already been
  +        made forces it to be reverted.  Vetos may not be overridden
  +        nor voted down, and only cease to apply when the committer
  +        who issued the veto withdraws it.  All vetos <em>must</em>
  +        be accompanied by a valid technical justification; a veto
  +        without such a justification is invalid.  Vetos only apply to
  +        code changes; they do not apply to procedural issues
  +        such as software releases.</dd>
  +
  +        <dt><strong><anchor id="Vice-President"/>Vice-President</strong></dt>
  +        <dd><link href="#ASF">ASF</link>
  +        vice-presidents are
  +        <link href="#Officer">officers</link>
  +        of the corporation, with authority over and responsibility for
  +        specific areas of the Foundation's work.
  +        <link href="#PMC">PMC</link>
  +        <link href="#Chair">chairs</link>
  +        are vice-presidents given charge of the proper operation
  +        of their projects.</dd>
  +
  +        <dt><strong><anchor id="Vote"/>Vote</strong></dt>
  +        <dd>TBD.</dd>
  +
         </dl>
   
       </section>
  
  
  
  1.1                  incubator-site/src/documentation/content/xdocs/drafts/voting.xml
  
  Index: voting.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
  <document>
    <header>
      <title>Apache Voting Process</title>
  
      <authors>
        <person name="Rodent of Unusual Size" email="coar@apache.org" />
      </authors>
  
      <notice>This document is a WIP (Work In Progress).</notice>
  
      <abstract>Description of how voting works in Apache.</abstract>
    </header>
  
    <body>
      <section>
        <title>Consensus Gauging through Voting</title>
        <p>Because one of the fundamental aspects of accomplishing things
        within the Apache framework is doing so by consensus, there obviously
        needs to be a way to tell whether it has been reached.  This is
        done by voting.</p>
        <p>There are essentially two types of voting:</p>
        <p/>
        <ol>
          <li>Code inclusion, and</li>
          <li>Procedural.</li>
        </ol>
        <p/>
        <p></p>
  
        <section>
          <title>Binding Votes</title>
          <p></p>
        </section>
  
        <section>
          <title>Expressing Votes: +1, 0, -1, and Fractions</title>
          <p></p>
        </section>
  
        <section>
          <title>Vetos</title>
          <p></p>
        </section>
  
      </section>
  
      <section>
        <title>Consensus Gauging through Silence</title>
        <p>An alternative to voting that is sometimes used to measure
        the acceptability of something is the concept of
        <em>lazy consensus</em>.</p>
        <p>Lazy consensus is simply an announcement of 'silence gives
        assent.'  When someone wants to determine the sense of the community
        this way, it might do so with a mail message such as:</p>
        <p/>
        <dl>
          <dt/>
          <dd>"The patch below fixes bug #8271847; if no-one objects
          within three days, I'll assume lazy consensus and commit it."</dd>
        </dl>
        <p/>
        <p>Lazy consensus cannot be applied to code changes when the
        <link href="glossary.html#ReviewThenCommit">review-then-commit</link>
        policy is in effect.</p>
      </section>
    </body>
  </document>
  
  
  

Mime
View raw message