yoavs | 3 Jun 03:00 2005
Picon

cvs commit: logging-site/src/xdocs index.xml

yoavs       2005/06/02 18:00:12

  Modified:    docs     index.html
               src/xdocs index.xml
  Log:
  Help out the ApacheCon folks ;)

  Revision  Changes    Path
  1.30      +6 -3      logging-site/docs/index.html

  Index: index.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/index.html,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- index.html	19 Jan 2005 22:41:37 -0000	1.29
  +++ index.html	3 Jun 2005 01:00:12 -0000	1.30
   <at>  <at>  -48,7 +48,10  <at>  <at> 
   	   <div class="centercol">
                <hr noshade="" size="1"/>
   		       
  -                                         <h1>Welcome to Logging Services Project  <at>  Apache</strong></h1>
  +                                       <a href="http://apachecon.com">
  +<img src="http://apache.org/images/ac2005eu_135x50.gif" />
  +</a>
  +                                                        <h1>Welcome to Logging Services Project  <at>  Apache</strong></h1>
                                       <p>The log4j developers are pleased to announce that the Board of
     Directors of the Apache Software Foundation unanimously passed a
     resolution for the creation of the Apache Logging Services
(Continue reading)

Jun Lu | 14 Jun 12:30 2005
Picon

Log4J manual Chinese translation is online

Hi,

I have added 2 links of Chinese (Simplified and Traditional)
translation of the short manual into "Translations to other languages" section of
/jakarta-log4j/src/xdocs/documentation.xml.

http://www.jaxwiki.org/zh/project/logging.apache.org/log4j/docs/manual.html
http://www.jaxwiki.org/hk/project/logging.apache.org/log4j/docs/manual.html

Please commit the changes into CVS.

Thanks.

Best Regards.

Jun Lu
Attachment (documentation.xml): text/xml, 7061 bytes
Mark Womack | 17 Jun 07:17 2005
Picon

Re: Log4J manual Chinese translation is online

Jun Lu,

Thanks.  I have added the links to the cvs.  It will be part of the next 
update to the web site.

-Mark

----- Original Message ----- 
From: "Jun Lu" <junlu <at> yahoo.com>
To: <general <at> logging.apache.org>
Sent: Tuesday, June 14, 2005 3:30 AM
Subject: Log4J manual Chinese translation is online

> Hi,
>
> I have added 2 links of Chinese (Simplified and Traditional)
> translation of the short manual into "Translations to other languages" 
> section of
> /jakarta-log4j/src/xdocs/documentation.xml.
>
> http://www.jaxwiki.org/zh/project/logging.apache.org/log4j/docs/manual.html
> http://www.jaxwiki.org/hk/project/logging.apache.org/log4j/docs/manual.html
>
> Please commit the changes into CVS.
>
> Thanks.
>
> Best Regards.
>
> Jun Lu
>
>
>

--------------------------------------------------------------------------------

> <?xml version="1.0"?>
> <document>
>
>  <properties>
>    <author email="">Ceki Gulcu</author>
>    <author email="yoavs <at> apache.org">Yoav Shapira</author>
>    <title>Documentation</title>
>  </properties>
>
>  <body>
>
>    <section name="Official log4j documentation">
>
>      <p>With the exception of the complete manual, the following
>      documentation is included with the standard log4j distribution
>      and also browsable online:
>      </p>
>
>      <ul>
>        <p>
>          <a
>           href="http://www.qos.ch/shop/products/eclm/"><img
>           align="right" src="images/coverSmall.png"></img></a> <li><a
>           href="manual.html"><b>short manual</b></a>,
>           </li>
>        </p>
>
>        <p>
>          <li><a href="http://www.qos.ch/shop/products/eclm/"><b>complete 
> manual</b></a> (commercial),
>          </li>
>        </p>
>
>        <p>
>          <li>
>            <a href="api/index.html"><b>javadoc documentation</b></a>,
>          </li>
>        </p>
>
>        <p>
>          <li>
>            <a href="HISTORY"><b>project history</b></a>,
>          </li>
>        </p>
>
>
> <p>
>   <li>
>     <a href="faq.html"><b>FAQ</b></a>,
>   </li>
> </p>
>
> <p>
>   <li>
>     <a href="TROUBLESHOOT.html"><b>troubleshooting guide</b></a>.
>   </li>
> </p>
>
>      </ul>
>    </section>
>
>    <section name="Translations to other languages">
>       <ul>
>         <li><a
>         href="http://www.vimeworks.com/~mauricio/manualLog4J.html">Spanish
>         translation</a> of the short manual Mauricio Santacruz (<a 
> href="http://www.vimeworks.com/~mauricio/manualLog4J.pdf">PDF</a>, <a 
> href="http://www.vimeworks.com/~mauricio/manualLog4J.html">HTML</a>)</li>
>         <li><a 
>
href="http://www.javacore.de/jumpToDownload.php?id=8&amp;url=tutorials/schnelle/log4jmanual.pdf">German 
> translation</a> of the short manual, courtesy of Dirk Schnelle. (PDF only 
> at this time)</li>
>         <li><a 
>
href="http://www.jaxwiki.org/zh/project/logging.apache.org/log4j/docs/manual.html">Simplified 
> Chinese</a> and <a 
>
href="http://www.jaxwiki.org/hk/project/logging.apache.org/log4j/docs/manual.html">traditional 
> Chinese</a> translation of the short manual (HTML only) by 
> Jaxwiki.org.</li>
>      </ul>
>    </section>
>
>
>    <section name="Articles on log4j">
>      <ul>
>
>        <p>
>          <li><a href="http://www.vipan.com/htdocs/log4jhelp.html">Don't 
> Use System.out.println!
>          Use Log4j</a> by Vipan Singla
>          </li>
>        </p>
>
>        <p><li><a 
> href="http://www.onjava.com/pub/a/onjava/2002/08/07/log4j.html?page=1">
>        Build Flexible Logs With log4j</a> by Vikram Goyal
>        </li></p>
>
>        <p><li><a
> 
> href="http://supportweb.cs.bham.ac.uk/documentation/tutorials/docsystem/build/tutorials/log4j/log4j.html">log4j</a>
>        by Ashley J.S Mills, University Of Birmingham</li></p>
>
>        <p><li><a 
> href="http://www.builder.com.com/article.jhtml?id=u00820020124kev01.htm">
>        Add logging to your Java Applications</a> by Kevin Brown
>        </li></p>
>
>        <p><li><a 
> href="http://www.builder.com.com/article.jhtml?id=u00220020724kev01.htm">
>        How does the Java logging API stack up against log4j?</a> by Kevin 
> Brown
>        </li></p>
>
>        <p>
>          <li>
>            <a 
> href="http://www.opensymphony.com/guidelines/logging.jsp">OpenSymphony 
> Logging Primer</a>
>          </li>
>        </p>
>
>        <p><li>
>   <a href="http://www.jguru.com/faq/Log4j">log4j FAQ</a> at jGuru
> </li></p>
>
> <p><li>
>   <a href="http://www.qos.ch/logging/thinkAgain.html">Think Again</a> by 
> Ceki G&#252;lc&#252;
>
> </li></p>
>
> <p><li> <a href="http://www.qos.ch/logging/sc.html">Supporting the
>   log4j <code>RepositorySelector</code></a> by Ceki
>   G&#252;lc&#252;
> </li></p>
>
>         <p><li> <a href="http://rei1.m-plify.net/log4j/">Log4j class
>         diagrams</a>, courtesy of David Tonhofer
>            </li>
>         </p>
>
>         <p><li> <a
> 
> href="http://www.onjava.com/pub/a/onjava/2003/04/02/log4j_ejb.html">Understanding
>         Classloaders: log4j in a J2EE Environment</a> by Vikram Goyal
>            </li>
>         </p>
>
>
>         <p><li> <a
> 
> href="http://www.linux-magazin.de/Artikel/ausgabe/2002/04/coffee/coffee.html">Logging
>         f&#252;r Java-Programme, Zu den Akten</a> by Bernhard Bablok
>         in Linux Magazine, 04/2002.
>            </li>
>         </p>
>
>         <p><li> <a
> 
> href="http://www-106.ibm.com/developerworks/java/library/j-instlog/">Instant 
> logging: Harness the power of log4j with Jabber</a> by Ruth Zamorano and 
> Rafael Luque, in developerWorks 2003
>         </li>
>         </p>
>
>         <p>
>           <li> <a
> 
> href="http://developers.sun.com/prodtech/appserver/reference/techart/log4j.html">Using 
> Log4j in the Sun Java System Application Server</a> by Matthew Litkey, Jay 
> Galvin, and Marina Sum, from Sun.
>           </li>
>         </p>
>
>         <p>
>           <li> <a
> 
> href="http://www.onjava.com/pub/a/onjava/2004/09/29/smtp-logging.html">Reporting
>           Application Errors by Email</a> by Sean C. Sullivan,
>           2004-09-24, published by O'Reilly.
>           </li>
>         </p>
>
>      </ul>
>    </section>
>
>    <section name="Log4j presentations">
>       <ul>
>
>
>         <p><li> <a href="http://www.jug-l.org/log4j.html">Advanced
>         Log4j</a> Louisville JUG presentation by Jonathan Cowherd 
> </li></p>
>
>         <p><li><a 
> href="http://www.johnmunsch.com/projects/Presentations/">Log4J
>         In 30 Minutes Or Less</a> by John Munsch</li></p>
>
>         <p><li><a href="https://www.qos.ch/ac2001/F11-10.html">Log4j, a 
> logging package for the Java language</a> by Ceki G&#252;lc&#252;</li></p>
>
>         <p><li><a
> 
> href="http://www.ejug.org/OpenSource%20Log4j2_files/frame.htm">Log4j 
> presentation by the</a>
>         Edmonton Java Users Group</li></p>
>
>         <p><li><a 
> href="http://www.ociweb.com/javasig/knowledgebase/January2001/Log4J.ppt">Log4j</a> 
> by Brent Twenter
>         </li></p>
>      </ul>
>    </section>
>
>
>    <section name="Training &amp; Professional support">
>      <p>The following organisations offer log4j-related consultancy
>      and training services. Their inclusion on this page does
>      not imply endorsement by the Apache Software Foundation.
>      </p>
>
>      <ul>
>        <li><a
>        href="https://www.qos.ch/shop/products/profSupport/">QOS.ch,
>        Switzerland</a> proposes professional support contracts.
>        </li>
>      </ul>
>
>      <ul>
>        <li><a
>        href="http://www.thegoodsoftwarecompany.com/log4jTraining.do">The
>        Good Software Company</a> proposes log4j training courses.
>        </li>
>      </ul>
>
>      <p><b>If you would like your log4j-related article or service
>      to be listed here, then please send a note to the <a
> 
> href="mailto:log4j-user <at> logging.apache.org">log4j-user <at> logging.apache.org</a>
>      list.</b>
>      </p>
>    </section>
>
>  </body>
> </document>
>
> 

mwomack | 17 Jun 07:45 2005
Picon

cvs commit: logging-site/src/xdocs/stylesheets project.xml

mwomack     2005/06/16 22:45:20

  Modified:    src/xdocs index.xml
               src/xdocs/site binindex.xml bugreport.xml bylaws.xml
                        cvs-repositories.xml logging-site.xml
                        mailing-lists.xml mission-statement.xml news.xml
                        who-we-are.xml
               src/xdocs/stylesheets project.xml
  Log:
  Updated to iso-8859-1 encoding.
  Updated PMC Chair info in who-we-are.xml.
  
  Revision  Changes    Path
  1.15      +1 -1      logging-site/src/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/index.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- index.xml	3 Jun 2005 01:00:12 -0000	1.14
  +++ index.xml	17 Jun 2005 05:45:20 -0000	1.15
   <at>  <at>  -1,4 +1,4  <at>  <at> 
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="iso-8859-1"?>
   <document>
   
     <properties>
  
  
  
  1.24      +1 -1      logging-site/src/xdocs/site/binindex.xml
  
  Index: binindex.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/binindex.xml,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- binindex.xml	10 May 2005 15:00:56 -0000	1.23
  +++ binindex.xml	17 Jun 2005 05:45:20 -0000	1.24
   <at>  <at>  -1,4 +1,4  <at>  <at> 
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="iso-8859-1"?>
   <document>
   
     <properties>
  
  
  
  1.10      +1 -1      logging-site/src/xdocs/site/bugreport.xml
  
  Index: bugreport.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/bugreport.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- bugreport.xml	23 Nov 2004 11:01:23 -0000	1.9
  +++ bugreport.xml	17 Jun 2005 05:45:20 -0000	1.10
   <at>  <at>  -1,4 +1,4  <at>  <at> 
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="iso-8859-1"?>
   <document>
   
     <properties>
  
  
  
  1.8       +832 -416  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.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- bylaws.xml	13 Aug 2004 09:31:09 -0000	1.7
  +++ bylaws.xml	17 Jun 2005 05:45:20 -0000	1.8
   <at>  <at>  -1,416 +1,832  <at>  <at> 
  -<?xml version="1.0"?>

  -<document>

  -

  -  <properties>

  -    <author email="ceki at apache dot org">Ceki Gulcu</author>

  -    <title>Bylaws of the Logging Services Project</title>

  -  </properties>

  -

  -  <meta name="keywords" content="bylaws, logging services"/>

  -

  -

  -<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>Roles and Responsibilities<a name="Roles and Responsibilities">&#160;</a></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">Users<a name="Users">&#160;</a></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">Developers<a name="Developers">&#160;</a></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">Committers<a name="Committers">&#160;</a></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">Project Management Committee

  -     <a name="Project Management Committee">&#160;</a></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">Decision Making

  -      <a name="Decision Making">&#160;</a> 

  -     </h3>

  -                        

  -     <p>Within the Logging Services project, different types of

  -     decisions require different forms of approval. For example, the

  -     previous section 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">Voting<a name="Voting">&#160;</a></h3>

  -

  -     <p>Decisions regarding the project are made by votes on the

  -     primary project mailing list (general <at> 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 class="ls" 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>Approvals<a name="Approvals">&#160;</a></h3>

  -

  -    <p>These are the types of approvals that can be sought. Different

  -       actions require different types of approvals</p>

  -

  -    <table  class="ls" valign="top">

  -    <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>Vetoes<a name="Vetoes">&#160;</a></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>Actions<a name="Actions">&#160;</a></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 class="ls" 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 valign="top">

  -      <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>Voting Timeframes<a name="Voting Timeframes">&#160;</a></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>

  -

  +<?xml version="1.0" encoding="iso-8859-1"?>
  +
  +<document>
  +
  +
  +
  +  <properties>
  +
  +    <author email="ceki at apache dot org">Ceki Gulcu</author>
  +
  +    <title>Bylaws of the Logging Services Project</title>
  +
  +  </properties>
  +
  +
  +
  +  <meta name="keywords" content="bylaws, logging services"/>
  +
  +
  +
  +
  +
  +<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>Roles and Responsibilities<a name="Roles and Responsibilities">&#160;</a></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">Users<a name="Users">&#160;</a></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">Developers<a name="Developers">&#160;</a></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">Committers<a name="Committers">&#160;</a></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">Project Management Committee
  +
  +     <a name="Project Management Committee">&#160;</a></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">Decision Making
  +
  +      <a name="Decision Making">&#160;</a> 
  +
  +     </h3>
  +
  +                        
  +
  +     <p>Within the Logging Services project, different types of
  +
  +     decisions require different forms of approval. For example, the
  +
  +     previous section 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">Voting<a name="Voting">&#160;</a></h3>
  +
  +
  +
  +     <p>Decisions regarding the project are made by votes on the
  +
  +     primary project mailing list (general <at> 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 class="ls" 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>Approvals<a name="Approvals">&#160;</a></h3>
  +
  +
  +
  +    <p>These are the types of approvals that can be sought. Different
  +
  +       actions require different types of approvals</p>
  +
  +
  +
  +    <table  class="ls" valign="top">
  +
  +    <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>Vetoes<a name="Vetoes">&#160;</a></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>Actions<a name="Actions">&#160;</a></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 class="ls" 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 valign="top">
  +
  +      <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>Voting Timeframes<a name="Voting Timeframes">&#160;</a></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.9       +1 -1      logging-site/src/xdocs/site/cvs-repositories.xml
  
  Index: cvs-repositories.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/cvs-repositories.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- cvs-repositories.xml	30 Apr 2005 15:19:01 -0000	1.8
  +++ cvs-repositories.xml	17 Jun 2005 05:45:20 -0000	1.9
   <at>  <at>  -1,4 +1,4  <at>  <at> 
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="iso-8859-1"?>
   <document>
   
     <properties>
  
  
  
  1.11      +1 -1      logging-site/src/xdocs/site/logging-site.xml
  
  Index: logging-site.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/logging-site.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- logging-site.xml	11 Jan 2005 21:38:30 -0000	1.10
  +++ logging-site.xml	17 Jun 2005 05:45:20 -0000	1.11
   <at>  <at>  -1,4 +1,4  <at>  <at> 
  -<?xml version="1.0"?>
  +<?xml version="1.0" encoding="iso-8859-1"?>
   <document>
   
     <properties>
  
  
  
  1.8       +482 -241  logging-site/src/xdocs/site/mailing-lists.xml
  
  Index: mailing-lists.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/mailing-lists.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- mailing-lists.xml	10 Mar 2005 00:17:25 -0000	1.7
  +++ mailing-lists.xml	17 Jun 2005 05:45:20 -0000	1.8
   <at>  <at>  -1,242 +1,483  <at>  <at> 
  -<?xml version="1.0"?>

  -<document>

  -

  -  <properties>

  -    <author email="ceki at apache dot org">Ceki Gulcu</author>

  -    <title>Mailing lists for the Logging Services Project</title>

  -  </properties>

  -

  -  <meta name="keywords" content="mailing list, mailing list logging services"/>

  -

  -

  -<body>

  -

  -  <h1>Mailing Lists</h1>

  -

  -  <p>Please read the <a

  -  href="http://jakarta.apache.org/site/mail.html">guidelines of the

  -  Jakarta Project</a> before subscribing and posting to any of the

  -  lists below. They apply to Logging Services' lists as well.

  -  </p>

  -

  -  <p><em>All lists are subscriber only lists, this means you have to

  -  subscribe before you can post to them.</em>

  -  </p>

  -

  -  <p>Please do your best to ensure that you are not sending HTML or

  -  "Stylelized" email to the list. If you are using Outlook or Outlook

  -  Express or Eudora, chances are that you are sending HTML email by

  -  default. There is usually a setting that will allow you to send

  -  "Plain Text" email.

  -  </p>

  -

  -

  -  <h2>The Logging Services <b>General</b> list</h2>

  -

  -   <p><b>Medium Traffic</b>

  -   <a href="mailto:general-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:general-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/><b>Archives:</b>

  -        <a href="http://marc.theaimsgroup.com/?l=apache-logging-general&amp;r=1&amp;w=2">MARC</a>, 

  -        <a href="http://dir.gmane.org/gmane.comp.apache.logging">GMANE</a>,

  -        apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-general/">mod_mbox</a>, 

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=199">eyebrowse</a>

  -   </p>

  -

  -   <p>This is the project general mailing list. This is where ideas,

  -   suggestions, and comments are exchanged that deal with the

  -   <em>overall</em> Logging Services project. READ: This is

  -   <em>not</em> a place to ask technical questions related to <a

  -   href="http://logging.apache.org/log4j/">log4j</a>, or any other

  -   single Logging Services project. Matters that affect the project as

  -   a whole are decided here. If you are interested in adding a new

  -   sub-project to Logging Services, please see <a

  -   href="http://jakarta.apache.org/site/newproject.html">this

  -   page</a>.

  -  </p>

  -

  -  <hr/>

  -  <h2>Log4cxx lists</h2>

  -

  -   <h3>log4cxx-user list</h3>

  -

  -   <p>

  -   <b>Medium Traffic</b>

  -   <a href="mailto:log4cxx-user-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:log4cxx-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/>

  -   <b>Archives:</b>

  -                    <a href="http://marc.theaimsgroup.com/?l=log4cxx-user&amp;r=1&amp;w=2">MARC</a>, 

  -                    <a href="http://dir.gmane.org/gmane.comp.apache.logging.log4cxx.user">GMANE</a>,

  -                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4cxx-user/">mod_mbox</a>,

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=219">eyebrowse</a>

  -   </p>

  -

  -   <p>This is the list for users of log4jcxx logging framework. It is

  -   also a good forum for asking questions about how log4cxx works, and

  -   how it can be used. Log4cxx developers should also join this list

  -   to offer support to their users.

  -   </p>

  -

  -

  -   <h3>log4cxx-dev list</h3>

  -

  -   <p>

  -   <b>Medium Traffic</b>

  -   <a href="mailto:log4cxx-dev-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:log4cxx-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/><b>Archives:</b>

  -                    <a href="http://marc.theaimsgroup.com/?l=log4cxx-dev&amp;r=1&amp;w=2">MARC</a>, 

  -                    <a href="http://dir.gmane.org/gmane.comp.apache.logging.log4cxx.devel">GMANE</a>,

  -                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4cxx-dev/">mod_mbox</a>, 

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=218">eyebrowse</a></p>

  -   

  -

  -   <p>This is the list where participating developers of the log4cxx

  -   framework meet and discuss issues, code changes/additions,

  -   etc. Subscribers to this list get notices of each and every code

  -   change, build results, testing notices, etc. Do not send mail to

  -   this list with usage questions or configuration problems -- that's

  -   what log4cxx-user is for.

  -   </p>

  -

  -

  -  <hr/>

  -  <h2>Log4j lists</h2>

  -

  -   <h3>log4j-user list</h3>

  -

  -   <p>

  -   <b>Medium Traffic</b>

  -   <a href="mailto:log4j-user-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:log4j-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/><b>Archives:</b>

  -                    <a href="http://marc.theaimsgroup.com/?l=log4j-user&amp;r=1&amp;w=2">MARC</a>, 

  -                    <a href="http://dir.gmane.org/gmane.comp.jakarta.log4j.user">GMANE</a>,

  -                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4j-user/">mod_mbox</a>, 

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=201">eyebrowse</a></p>

  -

  -

  -   <p>This is the list for users of log4jcxx logging framework. It is

  -   also a good forum for asking questions about how log4j works, and

  -   how it can be used. Log4j developers should also join this list

  -   to offer support to their users.

  -   </p>

  -

  -

  -   <h3>log4j-dev list</h3>

  -

  -   <p>

  -   <b>Medium Traffic</b>

  -   <a href="mailto:log4j-dev-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:log4j-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/><b>Archives:</b>

  -                    <a href="http://marc.theaimsgroup.com/?l=log4j-dev&amp;r=1&amp;w=2">MARC</a>, 

  -                    <a href="http://dir.gmane.org/gmane.comp.jakarta.log4j.devel">GMANE</a>,

  -                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4j-dev/">mod_mbox</a>, 

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=200">eyebrowse</a></p>

  -

  -   <p>This is the list where participating developers of the log4j

  -   framework meet and discuss issues, code changes/additions,

  -   etc. Subscribers to this list get notices of each and every code

  -   change, build results, testing notices, etc. Do not send mail to

  -   this list with usage questions or configuration problems -- that's

  -   what log4j-user is for.

  -   </p>

  -

  -

  -  <hr/>

  -  <h2>Log4net lists</h2>

  -

  -   <h3>log4net-user list</h3>

  -

  -   <p>

  -   <b>Medium Traffic</b>

  -   <a href="mailto:log4net-user-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:log4net-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/><b>Archives:</b>

  -                    <a href="http://marc.theaimsgroup.com/?l=log4net-user&amp;r=1&amp;w=2">MARC</a>, 

  -                    <a href="http://dir.gmane.org/gmane.comp.log.log4net.user">GMANE</a>,

  -                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4net-user/">mod_mbox</a>, 

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=215">eyebrowse</a></p>

  -

  -   <p>This is the list for users of log4jcxx logging framework. It is

  -   also a good forum for asking questions about how log4net works, and

  -   how it can be used. Log4net developers should also join this list

  -   to offer support to their users.

  -   </p>

  -

  -

  -   <h3>log4net-dev list</h3>

  -

  -   <p>

  -   <b>Medium Traffic</b>

  -   <a href="mailto:log4net-dev-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:log4net-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/><b>Archives:</b>

  -                    <a href="http://marc.theaimsgroup.com/?l=log4net-dev&amp;r=1&amp;w=2">MARC</a> 

  -                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4net-dev/">mod_mbox</a>, 

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=215">eyebrowse</a></p>

  -

  -   <p>This is the list where participating developers of the log4net

  -   framework meet and discuss issues, code changes/additions,

  -   etc. Subscribers to this list get notices of each and every code

  -   change, build results, testing notices, etc. Do not send mail to

  -   this list with usage questions or configuration problems -- that's

  -   what log4net-user is for.

  -   </p>

  -

  -  <hr/>

  -  <h2>Log4php lists</h2>

  -

  -   <h3>log4php-user list</h3>

  -

  -   <p>

  -   <b>Medium Traffic</b>

  -   <a href="mailto:log4php-user-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:log4php-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/><b>Archives:</b>

  -                    <a href="http://marc.theaimsgroup.com/?l=log4php-user&amp;r=1&amp;w=2">MARC</a>

  -                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4php-user/">mod_mbox</a>, 

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=217">eyebrowse</a></p>

  -

  -   <p>This is the list for users of log4php logging framework. It is

  -   also a good forum for asking questions about how log4php works, and

  -   how it can be used. Log4php developers should also join this list

  -   to offer support to their users.

  -   </p>

  -

  -

  -   <h3>log4php-dev list</h3>

  -

  -   <p>

  -   <b>Medium Traffic</b>

  -   <a href="mailto:log4php-dev-subscribe <at> logging.apache.org">Subscribe</a>

  -   <a href="mailto:log4php-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>

  -   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>

  -   <br/><b>Archives:</b>

  -                    <a href="http://marc.theaimsgroup.com/?l=log4php-dev&amp;r=1&amp;w=2">MARC</a> 

  -                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4php-dev/">mod_mbox</a>, 

  -                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=216">eyebrowse</a></p>

  -

  -   <p>This is the list where participating developers of the log4php

  -   framework meet and discuss issues, code changes/additions,

  -   etc. Subscribers to this list get notices of each and every code

  -   change, build results, testing notices, etc. Do not send mail to

  -   this list with usage questions or configuration problems -- that's

  -   what log4php-user is for.

  -   </p>

  -

  -

  -

  -

  -</body>

  +<?xml version="1.0" encoding="iso-8859-1"?>
  +
  +<document>
  +
  +
  +
  +  <properties>
  +
  +    <author email="ceki at apache dot org">Ceki Gulcu</author>
  +
  +    <title>Mailing lists for the Logging Services Project</title>
  +
  +  </properties>
  +
  +
  +
  +  <meta name="keywords" content="mailing list, mailing list logging services"/>
  +
  +
  +
  +
  +
  +<body>
  +
  +
  +
  +  <h1>Mailing Lists</h1>
  +
  +
  +
  +  <p>Please read the <a
  +
  +  href="http://jakarta.apache.org/site/mail.html">guidelines of the
  +
  +  Jakarta Project</a> before subscribing and posting to any of the
  +
  +  lists below. They apply to Logging Services' lists as well.
  +
  +  </p>
  +
  +
  +
  +  <p><em>All lists are subscriber only lists, this means you have to
  +
  +  subscribe before you can post to them.</em>
  +
  +  </p>
  +
  +
  +
  +  <p>Please do your best to ensure that you are not sending HTML or
  +
  +  "Stylelized" email to the list. If you are using Outlook or Outlook
  +
  +  Express or Eudora, chances are that you are sending HTML email by
  +
  +  default. There is usually a setting that will allow you to send
  +
  +  "Plain Text" email.
  +
  +  </p>
  +
  +
  +
  +
  +
  +  <h2>The Logging Services <b>General</b> list</h2>
  +
  +
  +
  +   <p><b>Medium Traffic</b>
  +
  +   <a href="mailto:general-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:general-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/><b>Archives:</b>
  +
  +        <a href="http://marc.theaimsgroup.com/?l=apache-logging-general&amp;r=1&amp;w=2">MARC</a>, 
  +
  +        <a href="http://dir.gmane.org/gmane.comp.apache.logging">GMANE</a>,
  +
  +        apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-general/">mod_mbox</a>, 
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=199">eyebrowse</a>
  +
  +   </p>
  +
  +
  +
  +   <p>This is the project general mailing list. This is where ideas,
  +
  +   suggestions, and comments are exchanged that deal with the
  +
  +   <em>overall</em> Logging Services project. READ: This is
  +
  +   <em>not</em> a place to ask technical questions related to <a
  +
  +   href="http://logging.apache.org/log4j/">log4j</a>, or any other
  +
  +   single Logging Services project. Matters that affect the project as
  +
  +   a whole are decided here. If you are interested in adding a new
  +
  +   sub-project to Logging Services, please see <a
  +
  +   href="http://jakarta.apache.org/site/newproject.html">this
  +
  +   page</a>.
  +
  +  </p>
  +
  +
  +
  +  <hr/>
  +
  +  <h2>Log4cxx lists</h2>
  +
  +
  +
  +   <h3>log4cxx-user list</h3>
  +
  +
  +
  +   <p>
  +
  +   <b>Medium Traffic</b>
  +
  +   <a href="mailto:log4cxx-user-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:log4cxx-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/>
  +
  +   <b>Archives:</b>
  +
  +                    <a href="http://marc.theaimsgroup.com/?l=log4cxx-user&amp;r=1&amp;w=2">MARC</a>, 
  +
  +                    <a href="http://dir.gmane.org/gmane.comp.apache.logging.log4cxx.user">GMANE</a>,
  +
  +                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4cxx-user/">mod_mbox</a>,
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=219">eyebrowse</a>
  +
  +   </p>
  +
  +
  +
  +   <p>This is the list for users of log4jcxx logging framework. It is
  +
  +   also a good forum for asking questions about how log4cxx works, and
  +
  +   how it can be used. Log4cxx developers should also join this list
  +
  +   to offer support to their users.
  +
  +   </p>
  +
  +
  +
  +
  +
  +   <h3>log4cxx-dev list</h3>
  +
  +
  +
  +   <p>
  +
  +   <b>Medium Traffic</b>
  +
  +   <a href="mailto:log4cxx-dev-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:log4cxx-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/><b>Archives:</b>
  +
  +                    <a href="http://marc.theaimsgroup.com/?l=log4cxx-dev&amp;r=1&amp;w=2">MARC</a>, 
  +
  +                    <a href="http://dir.gmane.org/gmane.comp.apache.logging.log4cxx.devel">GMANE</a>,
  +
  +                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4cxx-dev/">mod_mbox</a>, 
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=218">eyebrowse</a></p>
  +
  +   
  +
  +
  +
  +   <p>This is the list where participating developers of the log4cxx
  +
  +   framework meet and discuss issues, code changes/additions,
  +
  +   etc. Subscribers to this list get notices of each and every code
  +
  +   change, build results, testing notices, etc. Do not send mail to
  +
  +   this list with usage questions or configuration problems -- that's
  +
  +   what log4cxx-user is for.
  +
  +   </p>
  +
  +
  +
  +
  +
  +  <hr/>
  +
  +  <h2>Log4j lists</h2>
  +
  +
  +
  +   <h3>log4j-user list</h3>
  +
  +
  +
  +   <p>
  +
  +   <b>Medium Traffic</b>
  +
  +   <a href="mailto:log4j-user-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:log4j-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/><b>Archives:</b>
  +
  +                    <a href="http://marc.theaimsgroup.com/?l=log4j-user&amp;r=1&amp;w=2">MARC</a>, 
  +
  +                    <a href="http://dir.gmane.org/gmane.comp.jakarta.log4j.user">GMANE</a>,
  +
  +                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4j-user/">mod_mbox</a>, 
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=201">eyebrowse</a></p>
  +
  +
  +
  +
  +
  +   <p>This is the list for users of log4jcxx logging framework. It is
  +
  +   also a good forum for asking questions about how log4j works, and
  +
  +   how it can be used. Log4j developers should also join this list
  +
  +   to offer support to their users.
  +
  +   </p>
  +
  +
  +
  +
  +
  +   <h3>log4j-dev list</h3>
  +
  +
  +
  +   <p>
  +
  +   <b>Medium Traffic</b>
  +
  +   <a href="mailto:log4j-dev-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:log4j-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/><b>Archives:</b>
  +
  +                    <a href="http://marc.theaimsgroup.com/?l=log4j-dev&amp;r=1&amp;w=2">MARC</a>, 
  +
  +                    <a href="http://dir.gmane.org/gmane.comp.jakarta.log4j.devel">GMANE</a>,
  +
  +                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4j-dev/">mod_mbox</a>, 
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=200">eyebrowse</a></p>
  +
  +
  +
  +   <p>This is the list where participating developers of the log4j
  +
  +   framework meet and discuss issues, code changes/additions,
  +
  +   etc. Subscribers to this list get notices of each and every code
  +
  +   change, build results, testing notices, etc. Do not send mail to
  +
  +   this list with usage questions or configuration problems -- that's
  +
  +   what log4j-user is for.
  +
  +   </p>
  +
  +
  +
  +
  +
  +  <hr/>
  +
  +  <h2>Log4net lists</h2>
  +
  +
  +
  +   <h3>log4net-user list</h3>
  +
  +
  +
  +   <p>
  +
  +   <b>Medium Traffic</b>
  +
  +   <a href="mailto:log4net-user-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:log4net-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/><b>Archives:</b>
  +
  +                    <a href="http://marc.theaimsgroup.com/?l=log4net-user&amp;r=1&amp;w=2">MARC</a>, 
  +
  +                    <a href="http://dir.gmane.org/gmane.comp.log.log4net.user">GMANE</a>,
  +
  +                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4net-user/">mod_mbox</a>, 
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=215">eyebrowse</a></p>
  +
  +
  +
  +   <p>This is the list for users of log4jcxx logging framework. It is
  +
  +   also a good forum for asking questions about how log4net works, and
  +
  +   how it can be used. Log4net developers should also join this list
  +
  +   to offer support to their users.
  +
  +   </p>
  +
  +
  +
  +
  +
  +   <h3>log4net-dev list</h3>
  +
  +
  +
  +   <p>
  +
  +   <b>Medium Traffic</b>
  +
  +   <a href="mailto:log4net-dev-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:log4net-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/><b>Archives:</b>
  +
  +                    <a href="http://marc.theaimsgroup.com/?l=log4net-dev&amp;r=1&amp;w=2">MARC</a> 
  +
  +                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4net-dev/">mod_mbox</a>, 
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=215">eyebrowse</a></p>
  +
  +
  +
  +   <p>This is the list where participating developers of the log4net
  +
  +   framework meet and discuss issues, code changes/additions,
  +
  +   etc. Subscribers to this list get notices of each and every code
  +
  +   change, build results, testing notices, etc. Do not send mail to
  +
  +   this list with usage questions or configuration problems -- that's
  +
  +   what log4net-user is for.
  +
  +   </p>
  +
  +
  +
  +  <hr/>
  +
  +  <h2>Log4php lists</h2>
  +
  +
  +
  +   <h3>log4php-user list</h3>
  +
  +
  +
  +   <p>
  +
  +   <b>Medium Traffic</b>
  +
  +   <a href="mailto:log4php-user-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:log4php-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/><b>Archives:</b>
  +
  +                    <a href="http://marc.theaimsgroup.com/?l=log4php-user&amp;r=1&amp;w=2">MARC</a>
  +
  +                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4php-user/">mod_mbox</a>, 
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=217">eyebrowse</a></p>
  +
  +
  +
  +   <p>This is the list for users of log4php logging framework. It is
  +
  +   also a good forum for asking questions about how log4php works, and
  +
  +   how it can be used. Log4php developers should also join this list
  +
  +   to offer support to their users.
  +
  +   </p>
  +
  +
  +
  +
  +
  +   <h3>log4php-dev list</h3>
  +
  +
  +
  +   <p>
  +
  +   <b>Medium Traffic</b>
  +
  +   <a href="mailto:log4php-dev-subscribe <at> logging.apache.org">Subscribe</a>
  +
  +   <a href="mailto:log4php-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
  +   <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
  +   <br/><b>Archives:</b>
  +
  +                    <a href="http://marc.theaimsgroup.com/?l=log4php-dev&amp;r=1&amp;w=2">MARC</a> 
  +
  +                    and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4php-dev/">mod_mbox</a>, 
  +
  +                    <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=216">eyebrowse</a></p>
  +
  +
  +
  +   <p>This is the list where participating developers of the log4php
  +
  +   framework meet and discuss issues, code changes/additions,
  +
  +   etc. Subscribers to this list get notices of each and every code
  +
  +   change, build results, testing notices, etc. Do not send mail to
  +
  +   this list with usage questions or configuration problems -- that's
  +
  +   what log4php-user is for.
  +
  +   </p>
  +
  +
  +
  +
  +
  +
  +
  +
  +
  +</body>
  +
   </document>
  \ No newline at end of file
  
  
  
  1.2       +186 -93   logging-site/src/xdocs/site/mission-statement.xml
  
  Index: mission-statement.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/mission-statement.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- mission-statement.xml	22 Dec 2003 17:41:24 -0000	1.1
  +++ mission-statement.xml	17 Jun 2005 05:45:20 -0000	1.2
   <at>  <at>  -1,93 +1,186  <at>  <at> 
  -<?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>

  -

  +<?xml version="1.0" encoding="iso-8859-1"?>
  +
  +<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.9       +108 -54   logging-site/src/xdocs/site/news.xml
  
  Index: news.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/news.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- news.xml	1 May 2005 05:21:32 -0000	1.8
  +++ news.xml	17 Jun 2005 05:45:20 -0000	1.9
   <at>  <at>  -1,55 +1,109  <at>  <at> 
  -<?xml version="1.0"?>

  -<document>

  -

  -  <properties>

  -    <author email="ceki at qos dot ch">Ceki Gulcu</author>

  -    <author email="yoavs at apache dot org">Yoav Shapira</author>

  -    <title>News and Status</title>

  -  </properties>

  -

  -<body>

  -

  -<section name="News &amp; Status">

  -

  -<h3>11 January 2005 - log4cxx graduates from the incubator</h3>

  -

  - <p>The Incubator PMC has voted to graduate log4cxx.  log4cxx is

  - now a subproject of the Apache Logging Services Project.

  - </p>

  -

  -<hr noshade="noshade" size="1"/>

  -

  -<h3>22nd of January 2004 - Logging Services PMC has voted for the

  -adoption of log4cxx, log4net and log4php</h3>

  -

  - <p>The Logging Services PMC has voted for the incubation of the

  - log4cxx, log4net and log4php projects. These votes pave the vote for

  - their migration into Apache Logging Services.

  - </p>

  -

  - <p>We heartily welcome the new projects.</p>

  -

  -<hr noshade="noshade" size="1"/>

  -

  -<h3>17th December 2003 - Creation of the Logging Services Project</h3> 

  -

  - <p>The Board of Directors of the Apache Software foundation voted

  - unanimously for the creation of the Apache Logging Services project.

  - The mailing list thread with the discussion preceding the creation

  - of this project is available

  - <a href='http://marc.theaimsgroup.com/?t=107115526200001&amp;r=1&amp;w=2'>here.</a>

  - </p>

  -

  -<hr noshade="noshade" size="1"/>

  -

  -<h3>

  -Got News?

  -</h3>

  -

  -<p>If you would like to submit an item for posting to this page, send

  -an email with the subject <b>[NEWS]</b> to the <code>general at logging dot

  -apache dot org</code> mailing list..

  -</p>

  -</section>

  -</body>

  +<?xml version="1.0" encoding="iso-8859-1"?>
  +
  +<document>
  +
  +
  +
  +  <properties>
  +
  +    <author email="ceki at qos dot ch">Ceki Gulcu</author>
  +
  +    <author email="yoavs at apache dot org">Yoav Shapira</author>
  +
  +    <title>News and Status</title>
  +
  +  </properties>
  +
  +
  +
  +<body>
  +
  +
  +
  +<section name="News &amp; Status">
  +
  +
  +
  +<h3>11 January 2005 - log4cxx graduates from the incubator</h3>
  +
  +
  +
  + <p>The Incubator PMC has voted to graduate log4cxx.  log4cxx is
  +
  + now a subproject of the Apache Logging Services Project.
  +
  + </p>
  +
  +
  +
  +<hr noshade="noshade" size="1"/>
  +
  +
  +
  +<h3>22nd of January 2004 - Logging Services PMC has voted for the
  +
  +adoption of log4cxx, log4net and log4php</h3>
  +
  +
  +
  + <p>The Logging Services PMC has voted for the incubation of the
  +
  + log4cxx, log4net and log4php projects. These votes pave the vote for
  +
  + their migration into Apache Logging Services.
  +
  + </p>
  +
  +
  +
  + <p>We heartily welcome the new projects.</p>
  +
  +
  +
  +<hr noshade="noshade" size="1"/>
  +
  +
  +
  +<h3>17th December 2003 - Creation of the Logging Services Project</h3> 
  +
  +
  +
  + <p>The Board of Directors of the Apache Software foundation voted
  +
  + unanimously for the creation of the Apache Logging Services project.
  +
  + The mailing list thread with the discussion preceding the creation
  +
  + of this project is available
  +
  + <a href='http://marc.theaimsgroup.com/?t=107115526200001&amp;r=1&amp;w=2'>here.</a>
  +
  + </p>
  +
  +
  +
  +<hr noshade="noshade" size="1"/>
  +
  +
  +
  +<h3>
  +
  +Got News?
  +
  +</h3>
  +
  +
  +
  +<p>If you would like to submit an item for posting to this page, send
  +
  +an email with the subject <b>[NEWS]</b> to the <code>general at logging dot
  +
  +apache dot org</code> mailing list..
  +
  +</p>
  +
  +</section>
  +
  +</body>
  +
   </document>
  \ No newline at end of file
  
  
  
  1.10      +417 -212  logging-site/src/xdocs/site/who-we-are.xml
  
  Index: who-we-are.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/who-we-are.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- who-we-are.xml	8 Dec 2004 18:04:38 -0000	1.9
  +++ who-we-are.xml	17 Jun 2005 05:45:20 -0000	1.10
   <at>  <at>  -1,213 +1,418  <at>  <at> 
  -<?xml version="1.0"?>

  -<document>

  -

  -  <properties>

  -    <author email="ceki at apache dot org">Ceki Gulcu</author>

  -    <title>Who we are</title>

  -  </properties>

  -

  -  <meta name="keywords" content="mission, mission statement logging services"/>

  -

  -

  -<body>

  -

  -  <h1>List of developers</h1>

  -       

  -

  -  <p>The software proposed by Logging Services project is the result

  -  of contributions from several dozen developers and hundreds of users

  -  across the globe. Some of the more prominent contributors are listed

  -  below in alphabetical order.

  -  </p>

  -

  -  <!-- ======================================== -->

  -  <!-- LISTED IN ALPHABETICAL ORDER (last name) -->

  -  <!-- ======================================== -->

  -

  -  <h1>PMC members</h1>

  -  <ul>

  -  

  -

  -  <li><b>Curt Arnold</b> 

  -     <p>Curt is the current lead for the log4cxx project. He is also a

  -     regular contributor to the log4j project.

  -     </p>

  -  </li>

  -

  -  <li><b>Nicko Cadell</b> 

  -     <p>Nicko is the current lead for the log4net project.</p>

  -  </li>

  -

  -

  -

  -  <li><b>Scott Deboy</b> 

  -     <p>Scott began contributing to the log4j project in early 2003, 

  -        focusing his efforts on developing a new logging analysis tool that 

  -        would become the next version of Chainsaw.  Along the way, he 

  -        contributed code which gave Chainsaw (and log4j) the ability to process 

  -	    events generated by other logging frameworks.

  -     </p>

  -  </li>

  - 

  -  <li><b>Ceki G&#252;lc&#252;</b> 

  -

  -    <table>

  -    <tr><td> <p>Ceki serves as the chairman of the Logging Services

  -    project. He is the founder the log4j project which continues to

  -    take much of his time. He very much enjoys writing software,

  -    altough he is discovering that it is far more difficult than what

  -    it might seem initially. Ceki is also the author of <a

  -    href="https://www.qos.ch/shop/products/log4j/log4j-Manual.jsp">The

  -    complete log4j manual</a>.  </p></td>

  -    

  -   <td><img src="../images/ceki-72x101.gif"></img></td>

  -    </tr>

  -    </table>

  -  </li>

  -

  -  <li><b>Jacob Kjome</b> 

  -

  -     <p>Jacob Kjome has been developing software since 1997 and has

  -      been playing with Java for about 4 years.  Jake joined the log4j

  -      team after being very active on the user list and contributing

  -      servlet and repository selector related code to the

  -      logj-sandbox.  He is also a committer on the (non-Apache

  -      related) XMLC, BarracudaMVC, and Prevayler projects.  Of late

  -      his free time has been squeezed with a new job and his vigorous

  -      2 year old son, Nicholas, but he still tries to pitch in when he

  -      can. :-)

  -     </p>

  -  </li>

  -

  -  <li><b>Yoav Shapira</b> 

  -    <table>

  -      <tr><td>

  -    

  -      <p>Yoav Shapira contributes numerous Apache and other open-source

  -      projects: you can read more about him at 

  -      <a href="http://www.yoavshapira.com">YoavShapira.com</a>.

  -      </p>

  -      </td>

  -    

  -      <td><img align="right" src="../images/yshapira.bmp"></img></td>

  -      </tr>

  -     </table>

  -   </li>

  -

  -   <li><b>Paul Smith</b> 

  -     <table>

  -       <tr><td>

  -       

  -       <p>Paul Smith has been developing software since 1990, and

  -       playing computer games a few years longer than that.  He has

  -       been thoroughly enjoying Java since 1998 after he gave up on

  -       Visual Basic in disgust.  Paul joined the log4j team after

  -       finding how darn useful it and the companion Chainsaw

  -       application was in '03, and has been helping out where he can,

  -       working on Chainsaw v2, and generally making a good nuisance of

  -       himself.  </p>

  -       </td> 

  -       <td><img align="right" src="../images/psmith.jpg"></img></td>

  -       </tr>

  -     </table>

  -  </li>

  -

  -  <li><b>Mark Womack</b> 

  -

  -         <table>

  -          <tr><td>  <p>Mark Womack has been developing software for over 12

  -	  years. He has been developing in Java for the past 4 years,

  -	  focusing on web application development. He has been an

  -	  active committer for the Apache Jakarta log4j project since

  -	  April 2002, contributing features for the upcoming v1.3

  -	  release. </p></td> 

  -          <td><img src="../images/mark-72x99.gif"></img></td>

  -         </tr>

  -         </table>

  -    </li>	

  -  </ul>

  -

  -  <h1>Active committers</h1>    

  -

  -   <li><b>Jim Moore</b> 

  -   <p>Jim is often seen answering tough question from log4j users.</p>

  -   </li>

  -

  -

  -  <h1>Emeritus committers</h1>    

  -

  -  <p>Committers who ask for emeritus status or inactive for 6 at least

  -  months become emeritus committers. Their privileges are returned as

  -  soon as they decide to contribute once again.</p>

  -

  -  <ul>    

  -  

  -  <li><b>Mathias Bogaert</b> 

  -

  -    <p>While not lurking on <a

  -    href="http://www.theserverside.com/">the serverside</a>, Mathias

  -    mends the log4j documentation.</p>

  -  </li>

  -

  -  <li><b>James P. Cakalic</b>

  -   <p>Jim is the original author of the PatternLayout and the

  -   NTEventLogAppender.</p>

  -  </li>

  -

  -  <li><b>Paul Glezen</b> 

  -

  -   <table>

  -   

  -    <tr><td> <p>Paul consults for customers of IBM's WebSphere

  -     Application Server and related products. His software interests

  -     include developing distributed applications with an emphasis on

  -     source code maintainability and runtime manageability. His

  -     demonstration to customers of the value of the open source

  -     community and their products occasionally results in meager

  -     contributions back to these project.</p></td>

  -

  -       <td><img src="../images/paul-glezen.jpg"></img></td>

  -     </tr>

  -    </table>

  -   </li>

  -

  -   <li><b>Anders Kristensen</b> 

  -

  -   <p>Contributor of many enhancements, Anders takes a keen interest

  -   in log4j and all things Java, OO, and XML. He is currently

  -   specification lead for JSR 116, the SIP Servlet expert group.  </p>

  -   </li>

  -	

  -    <li><b>Jon Skeet</b> 

  -

  -     <p>Jon is a software developer in his mid-twenties living in the

  -     UK. He is a Java enthusiast and very active participant in the

  -     comp.lang.java.* newsgroups as well as a moderator for the log4j

  -     mailing lists. He is a committer for the Ant project, involved

  -     (when time permits!) in tidying up the code documentation.

  -      </p>

  -   </li>

  -

  -   <li><b>Chris Taylor</b> 

  -

  -

  -   <table>   

  -    <tr>

  -    <td> <p>Chris is the author NTEventLogAppender. In around 1832, he

  -     ported our previous GNU-make build system to, at the time little

  -     known but promising, <a href="http://ant.apache.org/">Apache

  -     Ant</a>.</p>

  -    </td>

  -    

  -    <td><img src="../images/chris.jpg"></img></td>

  -    </tr>

  -   </table>

  -   </li>

  -

  -   </ul>

  -

  -    

  -

  -

  -</body>

  +<?xml version="1.0" encoding="iso-8859-1"?>
  +
  +<document>
  +
  +
  +
  +  <properties>
  +
  +    <author email="ceki at apache dot org">Ceki Gulcu</author>
  +
  +    <title>Who we are</title>
  +
  +  </properties>
  +
  +
  +
  +  <meta name="keywords" content="mission, mission statement logging services"/>
  +
  +
  +
  +
  +
  +<body>
  +
  +
  +
  +  <h1>List of developers</h1>
  +
  +       
  +
  +
  +
  +  <p>The software proposed by Logging Services project is the result
  +
  +  of contributions from several dozen developers and hundreds of users
  +
  +  across the globe. Some of the more prominent contributors are listed
  +
  +  below in alphabetical order.
  +
  +  </p>
  +
  +
  +
  +  <!-- ======================================== -->
  +
  +  <!-- LISTED IN ALPHABETICAL ORDER (last name) -->
  +
  +  <!-- ======================================== -->
  +
  +
  +
  +  <h1>PMC members</h1>
  +
  +  <ul>
  +
  +  
  +
  +
  +
  +  <li><b>Curt Arnold</b> 
  +
  +     <p>Curt is the current lead for the log4cxx project. He is also a
  +
  +     regular contributor to the log4j project.
  +
  +     </p>
  +
  +  </li>
  +
  +
  +
  +  <li><b>Nicko Cadell</b> 
  +
  +     <p>Nicko is the current lead for the log4net project.</p>
  +
  +  </li>
  +
  +
  +
  +
  +
  +
  +
  +  <li><b>Scott Deboy</b> 
  +
  +     <p>Scott began contributing to the log4j project in early 2003, 
  +
  +        focusing his efforts on developing a new logging analysis tool that 
  +
  +        would become the next version of Chainsaw.  Along the way, he 
  +
  +        contributed code which gave Chainsaw (and log4j) the ability to process 
  +
  +	    events generated by other logging frameworks.
  +
  +     </p>
  +
  +  </li>
  +
  + 
  +
  +  <li><b>Ceki G&#252;lc&#252;</b> 
  +
  +
  +
  +    <table>
  +
  +    <tr><td> <p>Ceki is the founder the log4j project which continues to
  +
  +    take much of his time. He very much enjoys writing software,
  +
  +    altough he is discovering that it is far more difficult than what
  +
  +    it might seem initially. Ceki is also the author of <a
  +
  +    href="https://www.qos.ch/shop/products/log4j/log4j-Manual.jsp">The
  +
  +    complete log4j manual</a>.  </p></td>
  +
  +    
  +
  +   <td><img src="../images/ceki-72x101.gif"></img></td>
  +
  +    </tr>
  +
  +    </table>
  +
  +  </li>
  +
  +
  +
  +  <li><b>Jacob Kjome</b> 
  +
  +
  +
  +     <p>Jacob Kjome has been developing software since 1997 and has
  +
  +      been playing with Java for about 4 years.  Jake joined the log4j
  +
  +      team after being very active on the user list and contributing
  +
  +      servlet and repository selector related code to the
  +
  +      logj-sandbox.  He is also a committer on the (non-Apache
  +
  +      related) XMLC, BarracudaMVC, and Prevayler projects.  Of late
  +
  +      his free time has been squeezed with a new job and his vigorous
  +
  +      2 year old son, Nicholas, but he still tries to pitch in when he
  +
  +      can. :-)
  +
  +     </p>
  +
  +  </li>
  +
  +
  +
  +  <li><b>Yoav Shapira</b> 
  +
  +    <table>
  +
  +      <tr><td>
  +
  +    
  +
  +      <p>Yoav Shapira contributes numerous Apache and other open-source
  +
  +      projects: you can read more about him at 
  +
  +      <a href="http://www.yoavshapira.com">YoavShapira.com</a>.
  +
  +      </p>
  +
  +      </td>
  +
  +    
  +
  +      <td><img align="right" src="../images/yshapira.bmp"></img></td>
  +
  +      </tr>
  +
  +     </table>
  +
  +   </li>
  +
  +
  +
  +   <li><b>Paul Smith</b> 
  +
  +     <table>
  +
  +       <tr><td>
  +
  +       
  +
  +       <p>Paul Smith has been developing software since 1990, and
  +
  +       playing computer games a few years longer than that.  He has
  +
  +       been thoroughly enjoying Java since 1998 after he gave up on
  +
  +       Visual Basic in disgust.  Paul joined the log4j team after
  +
  +       finding how darn useful it and the companion Chainsaw
  +
  +       application was in '03, and has been helping out where he can,
  +
  +       working on Chainsaw v2, and generally making a good nuisance of
  +
  +       himself.  </p>
  +
  +       </td> 
  +
  +       <td><img align="right" src="../images/psmith.jpg"></img></td>
  +
  +       </tr>
  +
  +     </table>
  +
  +  </li>
  +
  +
  +
  +  <li><b>Mark Womack</b> 
  +
  +
  +
  +         <table>
  +
  +          <tr><td>  <p>Mark Womack has been developing software for over 12
  +	  years. He has been developing in Java for the past 5 years,
  +	  focusing on web application development. He has been an
  +	  active committer for the log4j project since April 2002, contributing 
  +    features for the upcoming v1.3 release. Mark is also the current chair
  +    of the Logging Services PMC.</p></td> 
  +
  +          <td><img src="../images/mark-72x99.gif"></img></td>
  +
  +         </tr>
  +
  +         </table>
  +
  +    </li>	
  +
  +  </ul>
  +
  +
  +
  +  <h1>Active committers</h1>    
  +
  +
  +
  +   <li><b>Jim Moore</b> 
  +
  +   <p>Jim is often seen answering tough question from log4j users.</p>
  +
  +   </li>
  +
  +
  +
  +
  +
  +  <h1>Emeritus committers</h1>    
  +
  +
  +
  +  <p>Committers who ask for emeritus status or inactive for 6 at least
  +
  +  months become emeritus committers. Their privileges are returned as
  +
  +  soon as they decide to contribute once again.</p>
  +
  +
  +
  +  <ul>    
  +
  +  
  +
  +  <li><b>Mathias Bogaert</b> 
  +
  +
  +
  +    <p>While not lurking on <a
  +
  +    href="http://www.theserverside.com/">the serverside</a>, Mathias
  +
  +    mends the log4j documentation.</p>
  +
  +  </li>
  +
  +
  +
  +  <li><b>James P. Cakalic</b>
  +
  +   <p>Jim is the original author of the PatternLayout and the
  +
  +   NTEventLogAppender.</p>
  +
  +  </li>
  +
  +
  +
  +  <li><b>Paul Glezen</b> 
  +
  +
  +
  +   <table>
  +
  +   
  +
  +    <tr><td> <p>Paul consults for customers of IBM's WebSphere
  +
  +     Application Server and related products. His software interests
  +
  +     include developing distributed applications with an emphasis on
  +
  +     source code maintainability and runtime manageability. His
  +
  +     demonstration to customers of the value of the open source
  +
  +     community and their products occasionally results in meager
  +
  +     contributions back to these project.</p></td>
  +
  +
  +
  +       <td><img src="../images/paul-glezen.jpg"></img></td>
  +
  +     </tr>
  +
  +    </table>
  +
  +   </li>
  +
  +
  +
  +   <li><b>Anders Kristensen</b> 
  +
  +
  +
  +   <p>Contributor of many enhancements, Anders takes a keen interest
  +
  +   in log4j and all things Java, OO, and XML. He is currently
  +
  +   specification lead for JSR 116, the SIP Servlet expert group.  </p>
  +
  +   </li>
  +
  +	
  +
  +    <li><b>Jon Skeet</b> 
  +
  +
  +
  +     <p>Jon is a software developer in his mid-twenties living in the
  +
  +     UK. He is a Java enthusiast and very active participant in the
  +
  +     comp.lang.java.* newsgroups as well as a moderator for the log4j
  +
  +     mailing lists. He is a committer for the Ant project, involved
  +
  +     (when time permits!) in tidying up the code documentation.
  +
  +      </p>
  +
  +   </li>
  +
  +
  +
  +   <li><b>Chris Taylor</b> 
  +
  +
  +
  +
  +
  +   <table>   
  +
  +    <tr>
  +
  +    <td> <p>Chris is the author NTEventLogAppender. In around 1832, he
  +
  +     ported our previous GNU-make build system to, at the time little
  +
  +     known but promising, <a href="http://ant.apache.org/">Apache
  +
  +     Ant</a>.</p>
  +
  +    </td>
  +
  +    
  +
  +    <td><img src="../images/chris.jpg"></img></td>
  +
  +    </tr>
  +
  +   </table>
  +
  +   </li>
  +
  +
  +
  +   </ul>
  +
  +
  +
  +    
  +
  +
  +
  +
  +
  +</body>
  +
   </document>
  \ No newline at end of file
  
  
  
  1.15      +88 -44    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.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- project.xml	27 Jul 2004 20:03:26 -0000	1.14
  +++ project.xml	17 Jun 2005 05:45:20 -0000	1.15
   <at>  <at>  -1,44 +1,88  <at>  <at> 
  -<?xml version="1.0" encoding="UTF-8"?>

  -<project name="Logging Services"

  -         href="http://logging.apache.org/">

  -

  -  <title>Logging Services</title>

  -  <!-- <logo href="images/logo.jpg">Apache Logging Services</logo> -->

  -  

  -  <body>

  -    

  -    <menu name="About Logging Services">

  -      <item name="Welcome"   href="/index.html"/>

  -      <item name="News"   href="/site/news.html"/>

  -      <item name="Apache Home" href="http://www.apache.org" />

  -    </menu>

  -

  -   <menu name="Projects">

  -     <item name="log4cxx"   href="/log4cxx"/>

  -     <item name="log4j"   href="/log4j/docs"/>

  -     <item name="log4net"   href="/log4net"/>

  -     <item name="log4php"   href="/log4php"/>

  -   </menu>

  -

  -

  -   <menu name="Information">

  -     <item name="Mission statement"  href="/site/mission-statement.html"/>

  -     <item name="Bylaws"   href="/site/bylaws.html"/>

  -     <item name="License"   href="http://www.apache.org/licenses/LICENSE-2.0.txt"/>

  -     <item name="Who we are"   href="/site/who-we-are.html"/>

  -   </menu>

  -

  -   <menu name="Support">

  -     <item name="Binary distributions" href="/site/binindex.cgi"/>

  -     <item name="CVS Repositories"   href="/site/cvs-repositories.html"/>

  -     <item name="Mailing Lists"   href="/site/mailing-lists.html"/>

  -     <item name="Bug Reporting"   href="/site/bugreport.html"/>

  -   </menu>

  -

  -   <menu name="Reference">

  -     <item name="Web-site maintenance"   href="/site/logging-site.html"/>

  -   </menu>

  -

  -

  -  </body>

  -</project>

  +<?xml version="1.0" encoding="iso-8859-1"?>
  +
  +<project name="Logging Services"
  +
  +         href="http://logging.apache.org/">
  +
  +
  +
  +  <title>Logging Services</title>
  +
  +  <!-- <logo href="images/logo.jpg">Apache Logging Services</logo> -->
  +
  +  
  +
  +  <body>
  +
  +    
  +
  +    <menu name="About Logging Services">
  +
  +      <item name="Welcome"   href="/index.html"/>
  +
  +      <item name="News"   href="/site/news.html"/>
  +
  +      <item name="Apache Home" href="http://www.apache.org" />
  +
  +    </menu>
  +
  +
  +
  +   <menu name="Projects">
  +
  +     <item name="log4cxx"   href="/log4cxx"/>
  +
  +     <item name="log4j"   href="/log4j/docs"/>
  +
  +     <item name="log4net"   href="/log4net"/>
  +
  +     <item name="log4php"   href="/log4php"/>
  +
  +   </menu>
  +
  +
  +
  +
  +
  +   <menu name="Information">
  +
  +     <item name="Mission statement"  href="/site/mission-statement.html"/>
  +
  +     <item name="Bylaws"   href="/site/bylaws.html"/>
  +
  +     <item name="License"   href="http://www.apache.org/licenses/LICENSE-2.0.txt"/>
  +
  +     <item name="Who we are"   href="/site/who-we-are.html"/>
  +
  +   </menu>
  +
  +
  +
  +   <menu name="Support">
  +
  +     <item name="Binary distributions" href="/site/binindex.cgi"/>
  +
  +     <item name="CVS Repositories"   href="/site/cvs-repositories.html"/>
  +
  +     <item name="Mailing Lists"   href="/site/mailing-lists.html"/>
  +
  +     <item name="Bug Reporting"   href="/site/bugreport.html"/>
  +
  +   </menu>
  +
  +
  +
  +   <menu name="Reference">
  +
  +     <item name="Web-site maintenance"   href="/site/logging-site.html"/>
  +
  +   </menu>
  +
  +
  +
  +
  +
  +  </body>
  +
  +</project>
  +
  
  
  

sdeboy | 17 Jun 07:55 2005
Picon

cvs commit: logging-site/src/xdocs index.xml

sdeboy      2005/06/16 22:55:21

  Modified:    src/xdocs index.xml
  Log:
  Lots of folks are responsible for the basic level of 'interop' we have - not just myself.  Also removed
log4cplus from the list.

  Revision  Changes    Path
  1.16      +1 -3      logging-site/src/xdocs/index.xml

  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/index.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- index.xml	17 Jun 2005 05:45:20 -0000	1.15
  +++ index.xml	17 Jun 2005 05:55:21 -0000	1.16
   <at>  <at>  -30,13 +30,11  <at>  <at> 
     </p>

     <p>We should also mention that thanks to the relentless efforts of
  -  many developers and in particular those of Scott Deboy, we currently
  -  have inter-operability between the following projects:
  +  many developers, we have a basic level of interoperability between the following projects:
     </p>

     <ul>
       <li>Log4Cxx (c++)</li>
  -    <li>Log4CPlus</li>
       <li>Log4j</li>
       <li>Log4Net</li>
       <li>Log4Perl</li>

ceki | 17 Jun 10:09 2005
Picon

cvs commit: logging-site/src/xdocs/site binindex.xml bylaws.xml logging-site.xml mission-statement.xml news.xml who-we-are.xml

ceki        2005/06/17 01:09:18

  Modified:    docs     index.html
               docs/site bylaws.html logging-site.html mailing-lists.html
                        mission-statement.html news.html who-we-are.html
               src/xdocs index.xml
               src/xdocs/site binindex.xml bylaws.xml logging-site.xml
                        mission-statement.xml news.xml who-we-are.xml
  Log:
  removed my email in author tags
  
  Revision  Changes    Path
  1.31      +2 -4      logging-site/docs/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/index.html,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- index.html	3 Jun 2005 01:00:12 -0000	1.30
  +++ index.html	17 Jun 2005 08:09:18 -0000	1.31
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
   
                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="ceki at apache dot org">
  +            <meta name="email" value="$au.getAttributeValue("email")">
                                           <meta name="author" value="Yoav Shapira">
               <meta name="email" value="yoavs at apache dot org">
               
   <at>  <at>  -62,12 +62,10  <at>  <at> 
     debugging and auditing. 
     </p>
                                                   <p>We should also mention that thanks to the relentless efforts of
  -  many developers and in particular those of Scott Deboy, we currently
  -  have inter-operability between the following projects:
  +  many developers, we have a basic level of interoperability between the following projects:
     </p>
                                                   <ul>
       <li>Log4Cxx (c++)</li>
  -    <li>Log4CPlus</li>
       <li>Log4j</li>
       <li>Log4Net</li>
       <li>Log4Perl</li>
  
  
  
  1.20      +313 -1    logging-site/docs/site/bylaws.html
  
  Index: bylaws.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/bylaws.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- bylaws.html	11 Jan 2005 21:39:43 -0000	1.19
  +++ bylaws.html	17 Jun 2005 08:09:18 -0000	1.20
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
   
                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="ceki at apache dot org">
  +            <meta name="email" value="$au.getAttributeValue("email")">
               
               
                                        <meta  name="keywords"  content="bylaws, logging services"  />
   <at>  <at>  -48,357 +48,669  <at>  <at> 
   		       
                                          <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>Roles and Responsibilities<a name="Roles and Responsibilities"> </a></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">Users<a name="Users"> </a></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">Developers<a name="Developers"> </a></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">Committers<a name="Committers"> </a></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">Project Management Committee
  +
        <a name="Project Management Committee"> </a></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">Decision Making
  +
         <a name="Decision Making"> </a> 
  +
        </h3>
                                                         <p>Within the Logging Services project, different types of
  +
        decisions require different forms of approval. For example, the
  +
        previous section 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">Voting<a name="Voting"> </a></h3>
                                                         <p>Decisions regarding the project are made by votes on the
  +
        primary project mailing list (general <at> 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 class="ls" 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>Approvals<a name="Approvals"> </a></h3>
                                                         <p>These are the types of approvals that can be sought. Different
  +
          actions require different types of approvals</p>
                                                         <table class="ls" valign="top">
  +
       <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>Vetoes<a name="Vetoes"> </a></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>Actions<a name="Actions"> </a></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 class="ls" 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 valign="top">
  +
         <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>Voting Timeframes<a name="Voting Timeframes"> </a></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>
                             
               
  
  
  
  1.14      +1 -1      logging-site/docs/site/logging-site.html
  
  Index: logging-site.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/logging-site.html,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- logging-site.html	11 Jan 2005 21:39:43 -0000	1.13
  +++ logging-site.html	17 Jun 2005 08:09:18 -0000	1.14
   <at>  <at>  -20,7 +20,7  <at>  <at> 
                                           <meta name="author" value="Ted Husted">
               <meta name="email" value="husted.AT.apache.DOT.org">
                                           <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="ceki.AT.apache.DOT.org">
  +            <meta name="email" value="$au.getAttributeValue("email")">
               
               
                                       
  
  
  
  1.24      +138 -0    logging-site/docs/site/mailing-lists.html
  
  Index: mailing-lists.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/mailing-lists.html,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- mailing-lists.html	10 Mar 2005 00:17:24 -0000	1.23
  +++ mailing-lists.html	17 Jun 2005 08:09:18 -0000	1.24
   <at>  <at>  -48,180 +48,318  <at>  <at> 
   		       
                                          <h1>Mailing Lists</h1>
                                                         <p>Please read the <a href="http://jakarta.apache.org/site/mail.html">guidelines of the
  +
     Jakarta Project</a> before subscribing and posting to any of the
  +
     lists below. They apply to Logging Services' lists as well.
  +
     </p>
                                                         <p><em>All lists are subscriber only lists, this means you have to
  +
     subscribe before you can post to them.</em>
  +
     </p>
                                                         <p>Please do your best to ensure that you are not sending HTML or
  +
     "Stylelized" email to the list. If you are using Outlook or Outlook
  +
     Express or Eudora, chances are that you are sending HTML email by
  +
     default. There is usually a setting that will allow you to send
  +
     "Plain Text" email.
  +
     </p>
                                                         <h2>The Logging Services <b>General</b> list</h2>
                                                         <p><b>Medium Traffic</b>
  +
      <a href="mailto:general-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:general-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br /><b>Archives:</b>
  +
           <a href="http://marc.theaimsgroup.com/?l=apache-logging-general&amp;r=1&amp;w=2">MARC</a>, 
  +
           <a href="http://dir.gmane.org/gmane.comp.apache.logging">GMANE</a>,
  +
           apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-general/">mod_mbox</a>, 
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=199">eyebrowse</a>
  +
      </p>
                                                         <p>This is the project general mailing list. This is where ideas,
  +
      suggestions, and comments are exchanged that deal with the
  +
      <em>overall</em> Logging Services project. READ: This is
  +
      <em>not</em> a place to ask technical questions related to <a href="http://logging.apache.org/log4j/">log4j</a>, or any other
  +
      single Logging Services project. Matters that affect the project as
  +
      a whole are decided here. If you are interested in adding a new
  +
      sub-project to Logging Services, please see <a href="http://jakarta.apache.org/site/newproject.html">this
  +
      page</a>.
  +
     </p>
                                                         <hr />
                                                         <h2>Log4cxx lists</h2>
                                                         <h3>log4cxx-user list</h3>
                                                         <p>
  +
      <b>Medium Traffic</b>
  +
      <a href="mailto:log4cxx-user-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:log4cxx-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br />
  +
      <b>Archives:</b>
  +
                       <a href="http://marc.theaimsgroup.com/?l=log4cxx-user&amp;r=1&amp;w=2">MARC</a>, 
  +
                       <a href="http://dir.gmane.org/gmane.comp.apache.logging.log4cxx.user">GMANE</a>,
  +
                       and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4cxx-user/">mod_mbox</a>,
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=219">eyebrowse</a>
  +
      </p>
                                                         <p>This is the list for users of log4jcxx logging framework. It is
  +
      also a good forum for asking questions about how log4cxx works, and
  +
      how it can be used. Log4cxx developers should also join this list
  +
      to offer support to their users.
  +
      </p>
                                                         <h3>log4cxx-dev list</h3>
                                                         <p>
  +
      <b>Medium Traffic</b>
  +
      <a href="mailto:log4cxx-dev-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:log4cxx-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br /><b>Archives:</b>
  +
                       <a href="http://marc.theaimsgroup.com/?l=log4cxx-dev&amp;r=1&amp;w=2">MARC</a>, 
  +
                       <a href="http://dir.gmane.org/gmane.comp.apache.logging.log4cxx.devel">GMANE</a>,
  +
                       and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4cxx-dev/">mod_mbox</a>, 
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=218">eyebrowse</a></p>
                                                         <p>This is the list where participating developers of the log4cxx
  +
      framework meet and discuss issues, code changes/additions,
  +
      etc. Subscribers to this list get notices of each and every code
  +
      change, build results, testing notices, etc. Do not send mail to
  +
      this list with usage questions or configuration problems -- that's
  +
      what log4cxx-user is for.
  +
      </p>
                                                         <hr />
                                                         <h2>Log4j lists</h2>
                                                         <h3>log4j-user list</h3>
                                                         <p>
  +
      <b>Medium Traffic</b>
  +
      <a href="mailto:log4j-user-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:log4j-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br /><b>Archives:</b>
  +
                       <a href="http://marc.theaimsgroup.com/?l=log4j-user&amp;r=1&amp;w=2">MARC</a>, 
  +
                       <a href="http://dir.gmane.org/gmane.comp.jakarta.log4j.user">GMANE</a>,
  +
                       and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4j-user/">mod_mbox</a>, 
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=201">eyebrowse</a></p>
                                                         <p>This is the list for users of log4jcxx logging framework. It is
  +
      also a good forum for asking questions about how log4j works, and
  +
      how it can be used. Log4j developers should also join this list
  +
      to offer support to their users.
  +
      </p>
                                                         <h3>log4j-dev list</h3>
                                                         <p>
  +
      <b>Medium Traffic</b>
  +
      <a href="mailto:log4j-dev-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:log4j-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br /><b>Archives:</b>
  +
                       <a href="http://marc.theaimsgroup.com/?l=log4j-dev&amp;r=1&amp;w=2">MARC</a>, 
  +
                       <a href="http://dir.gmane.org/gmane.comp.jakarta.log4j.devel">GMANE</a>,
  +
                       and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4j-dev/">mod_mbox</a>, 
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=200">eyebrowse</a></p>
                                                         <p>This is the list where participating developers of the log4j
  +
      framework meet and discuss issues, code changes/additions,
  +
      etc. Subscribers to this list get notices of each and every code
  +
      change, build results, testing notices, etc. Do not send mail to
  +
      this list with usage questions or configuration problems -- that's
  +
      what log4j-user is for.
  +
      </p>
                                                         <hr />
                                                         <h2>Log4net lists</h2>
                                                         <h3>log4net-user list</h3>
                                                         <p>
  +
      <b>Medium Traffic</b>
  +
      <a href="mailto:log4net-user-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:log4net-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br /><b>Archives:</b>
  +
                       <a href="http://marc.theaimsgroup.com/?l=log4net-user&amp;r=1&amp;w=2">MARC</a>, 
  +
                       <a href="http://dir.gmane.org/gmane.comp.log.log4net.user">GMANE</a>,
  +
                       and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4net-user/">mod_mbox</a>, 
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=215">eyebrowse</a></p>
                                                         <p>This is the list for users of log4jcxx logging framework. It is
  +
      also a good forum for asking questions about how log4net works, and
  +
      how it can be used. Log4net developers should also join this list
  +
      to offer support to their users.
  +
      </p>
                                                         <h3>log4net-dev list</h3>
                                                         <p>
  +
      <b>Medium Traffic</b>
  +
      <a href="mailto:log4net-dev-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:log4net-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br /><b>Archives:</b>
  +
                       <a href="http://marc.theaimsgroup.com/?l=log4net-dev&amp;r=1&amp;w=2">MARC</a> 
  +
                       and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4net-dev/">mod_mbox</a>, 
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=215">eyebrowse</a></p>
                                                         <p>This is the list where participating developers of the log4net
  +
      framework meet and discuss issues, code changes/additions,
  +
      etc. Subscribers to this list get notices of each and every code
  +
      change, build results, testing notices, etc. Do not send mail to
  +
      this list with usage questions or configuration problems -- that's
  +
      what log4net-user is for.
  +
      </p>
                                                         <hr />
                                                         <h2>Log4php lists</h2>
                                                         <h3>log4php-user list</h3>
                                                         <p>
  +
      <b>Medium Traffic</b>
  +
      <a href="mailto:log4php-user-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:log4php-user-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br /><b>Archives:</b>
  +
                       <a href="http://marc.theaimsgroup.com/?l=log4php-user&amp;r=1&amp;w=2">MARC</a>
  +
                       and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4php-user/">mod_mbox</a>, 
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=217">eyebrowse</a></p>
                                                         <p>This is the list for users of log4php logging framework. It is
  +
      also a good forum for asking questions about how log4php works, and
  +
      how it can be used. Log4php developers should also join this list
  +
      to offer support to their users.
  +
      </p>
                                                         <h3>log4php-dev list</h3>
                                                         <p>
  +
      <b>Medium Traffic</b>
  +
      <a href="mailto:log4php-dev-subscribe <at> logging.apache.org">Subscribe</a>
  +
      <a href="mailto:log4php-dev-unsubscribe <at> logging.apache.org">Unsubscribe</a>
  +
      <a href="http://jakarta.apache.org/site/mail.html">Guidelines</a>
  +
      <br /><b>Archives:</b>
  +
                       <a href="http://marc.theaimsgroup.com/?l=log4php-dev&amp;r=1&amp;w=2">MARC</a> 
  +
                       and apache.org <a href="http://mail-archives.eu.apache.org/mod_mbox/logging-log4php-dev/">mod_mbox</a>, 
  +
                       <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=216">eyebrowse</a></p>
                                                         <p>This is the list where participating developers of the log4php
  +
      framework meet and discuss issues, code changes/additions,
  +
      etc. Subscribers to this list get notices of each and every code
  +
      change, build results, testing notices, etc. Do not send mail to
  +
      this list with usage questions or configuration problems -- that's
  +
      what log4php-user is for.
  +
      </p>
                             
               
  
  
  
  1.18      +67 -1     logging-site/docs/site/mission-statement.html
  
  Index: mission-statement.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/mission-statement.html,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- mission-statement.html	11 Jan 2005 21:39:43 -0000	1.17
  +++ mission-statement.html	17 Jun 2005 08:09:18 -0000	1.18
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
   
                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="ceki at apache dot org">
  +            <meta name="email" value="$au.getAttributeValue("email")">
               
               
                                        <meta  name="keywords"  content="mission, mission statement logging services"  />
   <at>  <at>  -48,74 +48,140  <at>  <at> 
   		       
                                          <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ülcü
  +
         Jacob Kjome 
  +
         Yoav Shapira 
  +
         Paul Smith 
  +
         Mark Womack
   
  +
  +
      NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mr. Ceki
  +
      Gülcü 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>
                             
               
  
  
  
  1.26      +17 -1     logging-site/docs/site/news.html
  
  Index: news.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/news.html,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- news.html	1 May 2005 05:21:32 -0000	1.25
  +++ news.html	17 Jun 2005 08:09:18 -0000	1.26
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
   
                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="ceki at qos dot ch">
  +            <meta name="email" value="$au.getAttributeValue("email")">
                                           <meta name="author" value="Yoav Shapira">
               <meta name="email" value="yoavs at apache dot org">
               
   <at>  <at>  -50,31 +50,47  <at>  <at> 
                                            <h1>News & Status</strong></h1>
                                       <h3>11 January 2005 - log4cxx graduates from the incubator</h3>
                                                   <p>The Incubator PMC has voted to graduate log4cxx.  log4cxx is
  +
    now a subproject of the Apache Logging Services Project.
  +
    </p>
                                                   <hr noshade="noshade" size="1" />
                                                   <h3>22nd of January 2004 - Logging Services PMC has voted for the
  +
   adoption of log4cxx, log4net and log4php</h3>
                                                   <p>The Logging Services PMC has voted for the incubation of the
  +
    log4cxx, log4net and log4php projects. These votes pave the vote for
  +
    their migration into Apache Logging Services.
  +
    </p>
                                                   <p>We heartily welcome the new projects.</p>
                                                   <hr noshade="noshade" size="1" />
                                                   <h3>17th December 2003 - Creation of the Logging Services Project</h3>
                                                   <p>The Board of Directors of the Apache Software foundation voted
  +
    unanimously for the creation of the Apache Logging Services project.
  +
    The mailing list thread with the discussion preceding the creation
  +
    of this project is available
  +
    <a href="http://marc.theaimsgroup.com/?t=107115526200001&amp;r=1&amp;w=2">here.</a>
  +
    </p>
                                                   <hr noshade="noshade" size="1" />
                                                   <h3>
  +
   Got News?
  +
   </h3>
                                                   <p>If you would like to submit an item for posting to this page, send
  +
   an email with the subject <b>[NEWS]</b> to the <code>general at logging dot
  +
   apache dot org</code> mailing list..
  +
   </p>
                                                
               
  
  
  
  1.22      +170 -7    logging-site/docs/site/who-we-are.html
  
  Index: who-we-are.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/who-we-are.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- who-we-are.html	11 Jan 2005 21:39:43 -0000	1.21
  +++ who-we-are.html	17 Jun 2005 08:09:18 -0000	1.22
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
   
                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="ceki at apache dot org">
  +            <meta name="email" value="$au.getAttributeValue("email")">
               
               
                                        <meta  name="keywords"  content="mission, mission statement logging services"  />
   <at>  <at>  -48,182 +48,345  <at>  <at> 
   		       
                                          <h1>List of developers</h1>
                                                         <p>The software proposed by Logging Services project is the result
  +
     of contributions from several dozen developers and hundreds of users
  +
     across the globe. Some of the more prominent contributors are listed
  +
     below in alphabetical order.
  +
     </p>
                                                         <h1>PMC members</h1>
                                                         <ul>
  +
     
   
  +
  +
     <li><b>Curt Arnold</b> 
  +
        <p>Curt is the current lead for the log4cxx project. He is also a
  +
        regular contributor to the log4j project.
  +
        </p>
  +
     </li>
   
  +
  +
     <li><b>Nicko Cadell</b> 
  +
        <p>Nicko is the current lead for the log4net project.</p>
  +
     </li>
   
   
   
  +
  +
  +
  +
     <li><b>Scott Deboy</b> 
  +
        <p>Scott began contributing to the log4j project in early 2003, 
  +
           focusing his efforts on developing a new logging analysis tool that 
  +
           would become the next version of Chainsaw.  Along the way, he 
  +
           contributed code which gave Chainsaw (and log4j) the ability to process 
  +
   	    events generated by other logging frameworks.
  +
        </p>
  +
     </li>
  +
    
  +
     <li><b>Ceki Gülcü</b> 
   
  +
  +
       <table>
  -    <tr><td> <p>Ceki serves as the chairman of the Logging Services
  -    project. He is the founder the log4j project which continues to
  +
  +    <tr><td> <p>Ceki is the founder the log4j project which continues to
  +
       take much of his time. He very much enjoys writing software,
  +
       altough he is discovering that it is far more difficult than what
  +
       it might seem initially. Ceki is also the author of <a href="https://www.qos.ch/shop/products/log4j/log4j-Manual.jsp">The
  +
       complete log4j manual</a>.  </p></td>
  +
       
  +
      <td><img src="../images/ceki-72x101.gif" /></td>
  +
       </tr>
  +
       </table>
  +
     </li>
   
  +
  +
     <li><b>Jacob Kjome</b> 
   
  +
  +
        <p>Jacob Kjome has been developing software since 1997 and has
  +
         been playing with Java for about 4 years.  Jake joined the log4j
  +
         team after being very active on the user list and contributing
  +
         servlet and repository selector related code to the
  +
         logj-sandbox.  He is also a committer on the (non-Apache
  +
         related) XMLC, BarracudaMVC, and Prevayler projects.  Of late
  +
         his free time has been squeezed with a new job and his vigorous
  +
         2 year old son, Nicholas, but he still tries to pitch in when he
  +
         can. :-)
  +
        </p>
  +
     </li>
   
  +
  +
     <li><b>Yoav Shapira</b> 
  +
       <table>
  +
         <tr><td>
  +
       
  +
         <p>Yoav Shapira contributes numerous Apache and other open-source
  +
         projects: you can read more about him at 
  +
         <a href="http://www.yoavshapira.com">YoavShapira.com</a>.
  +
         </p>
  +
         </td>
  +
       
  +
         <td><img align="right" src="../images/yshapira.bmp" /></td>
  +
         </tr>
  +
        </table>
  +
      </li>
   
  +
  +
      <li><b>Paul Smith</b> 
  +
        <table>
  +
          <tr><td>
  +
          
  +
          <p>Paul Smith has been developing software since 1990, and
  +
          playing computer games a few years longer than that.  He has
  +
          been thoroughly enjoying Java since 1998 after he gave up on
  +
          Visual Basic in disgust.  Paul joined the log4j team after
  +
          finding how darn useful it and the companion Chainsaw
  +
          application was in '03, and has been helping out where he can,
  +
          working on Chainsaw v2, and generally making a good nuisance of
  +
          himself.  </p>
  +
          </td> 
  +
          <td><img align="right" src="../images/psmith.jpg" /></td>
  +
          </tr>
  +
        </table>
  +
     </li>
   
  +
  +
     <li><b>Mark Womack</b> 
   
  +
  +
            <table>
  +
             <tr><td>  <p>Mark Womack has been developing software for over 12
  -	  years. He has been developing in Java for the past 4 years,
  +	  years. He has been developing in Java for the past 5 years,
   	  focusing on web application development. He has been an
  -	  active committer for the Apache Jakarta log4j project since
  -	  April 2002, contributing features for the upcoming v1.3
  -	  release. </p></td> 
  +	  active committer for the log4j project since April 2002, contributing 
  +    features for the upcoming v1.3 release. Mark is also the current chair
  +    of the Logging Services PMC.</p></td> 
  +
             <td><img src="../images/mark-72x99.gif" /></td>
  +
            </tr>
  +
            </table>
  +
       </li>	
  +
     </ul>
                                                         <h1>Active committers</h1>
                                                         <li><b>Jim Moore</b> 
  +
      <p>Jim is often seen answering tough question from log4j users.</p>
  +
      </li>
                                                         <h1>Emeritus committers</h1>
                                                         <p>Committers who ask for emeritus status or inactive for 6 at least
  +
     months become emeritus committers. Their privileges are returned as
  +
     soon as they decide to contribute once again.</p>
                                                         <ul>    
  +
     
  +
     <li><b>Mathias Bogaert</b> 
   
  +
  +
       <p>While not lurking on <a href="http://www.theserverside.com/">the serverside</a>, Mathias
  +
       mends the log4j documentation.</p>
  +
     </li>
   
  +
  +
     <li><b>James P. Cakalic</b>
  +
      <p>Jim is the original author of the PatternLayout and the
  +
      NTEventLogAppender.</p>
  +
     </li>
   
  +
  +
     <li><b>Paul Glezen</b> 
   
  +
  +
      <table>
  +
      
  +
       <tr><td> <p>Paul consults for customers of IBM's WebSphere
  +
        Application Server and related products. His software interests
  +
        include developing distributed applications with an emphasis on
  +
        source code maintainability and runtime manageability. His
  +
        demonstration to customers of the value of the open source
  +
        community and their products occasionally results in meager
  +
        contributions back to these project.</p></td>
   
  +
  +
          <td><img src="../images/paul-glezen.jpg" /></td>
  +
        </tr>
  +
       </table>
  +
      </li>
   
  +
  +
      <li><b>Anders Kristensen</b> 
   
  +
  +
      <p>Contributor of many enhancements, Anders takes a keen interest
  +
      in log4j and all things Java, OO, and XML. He is currently
  +
      specification lead for JSR 116, the SIP Servlet expert group.  </p>
  +
      </li>
  +
   	
  +
       <li><b>Jon Skeet</b> 
   
  +
  +
        <p>Jon is a software developer in his mid-twenties living in the
  +
        UK. He is a Java enthusiast and very active participant in the
  +
        comp.lang.java.* newsgroups as well as a moderator for the log4j
  +
        mailing lists. He is a committer for the Ant project, involved
  +
        (when time permits!) in tidying up the code documentation.
  +
         </p>
  +
      </li>
   
  +
  +
      <li><b>Chris Taylor</b> 
   
   
  +
  +
  +
      <table>   
  +
       <tr>
  +
       <td> <p>Chris is the author NTEventLogAppender. In around 1832, he
  +
        ported our previous GNU-make build system to, at the time little
  +
        known but promising, <a href="http://ant.apache.org/">Apache
  +
        Ant</a>.</p>
  +
       </td>
  +
       
  +
       <td><img src="../images/chris.jpg" /></td>
  +
       </tr>
  +
      </table>
  +
      </li>
   
  +
  +
      </ul>
                             
               
  
  
  
  1.17      +1 -1      logging-site/src/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/index.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- index.xml	17 Jun 2005 05:55:21 -0000	1.16
  +++ index.xml	17 Jun 2005 08:09:18 -0000	1.17
   <at>  <at>  -2,7 +2,7  <at>  <at> 
   <document>
   
     <properties>
  -    <author email="ceki at apache dot org">Ceki Gulcu</author>
  +    <author>Ceki Gulcu</author>
       <author email="yoavs at apache dot org">Yoav Shapira</author>
       <title>Welcome</title>
     </properties>
  
  
  
  1.25      +1 -1      logging-site/src/xdocs/site/binindex.xml
  
  Index: binindex.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/binindex.xml,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- binindex.xml	17 Jun 2005 05:45:20 -0000	1.24
  +++ binindex.xml	17 Jun 2005 08:09:18 -0000	1.25
   <at>  <at>  -3,7 +3,7  <at>  <at> 
   
     <properties>
       <author email="jon.AT.latchkey.DOT.com">Jon S. Stevens</author>
  -    <author >Ceki Gulcu</author>
  +    <author>Ceki Gulcu</author>
       <title>Binary Downloads</title>
     </properties>
   
  
  
  
  1.9       +1 -1      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.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- bylaws.xml	17 Jun 2005 05:45:20 -0000	1.8
  +++ bylaws.xml	17 Jun 2005 08:09:18 -0000	1.9
   <at>  <at>  -6,7 +6,7  <at>  <at> 
   
     <properties>
   
  -    <author email="ceki at apache dot org">Ceki Gulcu</author>
  +    <author >Ceki Gulcu</author>
   
       <title>Bylaws of the Logging Services Project</title>
   
  
  
  
  1.12      +1 -1      logging-site/src/xdocs/site/logging-site.xml
  
  Index: logging-site.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/logging-site.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- logging-site.xml	17 Jun 2005 05:45:20 -0000	1.11
  +++ logging-site.xml	17 Jun 2005 08:09:18 -0000	1.12
   <at>  <at>  -4,7 +4,7  <at>  <at> 
     <properties>
       <author email="jon.AT.latchkey.DOT.com">Jon S. Stevens</author>
       <author email="husted.AT.apache.DOT.org">Ted Husted</author>
  -    <author email="ceki.AT.apache.DOT.org">Ceki Gulcu</author>
  +    <author>Ceki Gulcu</author>
       <title>About the Logging Services web-site</title>
     </properties>
   
  
  
  
  1.3       +1 -1      logging-site/src/xdocs/site/mission-statement.xml
  
  Index: mission-statement.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/mission-statement.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- mission-statement.xml	17 Jun 2005 05:45:20 -0000	1.2
  +++ mission-statement.xml	17 Jun 2005 08:09:18 -0000	1.3
   <at>  <at>  -6,7 +6,7  <at>  <at> 
   
     <properties>
   
  -    <author email="ceki at apache dot org">Ceki Gulcu</author>
  +    <author>Ceki Gulcu</author>
   
       <title>Mission Statement for the Logging Services Project</title>
   
  
  
  
  1.10      +1 -1      logging-site/src/xdocs/site/news.xml
  
  Index: news.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/news.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- news.xml	17 Jun 2005 05:45:20 -0000	1.9
  +++ news.xml	17 Jun 2005 08:09:18 -0000	1.10
   <at>  <at>  -6,7 +6,7  <at>  <at> 
   
     <properties>
   
  -    <author email="ceki at qos dot ch">Ceki Gulcu</author>
  +    <author>Ceki Gulcu</author>
   
       <author email="yoavs at apache dot org">Yoav Shapira</author>
   
  
  
  
  1.11      +1 -1      logging-site/src/xdocs/site/who-we-are.xml
  
  Index: who-we-are.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/who-we-are.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- who-we-are.xml	17 Jun 2005 05:45:20 -0000	1.10
  +++ who-we-are.xml	17 Jun 2005 08:09:18 -0000	1.11
   <at>  <at>  -6,7 +6,7  <at>  <at> 
   
     <properties>
   
  -    <author email="ceki at apache dot org">Ceki Gulcu</author>
  +    <author>Ceki Gulcu</author>
   
       <title>Who we are</title>
   
  
  
  

ceki | 17 Jun 10:54 2005
Picon

cvs commit: logging-site/docs/site binindex.html bylaws.html logging-site.html mailing-lists.html mission-statement.html news.html who-we-are.html

ceki        2005/06/17 01:54:31

  Modified:    src/xdocs index.xml
               src/xdocs/site binindex.xml bylaws.xml logging-site.xml
                        mailing-lists.xml mission-statement.xml news.xml
                        who-we-are.xml
               docs     index.html
               docs/site binindex.html bylaws.html logging-site.html
                        mailing-lists.html mission-statement.html news.html
                        who-we-are.html
  Log:

  Had to add back the email attribute in order to keep anakia happy. The

  value of the email attribute set to "not <at> disclosed". I suggest that

  other authors do the same.

  PR:

  Obtained from:

  Submitted by:	

  Reviewed by:	

  
  Revision  Changes    Path
  1.18      +1 -1      logging-site/src/xdocs/index.xml

  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/index.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- index.xml	17 Jun 2005 08:09:18 -0000	1.17
  +++ index.xml	17 Jun 2005 08:54:30 -0000	1.18
   <at>  <at>  -2,7 +2,7  <at>  <at> 
   <document>

     <properties>
  -    <author>Ceki Gulcu</author>
  +    <author email="not <at> disclosed">Ceki Gulcu</author>
       <author email="yoavs at apache dot org">Yoav Shapira</author>
       <title>Welcome</title>
     </properties>

  

  1.26      +1 -1      logging-site/src/xdocs/site/binindex.xml

  Index: binindex.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/binindex.xml,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- binindex.xml	17 Jun 2005 08:09:18 -0000	1.25
  +++ binindex.xml	17 Jun 2005 08:54:30 -0000	1.26
   <at>  <at>  -3,7 +3,7  <at>  <at> 

     <properties>
       <author email="jon.AT.latchkey.DOT.com">Jon S. Stevens</author>
  -    <author>Ceki Gulcu</author>
  +    <author email="not <at> disclosed">Ceki Gulcu</author>
       <title>Binary Downloads</title>
     </properties>

  

  
  1.10      +1 -1      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.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- bylaws.xml	17 Jun 2005 08:09:18 -0000	1.9
  +++ bylaws.xml	17 Jun 2005 08:54:30 -0000	1.10
   <at>  <at>  -6,7 +6,7  <at>  <at> 

     <properties>

  -    <author >Ceki Gulcu</author>
  +    <author email="not <at> disclosed">Ceki Gulcu</author>

       <title>Bylaws of the Logging Services Project</title>

  

  
  1.13      +1 -1      logging-site/src/xdocs/site/logging-site.xml

  Index: logging-site.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/logging-site.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- logging-site.xml	17 Jun 2005 08:09:18 -0000	1.12
  +++ logging-site.xml	17 Jun 2005 08:54:30 -0000	1.13
   <at>  <at>  -4,7 +4,7  <at>  <at> 
     <properties>
       <author email="jon.AT.latchkey.DOT.com">Jon S. Stevens</author>
       <author email="husted.AT.apache.DOT.org">Ted Husted</author>
  -    <author>Ceki Gulcu</author>
  +    <author email="not <at> disclosed">Ceki Gulcu</author>
       <title>About the Logging Services web-site</title>
     </properties>

  

  
  1.9       +1 -1      logging-site/src/xdocs/site/mailing-lists.xml

  Index: mailing-lists.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/mailing-lists.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- mailing-lists.xml	17 Jun 2005 05:45:20 -0000	1.8
  +++ mailing-lists.xml	17 Jun 2005 08:54:30 -0000	1.9
   <at>  <at>  -6,7 +6,7  <at>  <at> 

     <properties>

  -    <author email="ceki at apache dot org">Ceki Gulcu</author>
  +    <author  email="not <at> disclosed">Ceki Gulcu</author>

       <title>Mailing lists for the Logging Services Project</title>

  

  
  1.4       +1 -1      logging-site/src/xdocs/site/mission-statement.xml

  Index: mission-statement.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/mission-statement.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- mission-statement.xml	17 Jun 2005 08:09:18 -0000	1.3
  +++ mission-statement.xml	17 Jun 2005 08:54:30 -0000	1.4
   <at>  <at>  -6,7 +6,7  <at>  <at> 

     <properties>

  -    <author>Ceki Gulcu</author>
  +    <author  email="not <at> disclosed">Ceki Gulcu</author>

       <title>Mission Statement for the Logging Services Project</title>

  

  
  1.11      +1 -1      logging-site/src/xdocs/site/news.xml

  Index: news.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/news.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- news.xml	17 Jun 2005 08:09:18 -0000	1.10
  +++ news.xml	17 Jun 2005 08:54:30 -0000	1.11
   <at>  <at>  -6,7 +6,7  <at>  <at> 

     <properties>

  -    <author>Ceki Gulcu</author>
  +    <author  email="not <at> disclosed">Ceki Gulcu</author>

       <author email="yoavs at apache dot org">Yoav Shapira</author>

  

  
  1.12      +1 -1      logging-site/src/xdocs/site/who-we-are.xml

  Index: who-we-are.xml
  ===================================================================
  RCS file: /home/cvs/logging-site/src/xdocs/site/who-we-are.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- who-we-are.xml	17 Jun 2005 08:09:18 -0000	1.11
  +++ who-we-are.xml	17 Jun 2005 08:54:30 -0000	1.12
   <at>  <at>  -6,7 +6,7  <at>  <at> 

     <properties>

  -    <author>Ceki Gulcu</author>
  +    <author  email="not <at> disclosed">Ceki Gulcu</author>

       <title>Who we are</title>

  

  
  1.32      +1 -1      logging-site/docs/index.html

  Index: index.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/index.html,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- index.html	17 Jun 2005 08:09:18 -0000	1.31
  +++ index.html	17 Jun 2005 08:54:30 -0000	1.32
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>

                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="$au.getAttributeValue("email")">
  +            <meta name="email" value="not <at> disclosed">
                                           <meta name="author" value="Yoav Shapira">
               <meta name="email" value="yoavs at apache dot org">

  

  
  1.30      +1 -1      logging-site/docs/site/binindex.html

  Index: binindex.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/binindex.html,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- binindex.html	10 May 2005 15:00:56 -0000	1.29
  +++ binindex.html	17 Jun 2005 08:54:30 -0000	1.30
   <at>  <at>  -18,7 +18,7  <at>  <at> 
                                                       <meta name="author" value="Jon S. Stevens">
               <meta name="email" value="jon.AT.latchkey.DOT.com">
                                           <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="$au.getAttributeValue("email")">
  +            <meta name="email" value="not <at> disclosed">

               

  

  
  1.21      +1 -1      logging-site/docs/site/bylaws.html

  Index: bylaws.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/bylaws.html,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- bylaws.html	17 Jun 2005 08:09:18 -0000	1.20
  +++ bylaws.html	17 Jun 2005 08:54:30 -0000	1.21
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>

                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="$au.getAttributeValue("email")">
  +            <meta name="email" value="not <at> disclosed">

               
                                        <meta  name="keywords"  content="bylaws, logging services"  />

  

  1.15      +1 -1      logging-site/docs/site/logging-site.html

  Index: logging-site.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/logging-site.html,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- logging-site.html	17 Jun 2005 08:09:18 -0000	1.14
  +++ logging-site.html	17 Jun 2005 08:54:30 -0000	1.15
   <at>  <at>  -20,7 +20,7  <at>  <at> 
                                           <meta name="author" value="Ted Husted">
               <meta name="email" value="husted.AT.apache.DOT.org">
                                           <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="$au.getAttributeValue("email")">
  +            <meta name="email" value="not <at> disclosed">

               

  

  
  1.25      +1 -1      logging-site/docs/site/mailing-lists.html

  Index: mailing-lists.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/mailing-lists.html,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- mailing-lists.html	17 Jun 2005 08:09:18 -0000	1.24
  +++ mailing-lists.html	17 Jun 2005 08:54:30 -0000	1.25
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>

                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="ceki at apache dot org">
  +            <meta name="email" value="not <at> disclosed">

               
                                        <meta  name="keywords"  content="mailing list, mailing list logging services"  />

  

  1.19      +1 -1      logging-site/docs/site/mission-statement.html

  Index: mission-statement.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/mission-statement.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- mission-statement.html	17 Jun 2005 08:09:18 -0000	1.18
  +++ mission-statement.html	17 Jun 2005 08:54:30 -0000	1.19
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>

                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="$au.getAttributeValue("email")">
  +            <meta name="email" value="not <at> disclosed">

               
                                        <meta  name="keywords"  content="mission, mission statement logging services"  />

  

  1.27      +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.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- news.html	17 Jun 2005 08:09:18 -0000	1.26
  +++ news.html	17 Jun 2005 08:54:30 -0000	1.27
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>

                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="$au.getAttributeValue("email")">
  +            <meta name="email" value="not <at> disclosed">
                                           <meta name="author" value="Yoav Shapira">
               <meta name="email" value="yoavs at apache dot org">

  

  
  1.23      +1 -1      logging-site/docs/site/who-we-are.html

  Index: who-we-are.html
  ===================================================================
  RCS file: /home/cvs/logging-site/docs/site/who-we-are.html,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- who-we-are.html	17 Jun 2005 08:09:18 -0000	1.22
  +++ who-we-are.html	17 Jun 2005 08:54:30 -0000	1.23
   <at>  <at>  -16,7 +16,7  <at>  <at> 
               <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>

                                                       <meta name="author" value="Ceki Gulcu">
  -            <meta name="email" value="$au.getAttributeValue("email")">
  +            <meta name="email" value="not <at> disclosed">

               
                                        <meta  name="keywords"  content="mission, mission statement logging services"  />

Jun Lu | 17 Jun 12:40 2005
Picon

Re: Log4J manual Chinese translation is online

Mark,
 
Thanks. I am working on translate Log4J site to Chinese now. It will be ready to let people see soon.
 
Jun

Mark Womack <mwomack <at> apache.org> wrote:
Jun Lu,

Thanks. I have added the links to the cvs. It will be part of the next
update to the web site.

-Mark

----- Original Message -----
From: "Jun Lu"
To:
Sent: Tuesday, June 14, 2005 3:30 AM
Subject: Log4J manual Chinese translation is online


> Hi,
>
> I have added 2 links of Chinese (Simplified and Traditional)
> translation of the short manual into "Translations to other languages"
> section of
> /jakarta-log4j/src/xdocs/documentation.xml.
>
> http://www.jaxwiki.org/zh/project/logging.apache.org/log4j/docs/manual.html
> http://www.jaxwiki.org/hk/project/logging.apache.org/log4j/docs/manual.html
>
> Please commit the changes in to CVS.
>
> Thanks.
>
> Best Regards.
>
> Jun Lu
>
>
>


--------------------------------------------------------------------------------


>
>
>
>
> Ceki Gulcu
> Yoav Shapira
>
>
>
>
>
>
>
>

With the exception of the complete manual, the following
> documentation is included with the standard log4j distribution
> and also browsable online:
>


>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

The following organisations offer log4j-related consultancy
> and training services. Their inclusion on this page does
> not imply endorsement by the Apache Software Foundation.
>


>
>
>
>
>
>

If you would like your log4j-related article or service
> to be listed here, then please send a note to the >
> href="mailto:log4j-user <at> logging.apache.org">log4j-user <at> logging.apache.org

> list.
>


>
>
>
>
>
>


Mark Womack | 20 Jun 20:06 2005
Picon

[VOTE] LS PMC Acceptance of Release: log4j 1.2.11

The log4j committers, having voted to release version 1.2.11 of log4j,
hereby request approval from the LS PMC to release it as an official release
of the LS Project.

The images are available for review at:

http://people.apache.org/~mwomack/log4j-1.2.11

I am +1 for acceptance and release.

-Mark

Curt Arnold | 20 Jun 21:35 2005
Picon

Re: [VOTE] LS PMC Acceptance of Release: log4j 1.2.11

+1

On Jun 20, 2005, at 1:06 PM, Mark Womack wrote:

> The log4j committers, having voted to release version 1.2.11 of log4j,
> hereby request approval from the LS PMC to release it as an  
> official release
> of the LS Project.
>
> The images are available for review at:
>
> http://people.apache.org/~mwomack/log4j-1.2.11
>
> I am +1 for acceptance and release.
>
> -Mark
>
>


Gmane