logging-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject cvs commit: logging-site/src/xdocs/stylesheets project.xml
Date Mon, 22 Dec 2003 17:41:25 GMT
ceki        2003/12/22 09:41:24

  Modified:    docs     index.html
               docs/site bylaws.html news.html
               src/xdocs/site bylaws.xml
               src/xdocs/stylesheets project.xml
  Added:       docs/css site.css
               docs/images paul-glezen.jpg
               src/xdocs/site mission-statement.xml
  Log:
  work in progress
  
  Revision  Changes    Path
  1.8       +1 -1      logging-site/docs/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/index.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- index.html	22 Dec 2003 15:08:40 -0000	1.7
  +++ index.html	22 Dec 2003 17:41:24 -0000	1.8
  @@ -80,7 +80,7 @@
         	      	  <tr >
         	    <td><strong>Information</strong></td>
         	  </tr>
  -      	        	      <tr><td>&nbsp;&nbsp;    <a href="./site/mission.html">Mission statement</a>
  +      	        	      <tr><td>&nbsp;&nbsp;    <a href="./site/mission-statement.html">Mission statement</a>
   </td></tr>
         	          	      <tr><td>&nbsp;&nbsp;    <a href="./site/bylaws.html">Bylaws</a>
   </td></tr>
  
  
  
  1.1                  logging-site/docs/css/site.css
  
  Index: site.css
  ===================================================================
  H1 {
   color: #2222AA;
  }
  
  H2 {
   color: #2222AA;
  }
  
  H3 {
   color: #2222AA;
  }
  
  
  A {
    text-decoration: none;
    /* color: #006699;  */
  }
  A:link {
    text-decoration: none;
    color: #0077AA;
    /* color: #006699;  */
  }
  
  A:visited {
    text-decoration: none;
    color: #006699;
  }
  
  A:hover {
    text-decoration: underline;
    color: #006699;
  }
  
  P {
   /*  font  : 11pt trebuchet MS, Arial, Helvetica, sans-serif; */
  }
  
  TD {
   /*  font : 11pt trebuchet MS, Arial, Helvetica, sans-serif; */
  }
  
  /*
  TD.MENU {
    color: #003366;
    font : 10pt trebuchet MS, Arial, Helvetica, sans-serif;
  }
  
  
  TR.MENU {
    color: #003366;
    font : 10pt trebuchet MS, Arial, Helvetica, sans-serif;
    background-color: #ffcc99;
  }
  */
  
  .MENU {
    background-color: #ffcc99;
    color: #aa7766;
    font-weight: bold;
    /* color : #4444FF; */
  }
  
  .listprice { 
    text-decoration: line-through;   
  }
  
  
  
  
  1.1                  logging-site/docs/images/paul-glezen.jpg
  
  	<<Binary file>>
  
  
  1.2       +583 -14   logging-site/docs/site/bylaws.html
  
  Index: bylaws.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/bylaws.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- bylaws.html	22 Dec 2003 15:09:14 -0000	1.1
  +++ bylaws.html	22 Dec 2003 17:41:24 -0000	1.2
  @@ -80,7 +80,7 @@
         	      	  <tr >
         	    <td><strong>Information</strong></td>
         	  </tr>
  -      	        	      <tr><td>&nbsp;&nbsp;    <a href="../site/mission.html">Mission statement</a>
  +      	        	      <tr><td>&nbsp;&nbsp;    <a href="../site/mission-statement.html">Mission statement</a>
   </td></tr>
         	          	      <tr><td>&nbsp;&nbsp;    <a href="../site/bylaws.html">Bylaws</a>
   </td></tr>
  @@ -111,20 +111,589 @@
                       <td width="80%" align="left" valign="top">
                          <div style="position: relative; left: 8px;">
   	                                                                  <h1>Bylaws</h1>
  -                                                                                                   <p>This document defines the guidelines for the <a href="../index.html">Apache Logging Services Project</a>. It includes
  -    definitions of how conflict is resolved by voting, who is able to
  -    vote, and the procedures to follow for proposing and making
  -    changes to the Apache products.</p>
  -                                                                                                   <p>The objective here is to avoid unnecessary conflict over
  -    changes and continue to produce a quality system in a timely
  -    manner. Not all conflict can be avoided, but at least we can agree
  -    on the procedures for conflict to be resolved.
  +                                                                                                   <p>This document defines the bylaws under which the Apache Logging
  +   Services project operates. It defines the roles and
  +   responsibilities of the project, who may vote, how voting works,
  +   how conflicts are resolved, etc.
  +   </p>
  +                                                                                                   <p>The Logging Services is a project of the
  +   <a href="http://www.apache.org/foundation/">Apache Software
  +   Foundation</a>. The foundation holds the copyright on Apache
  +   code including the code in the Logging Services codebase. The <a href="http://www.apache.org/foundation/faq.html">foundation FAQ</a>
  +   explains the operation and background of the foundation.
  +   </p>
  +                                                                                                   <p>Logging Services is typical of Apache projects in that it
  +   operates under a set of principles, known collectively as the
  +   "Apache Way". If you are new to Apache development, please refer to
  +   the <a href="http://incubator.apache.org">Incubator project</a> for
  +   more information on how Apache projects operate.
  +   </p>
  +                                                                                                   <ul>
  +     <li><a href="#Roles and Responsibilities">Roles and Responsibilities</a></li>
  +      <li><a href="#Decision Making">How decisions are made</a></li>
  +   </ul>
  +                                                                                                   <h2><a name="Roles and Responsibilities" />
  +      Roles and Responsibilities
  +    </h2>
  +                                                                                                   <p>Apache projects define a set of roles with associated rights
  +      and responsibilities. These roles govern what tasks an
  +      individual may perform within the project. The roles are defined
  +      in the following sections
       </p>
  -                                                                                                   <h2>some subsection</h2>
  -                                                                                                   <p>This document defines the guidelines for the <a href="index.html">Apache Logging Services Project</a>. It includes
  -    definitions of how conflict is resolved by voting, who is able to
  -    vote, and the procedures to follow for proposing and making
  -    changes to the Apache products.</p>
  +                                                                                                   <ul>
  +      <li><a href="#Users">Users</a></li>
  +      <li><a href="#Developers">Developers</a></li>
  +      <li><a href="#Committers">Committers</a></li>
  +      <li><a href="#Project Management Committee">
  +        Project Management Committee (PMC)</a>
  +      </li>
  +    </ul>
  +                                                                                                   <h3 class="subsection">
  +        <a name="Users" />
  +        Users
  +     </h3>
  +                                                                                                   <p>The most important participants in the project are people who
  +     use our software. The majority of our developers start out as
  +     users and guide their development efforts from the user's
  +     perspective.
  +      </p>
  +                                                                                                   <p>Users contribute to the Apache projects by providing feedback
  +        to developers in the form of bug reports and feature
  +        suggestions. As well, users participate in the Apache
  +        community by helping other users on mailing lists and user
  +        support forums.
  +     </p>
  +                                                                                                   <h3 class="subsection">
  +      <a name="Developers" />
  +        Developers
  +     </h3>
  +                                                                                                   <p>All of the volunteers who are contributing time, code,
  +     documentation, or resources to the Logging Services Project. A developer that
  +     makes sustained, welcome contributions to the project may be
  +     invited to become a Committer, though the exact timing of such
  +     invitations depends on many factors.
  +      </p>
  +                                                                                                   <h3 class="subsection"><a name="Committers" />Committers</h3>
  +                                                                                                   <p>The project's Committers are responsible for the project's
  +     technical management. All committers have write access to the
  +     project's source repositories. Committers may cast binding votes
  +     on any technical discussion regarding the project.
  +      </p>
  +                                                                                                   <p>Committer access is by invitation only and must be approved by
  +     lazy consensus of the active PMC members. A Committer is
  +     considered emeritus by their own declaration or by not
  +     contributing in any form to the project for over six months. An
  +     emeritus committer may request reinstatement of commit access
  +     from the PMC. Such reinstatement is subject to lazy consensus of
  +     active PMC members.
  +      </p>
  +                                                                                                   <p>Commit access can be revoked by a unanimous vote of all the
  +     active PMC members (except the committer in question if they are
  +     also a PMC member).</p>
  +                                                                                                   <p>All Apache committers are required to have a signed
  +     Contributor License Agreement (CLA) on file with the Apache
  +     Software Foundation. There is a <a href="http://www.apache.org/dev/committers.html">Committer
  +     FAQ</a> which provides more details on the requirements for
  +     Committers.</p>
  +                                                                                                   <p>A committer who makes a sustained contribution to the project
  +     may be invited to become a member of the PMC. The form of
  +     contribution is not limited to code. It can also include code
  +     review, helping out users on the mailing lists, documentation,
  +     etc.
  +     </p>
  +                                                                                                   <h3 class="subsection"><a name="Project Management Committee" />Project Management Committee
  +      </h3>
  +                                                                                                   <p>The Project Management Committee (PMC) for Apache Logging Services was
  +      created by a <a href="mission.html">resolution</a> of the board
  +      of the Apache Software Foundation on 18<sup>th</sup> November
  +      2002. The PMC is responsible to the board and the ASF for the
  +      management and oversight of the Apache Logging Services codebase. The
  +      responsibilities of the PMC include
  +      </p>
  +                                                                                                   <ul>
  +        <li>Deciding what is distributed as products of the Apache Logging Services project.
  +            In particular all releases must be approved by the PMC
  +        </li>
  +        <li>Maintaining the project's shared resources, including the codebase
  +            repository, mailing lists, websites.
  +        </li>
  +        <li>Speaking on behalf of the project.
  +        </li>
  +        <li>Resolving license disputes regarding products of the project
  +        </li>
  +        <li>Nominating new PMC members and committers
  +        </li>
  +        <li>Maintaining these bylaws and other guidelines of the project
  +        </li>
  +      </ul>
  +                                                                                                   <p>Membership of the PMC is by invitation only and must be
  +      approved by a lazy consensus of active PMC members. A PMC member
  +      is considered "emeritus" by their own declaration or by not
  +      contributing in any form to the project for over six months. An
  +      emeritus member may request reinstatement to the PMC. Such
  +      reinstatement is subject to lazy consensus of the active PMC
  +      members. Membership of the PMC can be revoked by an unanimous
  +      vote of all the active PMC members other than the member in
  +      question.
  +      </p>
  +                                                                                                   <p>The chair of the PMC is appointed by the ASF board. The chair
  +     is an office holder of the Apache Software Foundation (Vice
  +     President, Apache Logging Services) and has primary responsibility to the
  +     board for the management of the projects within the scope of the
  +     Logging Services PMC. The chair reports to the board quarterly on developments
  +     within the Logging Services project.  The PMC may consider the position of PMC
  +     chair annually and if supported by 2/3 Majority may recommend a
  +     new chair to the board.  Ultimately, however, it is the board's
  +     responsibility who it chooses to appoint as the PMC chair.
  +     </p>
  +                                                                                                   <h3 class="section"><a name="Decision Making" />Decision Making</h3>
  +                                                                                                   <p>Within the Logging Services project, different types of decisions require
  +     different forms of approval. For example, the <a href="#Roles and      Responsibilities">previous section</a> describes several
  +     decisions which require "lazy consensus" approval. This section
  +     defines how voting is performed, the types of approvals, and
  +     which types of decision require which type of approval.
  +    </p>
  +                                                                                                   <h3 class="subsection"><a name="Voting" />Voting</h3>
  +                                                                                                   <p>Decisions regarding the project are made by votes on the
  +     primary project mailing list (general@logging.apache.org). Where
  +     necessary, PMC voting may take place on the private Logging
  +     Services PMC mailing list.  Votes are clearly indicated by
  +     subject line starting with [VOTE] or [PMC-VOTE]. Votes may
  +     contain multiple items for approval and these should be clearly
  +     separated. Voting is carried out by replying to the vote
  +     mail. Voting may take four flavours
  +      </p>
  +                                                                                                    <table>
  +                        <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>+1</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                "Yes," "Agree," or "the action should be performed." In
  +       general, this vote also indicates a willingness on the behalf
  +       of the voter in "making it happen"
  +       
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>+0</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                This vote indicates a willingness for the action under
  +       consideration to go ahead. The voter, however will not be able
  +       to help.
  +       
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>-0</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                This vote indicates that the voter does not, in general, agree with
  +           the proposed action but is not concerned enough to prevent the
  +           action going ahead.
  +      
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>-1</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                This is a negative vote. On issues where consensus is required,
  +            this vote counts as a <strong>veto</strong>. All vetoes must
  +            contain an explanation of why the veto is appropriate. Vetoes with
  +            no explanation are void. It may also be appropriate for a -1 vote
  +            to include an alternative course of action.          
  +        
  +            </font>
  +</td>
  +            </tr>
  +            </table>
  +                                                                                                   <p>All participants in the Logging Services project are encouraged
  +    to show their agreement with or against a particular action by
  +    voting. For technical decisions, only the votes of active
  +    committers are binding. Non binding votes are still useful for
  +    those with binding votes to understand the perception of an action
  +    in the wider Logging Services community. For PMC decisions, only
  +    the votes of PMC members are binding.</p>
  +                                                                                                   <p>Voting can also be applied to changes made to the Logging Services
  +    codebase. These typically take the form of a veto (-1) in reply to
  +    the commit message sent when the commit is made.</p>
  +                                                                                                   <h3><a name="Approvals" />Approvals </h3>
  +                                                                                                   <p>These are the types of approvals that can be sought. Different
  +       actions require different types of approvals</p>
  +                                                                                                    <table>
  +                        <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>Consensus</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                For this to pass, all voters with binding votes must vote and there
  +          can be no binding vetoes (-1). Consensus votes are rarely required
  +          due to the impracticality of getting all eligible voters to cast a
  +          vote.
  +      
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>Lazy Consensus</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Lazy consensus requires 3 binding +1 votes and no binding vetoes. 
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                
  +          <strong>Lazy Majority</strong>
  +      
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                A lazy majority vote requires 3 binding +1 votes and more binding +1
  +          votes that -1 votes.
  +      
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>Lazy Approval</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                An action with lazy approval is implicitly allowed unless a -1 vote
  +          is received, at which time, depending on the type of action, either
  +          lazy majority or lazy consensus approval must be obtained.
  +      
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>2/3 Majority</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Some actions require a 2/3 majority of active committers or PMC
  +          members to pass. Such actions typically affect the foundation
  +          of the project (e.g. adopting a new codebase to replace an existing
  +          product). The higher threshold is designed to ensure such changes
  +          are strongly supported. To pass this vote requires at least 2/3 of
  +          binding vote holders to vote +1
  +      
  +            </font>
  +</td>
  +            </tr>
  +            </table>
  +                                                                                                   <h3><a name="Vetoes" />Vetoes</h3>
  +                                                                                                   <p>A valid, binding veto cannot be overruled. If a veto is cast, it
  +   must be accompanied by a valid reason explaining the reasons for
  +   the veto. The validity of a veto, if challenged, can be confirmed
  +   by anyone who has a binding vote. This does not necessarily signify
  +   agreement with the veto - merely that the veto is valid.
  +   </p>
  +                                                                                                   <p>If you disagree with a valid veto, you must lobby the person
  +   casting the veto to withdraw their veto. If a veto is not
  +   withdrawn, the action that has been vetoed must be reversed in a
  +   timely manner.</p>
  +                                                                                                   <h3><a name="Actions" />Actions</h3>
  +                                                                                                   <p>This section describes the various actions which are undertaken
  +   within the project, the corresponding approval required for that
  +   action and those who have binding votes over the action.
  +   </p>
  +                                                                                                    <table>
  +                        <tr>
  +                        <th bgcolor="#039acc" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Action
  +            </font>
  +</th>
  +                                <th bgcolor="#039acc" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Description
  +            </font>
  +</th>
  +                                <th bgcolor="#039acc" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Approval
  +            </font>
  +</th>
  +                                <th bgcolor="#039acc" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Binding Votes 
  +            </font>
  +</th>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                 <strong>Code Change</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                A change made to the codebase of a sub-project and committed
  +      by a committer. This includes source code, documentation,
  +      website content, etc.
  +      
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Lazy approval and then lazy consensus.
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Active committers of the relevant sub-project.
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                 <strong>Release Plan</strong> 
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Defines the timetable and actions for a release. The plan also
  +      nominates a Release Manager.
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Lazy majority
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Active committers of the relevant sub-project
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>Product Release</strong> 
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                When a release of one of the sub-project's products is
  +      ready, a vote is required to accept the release as an official
  +      release of the Logging Services project.
  +      
  +      <p>This step ensures the overall supervision by the Logging
  +      Services PMC over its sub-projects.</p>
  +      
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Lazy Majority
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <b>Active PMC members</b>
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>Adoption of New Codebase</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                 
  +
  +        <p>When the codebase for an existing, released product is to
  +        be replaced with an alternative codebase. If such a vote fails
  +        to gain approval, the existing code base will continue.</p>
  +
  +        <p>This also covers the creation of new sub-projects within
  +         the project</p>          
  +      
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                2/3 majority
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Active PMC members
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>Modification of the Bylaws</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Modification of this document
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                2/3 majority
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Active PMC members
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>New Committer</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                When a new committer is proposed for a sub-project.
  +
  +         <p>The PMC must be informed of the result of the
  +         sub-project's vote. 
  +         </p>
  +
  +      
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Lazy consensus
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Active committers of the relevant sub-project
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>New PMC Member</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                When a committer is proposed for the PMC
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Lazy consensus
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Active PMC members
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>Committer Removal</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                 <p>When removal of commit privileges is sought.</p>
  +           <p><b>Note: </b> Such actions will also be referred to the ASF
  +            board by the PMC chair</p>
  +      
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Consensus
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Active PMC members (excluding the committer in question if a
  +          member of the PMC).
  +       
  +            </font>
  +</td>
  +            </tr>
  +                                <tr>
  +                        <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <strong>PMC Member Removal</strong>
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                <p>When removal of a PMC member is sought.</p>
  +            <p><b>Note: </b> Such actions will also be referred to the
  +            ASF board by the PMC chair</p>          
  +      
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Consensus
  +            </font>
  +</td>
  +                                <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top" align="left">
  +    <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  +                Active PMC members (excluding the member in question).
  +            </font>
  +</td>
  +            </tr>
  +            </table>
  +                                                                                                   <h3><a name="Voting Timeframes" />Voting Timeframes</h3>
  +                                                                                                   <p>Votes are open for a period of 72 hours to allow all active
  +  voters time to consider the vote. Votes relating to code changes are
  +  not subject to a strict timetable but should be made as timely as
  +  possible.</p>
                                                                          </div>
   
                       </td>
  
  
  
  1.6       +1 -1      logging-site/docs/site/news.html
  
  Index: news.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/news.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- news.html	22 Dec 2003 15:08:40 -0000	1.5
  +++ news.html	22 Dec 2003 17:41:24 -0000	1.6
  @@ -79,7 +79,7 @@
         	      	  <tr >
         	    <td><strong>Information</strong></td>
         	  </tr>
  -      	        	      <tr><td>&nbsp;&nbsp;    <a href="../site/mission.html">Mission statement</a>
  +      	        	      <tr><td>&nbsp;&nbsp;    <a href="../site/mission-statement.html">Mission statement</a>
   </td></tr>
         	          	      <tr><td>&nbsp;&nbsp;    <a href="../site/bylaws.html">Bylaws</a>
   </td></tr>
  
  
  
  1.4       +400 -18   logging-site/src/xdocs/site/bylaws.xml
  
  Index: bylaws.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/bylaws.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- bylaws.xml	22 Dec 2003 15:08:40 -0000	1.3
  +++ bylaws.xml	22 Dec 2003 17:41:24 -0000	1.4
  @@ -11,27 +11,409 @@
   
   <body>
       <h1>Bylaws</h1>
  +
  +    <p>This document defines the bylaws under which the Apache Logging
  +   Services project operates. It defines the roles and
  +   responsibilities of the project, who may vote, how voting works,
  +   how conflicts are resolved, etc.
  +   </p>
  +
  +   <p>The Logging Services is a project of the
  +   <a href="http://www.apache.org/foundation/">Apache Software
  +   Foundation</a>. The foundation holds the copyright on Apache
  +   code including the code in the Logging Services codebase. The <a
  +   href="http://www.apache.org/foundation/faq.html">foundation FAQ</a>
  +   explains the operation and background of the foundation.
  +   </p>
  +
  +   <p>Logging Services is typical of Apache projects in that it
  +   operates under a set of principles, known collectively as the
  +   "Apache Way". If you are new to Apache development, please refer to
  +   the <a href="http://incubator.apache.org">Incubator project</a> for
  +   more information on how Apache projects operate.
  +   </p>
  +   
  +   <ul>
  +     <li><a href="#Roles and Responsibilities">Roles and Responsibilities</a></li>
  +      <li><a href="#Decision Making">How decisions are made</a></li>
  +   </ul>
  +
  +    <h2><a name="Roles and Responsibilities"></a>
  +      Roles and Responsibilities
  +    </h2>
  +
  +    <p>Apache projects define a set of roles with associated rights
  +      and responsibilities. These roles govern what tasks an
  +      individual may perform within the project. The roles are defined
  +      in the following sections
  +    </p>
  +       
  +    <ul>
  +      <li><a href="#Users">Users</a></li>
  +      <li><a href="#Developers">Developers</a></li>
  +      <li><a href="#Committers">Committers</a></li>
  +      <li><a href="#Project Management Committee">
  +        Project Management Committee (PMC)</a>
  +      </li>
  +    </ul>
  +
  +    <h3 class="subsection">
  +        <a name="Users"></a>
  +        Users
  +     </h3>
       
  -    <p>This document defines the guidelines for the <a
  -    href="../index.html">Apache Logging Services Project</a>. It includes
  -    definitions of how conflict is resolved by voting, who is able to
  -    vote, and the procedures to follow for proposing and making
  -    changes to the Apache products.</p>
  -
  -    <p>The objective here is to avoid unnecessary conflict over
  -    changes and continue to produce a quality system in a timely
  -    manner. Not all conflict can be avoided, but at least we can agree
  -    on the procedures for conflict to be resolved.
  +     <p>The most important participants in the project are people who
  +     use our software. The majority of our developers start out as
  +     users and guide their development efforts from the user's
  +     perspective.
  +      </p>
  +
  +     <p>Users contribute to the Apache projects by providing feedback
  +        to developers in the form of bug reports and feature
  +        suggestions. As well, users participate in the Apache
  +        community by helping other users on mailing lists and user
  +        support forums.
  +     </p>
  +     
  +     <h3 class="subsection">
  +      <a name="Developers"></a>
  +        Developers
  +     </h3>
  +
  +     <p>All of the volunteers who are contributing time, code,
  +     documentation, or resources to the Logging Services Project. A developer that
  +     makes sustained, welcome contributions to the project may be
  +     invited to become a Committer, though the exact timing of such
  +     invitations depends on many factors.
  +      </p>
  +
  +     <h3 class="subsection"><a name="Committers"></a>Committers</h3>
  +
  +     <p>The project's Committers are responsible for the project's
  +     technical management. All committers have write access to the
  +     project's source repositories. Committers may cast binding votes
  +     on any technical discussion regarding the project.
  +      </p>
  + 
  +     <p>Committer access is by invitation only and must be approved by
  +     lazy consensus of the active PMC members. A Committer is
  +     considered emeritus by their own declaration or by not
  +     contributing in any form to the project for over six months. An
  +     emeritus committer may request reinstatement of commit access
  +     from the PMC. Such reinstatement is subject to lazy consensus of
  +     active PMC members.
  +      </p>
  +
  +     <p>Commit access can be revoked by a unanimous vote of all the
  +     active PMC members (except the committer in question if they are
  +     also a PMC member).</p>
  +      
  +     <p>All Apache committers are required to have a signed
  +     Contributor License Agreement (CLA) on file with the Apache
  +     Software Foundation. There is a <a
  +     href="http://www.apache.org/dev/committers.html">Committer
  +     FAQ</a> which provides more details on the requirements for
  +     Committers.</p>
  + 
  +     <p>A committer who makes a sustained contribution to the project
  +     may be invited to become a member of the PMC. The form of
  +     contribution is not limited to code. It can also include code
  +     review, helping out users on the mailing lists, documentation,
  +     etc.
  +     </p>
  +
  +     <h3 class="subsection"><a name="Project Management Committee"></a>Project Management Committee
  +      </h3>
  + 
  +      <p>The Project Management Committee (PMC) for Apache Logging Services was
  +      created by a <a href="mission.html">resolution</a> of the board
  +      of the Apache Software Foundation on 18<sup>th</sup> November
  +      2002. The PMC is responsible to the board and the ASF for the
  +      management and oversight of the Apache Logging Services codebase. The
  +      responsibilities of the PMC include
  +      </p>
  +
  +      <ul>
  +        <li>Deciding what is distributed as products of the Apache Logging Services project.
  +            In particular all releases must be approved by the PMC
  +        </li>
  +        <li>Maintaining the project's shared resources, including the codebase
  +            repository, mailing lists, websites.
  +        </li>
  +        <li>Speaking on behalf of the project.
  +        </li>
  +        <li>Resolving license disputes regarding products of the project
  +        </li>
  +        <li>Nominating new PMC members and committers
  +        </li>
  +        <li>Maintaining these bylaws and other guidelines of the project
  +        </li>
  +      </ul>
  +      
  +      <p>Membership of the PMC is by invitation only and must be
  +      approved by a lazy consensus of active PMC members. A PMC member
  +      is considered "emeritus" by their own declaration or by not
  +      contributing in any form to the project for over six months. An
  +      emeritus member may request reinstatement to the PMC. Such
  +      reinstatement is subject to lazy consensus of the active PMC
  +      members. Membership of the PMC can be revoked by an unanimous
  +      vote of all the active PMC members other than the member in
  +      question.
  +      </p>
  +
  +    <p>The chair of the PMC is appointed by the ASF board. The chair
  +     is an office holder of the Apache Software Foundation (Vice
  +     President, Apache Logging Services) and has primary responsibility to the
  +     board for the management of the projects within the scope of the
  +     Logging Services PMC. The chair reports to the board quarterly on developments
  +     within the Logging Services project.  The PMC may consider the position of PMC
  +     chair annually and if supported by 2/3 Majority may recommend a
  +     new chair to the board.  Ultimately, however, it is the board's
  +     responsibility who it chooses to appoint as the PMC chair.
  +     </p>
  +
  +     <h3 class="section"><a name="Decision Making"></a>Decision Making</h3>
  +                        
  +     <p>Within the Logging Services project, different types of decisions require
  +     different forms of approval. For example, the <a href="#Roles and
  +     Responsibilities">previous section</a> describes several
  +     decisions which require "lazy consensus" approval. This section
  +     defines how voting is performed, the types of approvals, and
  +     which types of decision require which type of approval.
       </p>
  -  
  -    <h2>some subsection</h2>
  -  
  -    <p>This document defines the guidelines for the <a
  -    href="index.html">Apache Logging Services Project</a>. It includes
  -    definitions of how conflict is resolved by voting, who is able to
  -    vote, and the procedures to follow for proposing and making
  -    changes to the Apache products.</p>
  + 
  +     <h3 class="subsection"><a name="Voting"></a>Voting</h3>
  +
  +     <p>Decisions regarding the project are made by votes on the
  +     primary project mailing list (general@logging.apache.org). Where
  +     necessary, PMC voting may take place on the private Logging
  +     Services PMC mailing list.  Votes are clearly indicated by
  +     subject line starting with [VOTE] or [PMC-VOTE]. Votes may
  +     contain multiple items for approval and these should be clearly
  +     separated. Voting is carried out by replying to the vote
  +     mail. Voting may take four flavours
  +      </p>
  + 
  +     <table cellspacing="1" cellpadding="4">
  +     <tr>
  +       <td><strong>+1</strong></td> 
  +       <td>"Yes," "Agree," or "the action should be performed." In
  +       general, this vote also indicates a willingness on the behalf
  +       of the voter in "making it happen"
  +       </td>
  +     </tr>
  +     <tr>
  +       <td><strong>+0</strong></td>
  +       <td>This vote indicates a willingness for the action under
  +       consideration to go ahead. The voter, however will not be able
  +       to help.
  +       </td>
  +     </tr>
  +     <tr>
  +       <td><strong>-0</strong></td>
  +       <td>This vote indicates that the voter does not, in general, agree with
  +           the proposed action but is not concerned enough to prevent the
  +           action going ahead.
  +      </td>
  +      </tr>
  +      <tr>
  +        <td><strong>-1</strong></td>
  +        <td>This is a negative vote. On issues where consensus is required,
  +            this vote counts as a <strong>veto</strong>. All vetoes must
  +            contain an explanation of why the veto is appropriate. Vetoes with
  +            no explanation are void. It may also be appropriate for a -1 vote
  +            to include an alternative course of action.          
  +        </td>
  +      </tr>
  +    </table>
  + 
  +    <p>All participants in the Logging Services project are encouraged
  +    to show their agreement with or against a particular action by
  +    voting. For technical decisions, only the votes of active
  +    committers are binding. Non binding votes are still useful for
  +    those with binding votes to understand the perception of an action
  +    in the wider Logging Services community. For PMC decisions, only
  +    the votes of PMC members are binding.</p>
  +            
  +    <p>Voting can also be applied to changes made to the Logging Services
  +    codebase. These typically take the form of a veto (-1) in reply to
  +    the commit message sent when the commit is made.</p>
  +                                                    
  +    <h3><a name="Approvals"></a>Approvals </h3>
  +
  +    <p>These are the types of approvals that can be sought. Different
  +       actions require different types of approvals</p>
  +
  +    <table>
  +    <tr>
  +      <td><strong>Consensus</strong></td>
  +      <td>For this to pass, all voters with binding votes must vote and there
  +          can be no binding vetoes (-1). Consensus votes are rarely required
  +          due to the impracticality of getting all eligible voters to cast a
  +          vote.
  +      </td>
  +    </tr>
  +    <tr>
  +      <td><strong>Lazy Consensus</strong></td>
  +      <td>Lazy consensus requires 3 binding +1 votes and no binding vetoes. </td>
  +    </tr>
  +    <tr>
  +      <td>
  +          <strong>Lazy Majority</strong>
  +      </td>
  +      <td>A lazy majority vote requires 3 binding +1 votes and more binding +1
  +          votes that -1 votes.
  +      </td>
  +    </tr>
  +    <tr>
  +      <td><strong>Lazy Approval</strong></td>
  +      <td>An action with lazy approval is implicitly allowed unless a -1 vote
  +          is received, at which time, depending on the type of action, either
  +          lazy majority or lazy consensus approval must be obtained.
  +      </td>
  +    </tr>
  +    <tr>
  +      <td><strong>2/3 Majority</strong></td>
  +      <td>Some actions require a 2/3 majority of active committers or PMC
  +          members to pass. Such actions typically affect the foundation
  +          of the project (e.g. adopting a new codebase to replace an existing
  +          product). The higher threshold is designed to ensure such changes
  +          are strongly supported. To pass this vote requires at least 2/3 of
  +          binding vote holders to vote +1
  +      </td>
  +    </tr>
  +  </table>
  +
  +   <h3><a name="Vetoes"></a>Vetoes</h3>
  +      
  +   <p>A valid, binding veto cannot be overruled. If a veto is cast, it
  +   must be accompanied by a valid reason explaining the reasons for
  +   the veto. The validity of a veto, if challenged, can be confirmed
  +   by anyone who has a binding vote. This does not necessarily signify
  +   agreement with the veto - merely that the veto is valid.
  +   </p>
  +
  +   <p>If you disagree with a valid veto, you must lobby the person
  +   casting the veto to withdraw their veto. If a veto is not
  +   withdrawn, the action that has been vetoed must be reversed in a
  +   timely manner.</p>
  +
  +   <h3><a name="Actions"></a>Actions</h3>
  + 
  +   <p>This section describes the various actions which are undertaken
  +   within the project, the corresponding approval required for that
  +   action and those who have binding votes over the action.
  +   </p>
  +
  +   <table cellspacing="1" cellpadding="4">
  +    <tr>
  +      <th>Action</th>
  +      <th>Description</th>
  +      <th>Approval</th>
  +      <th>Binding Votes </th>
  +    </tr>
  +    <tr>
  +      <td> <strong>Code Change</strong></td> 
  +
  +      <td>A change made to the codebase of a sub-project and committed
  +      by a committer. This includes source code, documentation,
  +      website content, etc.
  +      </td>
  +      <td>Lazy approval and then lazy consensus.</td>
  +      <td>Active committers of the relevant sub-project.</td>
  +    </tr>
  +
  +    <tr>
  +      <td> <strong>Release Plan</strong> </td>
  +      <td>Defines the timetable and actions for a release. The plan also
  +      nominates a Release Manager.</td>
  +      <td>Lazy majority</td>
  +      <td>Active committers of the relevant sub-project</td>
  +    </tr>
  +
  +    <tr>
  +      <td><strong>Product Release</strong> </td>
  +      <td>When a release of one of the sub-project's products is
  +      ready, a vote is required to accept the release as an official
  +      release of the Logging Services project.
  +      
  +      <p>This step ensures the overall supervision by the Logging
  +      Services PMC over its sub-projects.</p>
  +      </td>
  +     <td>Lazy Majority</td>
  +     <td><b>Active PMC members</b></td>
  +    </tr>
  +
  +    <tr>
  +      <td><strong>Adoption of New Codebase</strong></td>
  +      <td> 
  +
  +        <p>When the codebase for an existing, released product is to
  +        be replaced with an alternative codebase. If such a vote fails
  +        to gain approval, the existing code base will continue.</p>
  +
  +        <p>This also covers the creation of new sub-projects within
  +         the project</p>          
  +      </td>
  +      <td>2/3 majority</td>
  +      <td>Active PMC members</td>
  +    </tr>
  +
  +    <tr>
  +      <td><strong>Modification of the Bylaws</strong></td>
  +      <td>Modification of this document</td>
  +      <td>2/3 majority</td>
  +      <td>Active PMC members</td>
  +    </tr>
  +
  +    <tr>
  +      <td><strong>New Committer</strong></td>
  +      <td>When a new committer is proposed for a sub-project.
  +
  +         <p>The PMC must be informed of the result of the
  +         sub-project's vote. 
  +         </p>
  +
  +      </td>
  +      <td>Lazy consensus</td>
  +      <td>Active committers of the relevant sub-project</td>
  +    </tr>
  +    <tr>
  +      <td><strong>New PMC Member</strong></td>
  +      <td>When a committer is proposed for the PMC</td>
  +      <td>Lazy consensus</td>
  +      <td>Active PMC members</td>
  +    </tr>
  +
  +    <tr>
  +      <td><strong>Committer Removal</strong></td>
  +      <td> <p>When removal of commit privileges is sought.</p>
  +           <p><b>Note: </b> Such actions will also be referred to the ASF
  +            board by the PMC chair</p>
  +      </td>
  +      <td>Consensus</td>
  +      <td>Active PMC members (excluding the committer in question if a
  +          member of the PMC).
  +       </td>
  +    </tr>
  +    <tr> 
  +      <td><strong>PMC Member Removal</strong></td>
  +      <td><p>When removal of a PMC member is sought.</p>
  +            <p><b>Note: </b> Such actions will also be referred to the
  +            ASF board by the PMC chair</p>          
  +      </td>
  +      <td>Consensus</td>
  +      <td>Active PMC members (excluding the member in question).</td>
  +    </tr>
  +  </table>
      
  + 
  +  <h3><a name="Voting Timeframes"></a>Voting Timeframes</h3>
  +  
  +  <p>Votes are open for a period of 72 hours to allow all active
  +  voters time to consider the vote. Votes relating to code changes are
  +  not subject to a strict timetable but should be made as timely as
  +  possible.</p>
   
     </body>
   </document>
  
  
  
  1.1                  logging-site/src/xdocs/site/mission-statement.xml
  
  Index: mission-statement.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
  
    <properties>
      <author email="ceki at apache dot org">Ceki Gulcu</author>
      <title>Mission Statement for the Logging Services Project</title>
    </properties>
  
    <meta name="keywords" content="mission, mission statement logging services"/>
  
  
  <body>
    <h1>Mission statement</h1>
  
    <p>The mission of the Logging Services project is the development
     and maintanance of open-source software for tracing and logging of
     application behavior.
     </p>
  
     <h2>Board resolution</h2>
  
     <p>Logging Services project was created by the following resolution
     of the Board of Directors, dated 2003-12-17.
     </p>
  
  <pre>
     Board Resolution for the creation of the Logging Services PMC 
  
     WHEREAS, the Board of Directors deems it to be in the best
     interests of the Foundation and consistent with the Foundation's
     purpose to establish a Project Management Committee charged with
     the creation and maintenance of open-source software related to the
     logging of application behavior, for distribution at no charge to
     the public.
  
     NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
     (PMC), to be known as the "Apache Logging Services PMC", be and
     hereby is established pursuant to Bylaws of the Foundation; and be
     it further
  
     RESOLVED, that the Apache Logging Services PMC be and hereby is
     responsible for the creation and maintenance of software for
     managing the logging of application behavior, and for related
     software components, based on software licensed to the Foundation;
     and be it further
  
     RESOLVED, that the office of "Vice President, Apache Logging
     Services" be and hereby is created, the person holding such office
     to serve at the direction of the Board of Directors as the chair of
     the Apache Logging Services PMC, and to have primary responsibility
     for management of the projects within the scope of responsibility
     of the Apache Logging Services PMC; and be it further
  
     RESOLVED, that the persons listed immediately below be and hereby
     are appointed to serve as the initial members of the Apache Logging
     Services PMC:
  
        Scott Deboy
        Ceki G&#252;lc&#252;
        Jacob Kjome 
        Yoav Shapira 
        Paul Smith 
        Mark Womack
  
     NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mr. Ceki
     G&#252;lc&#252; be and hereby is appointed to the office of Vice
     President, Apache Logging Services, to serve in accordance with and
     subject to the direction of the Board of Directors and the Bylaws
     of the Foundation until death, resignation, retirement, removal or
     disqualification, or until a successor is appointed; and be it
     further
  
     RESOLVED, that the initial Apache Logging Services PMC be and
     hereby is tasked with the creation of a set of bylaws intended to
     encourage open development and increased participation in the
     Apache Logging Services Project; and be it further
  
     RESOLVED, that the initial Logging Services PMC be and hereby is
     tasked with the migration and rationalization of the log4j Apache
     Jakarta subproject; and be it further
  
     RESOLVED, that the initial Logging Services PMC be and hereby is
     tasked with the migration and integration of the sister projects,
     namely but not exclusively, Log4Perl, Log4Net, Log4Cxx (c++),
     Log4CPlus, Log4PHP and Log4plsql, subject to the will and approval
     of the respective project owners and communities.
  </pre>
  
  
  
    </body>
  </document>
  
  
  
  
  1.3       +1 -1      logging-site/src/xdocs/stylesheets/project.xml
  
  Index: project.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/stylesheets/project.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- project.xml	22 Dec 2003 10:46:18 -0000	1.2
  +++ project.xml	22 Dec 2003 17:41:24 -0000	1.3
  @@ -22,7 +22,7 @@
   
   
      <menu name="Information">
  -     <item name="Mission statement"   href="/site/mission.html"/>
  +     <item name="Mission statement"   href="/site/mission-statement.html"/>
        <item name="Bylaws"   href="/site/bylaws.html"/>
        <item name="License"   href=""/>
        <item name="Who we are"   href="/site/who-we-are.html"/>
  
  
  

Mime
View raw message