Return-Path: Delivered-To: apmail-logging-general-archive@www.apache.org Received: (qmail 26411 invoked from network); 17 Jun 2005 05:45:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Jun 2005 05:45:46 -0000 Received: (qmail 18264 invoked by uid 500); 17 Jun 2005 05:45:45 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 18214 invoked by uid 500); 17 Jun 2005 05:45:44 -0000 Mailing-List: contact general-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Logging General" List-Id: Delivered-To: mailing list general@logging.apache.org Received: (qmail 18198 invoked by uid 500); 17 Jun 2005 05:45:44 -0000 Delivered-To: apmail-logging-site-cvs@apache.org Received: (qmail 18192 invoked by uid 99); 17 Jun 2005 05:45:43 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from minotaur.apache.org (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 16 Jun 2005 22:45:39 -0700 Received: (qmail 26294 invoked by uid 1491); 17 Jun 2005 05:45:20 -0000 Date: 17 Jun 2005 05:45:20 -0000 Message-ID: <20050617054520.26293.qmail@minotaur.apache.org> From: mwomack@apache.org To: logging-site-cvs@apache.org Subject: cvs commit: logging-site/src/xdocs/stylesheets project.xml X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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 @@ -1,4 +1,4 @@ - + 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 @@ -1,4 +1,4 @@ - + 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 @@ -1,4 +1,4 @@ - + 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 @@ -1,416 +1,832 @@ - - - - - Ceki Gulcu - Bylaws of the Logging Services Project - - - - - - -

Bylaws

- -

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. -

- -

The Logging Services is a project of the - Apache Software - Foundation. The foundation holds the copyright on Apache - code including the code in the Logging Services codebase. The foundation FAQ - explains the operation and background of the foundation. -

- -

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 Incubator project for - more information on how Apache projects operate. -

- -

Roles and Responsibilities
How decisions are made

- -

Roles and Responsibilities

- -

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 -

- -

Users
Developers
Committers
- Project Management Committee (PMC) -

- -

Users

- -

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. -

- -

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. -

- - -

Developers

- - -

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. -

- -

Committers

- -

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. -

- -

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. -

- -

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).

- -

All Apache committers are required to have a signed - Contributor License Agreement (CLA) on file with the Apache - Software Foundation. There is a Committer - FAQ which provides more details on the requirements for - Committers.

- -

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. -

- -

Project Management Committee -

- -

The Project Management Committee (PMC) for Apache Logging Services was - created by a resolution of the board - of the Apache Software Foundation on 18^th 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 -

- -

Deciding what is distributed as products of the Apache Logging Services project. - In particular all releases must be approved by the PMC -
Maintaining the project's shared resources, including the codebase - repository, mailing lists, websites. -
Speaking on behalf of the project. -
Resolving license disputes regarding products of the project -
Nominating new PMC members and committers -
Maintaining these bylaws and other guidelines of the project -

- -

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. -

- -

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. -

- -

Decision Making - -

- -

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. -

- -

Voting

- -

Decisions regarding the project are made by votes on the - primary project mailing list (general@logging.apache.org). Where - necessary, PMC voting may take place on the private Logging - Services PMC mailing list. Votes are clearly indicated by - subject line starting with [VOTE] or [PMC-VOTE]. Votes may - contain multiple items for approval and these should be clearly - separated. Voting is carried out by replying to the vote - mail. Voting may take four flavours -

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

+1	"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" -
+0	This vote indicates a willingness for the action under - consideration to go ahead. The voter, however will not be able - to help. -
-0	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. -
-1	This is a negative vote. On issues where consensus is required, - this vote counts as a veto. 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. -

- -

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.

- -

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.

- -

Approvals

- -

These are the types of approvals that can be sought. Different - actions require different types of approvals

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

Consensus	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. -
Lazy Consensus	Lazy consensus requires 3 binding +1 votes and no binding vetoes.
- Lazy Majority -	A lazy majority vote requires 3 binding +1 votes and more binding +1 - votes that -1 votes. -
Lazy Approval	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. -
2/3 Majority	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 -

- -

Vetoes

- -

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. -

- -

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.

- -

Actions

- -

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. -

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

Action	Description	Approval	Binding Votes
Code Change	A change made to the codebase of a sub-project and committed - by a committer. This includes source code, documentation, - website content, etc. -	Lazy approval and then lazy consensus.	Active committers of the relevant sub-project.
Release Plan	Defines the timetable and actions for a release. The plan also - nominates a Release Manager.	Lazy majority	Active committers of the relevant sub-project
Product Release	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. - - This step ensures the overall supervision by the Logging - Services PMC over its sub-projects. -	Lazy Majority	Active PMC members
Adoption of New Codebase	- - 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. - - This also covers the creation of new sub-projects within - the project -	2/3 majority	Active PMC members
Modification of the Bylaws	Modification of this document	2/3 majority	Active PMC members
New Committer	When a new committer is proposed for a sub-project. - - The PMC must be informed of the result of the - sub-project's vote. - - -	Lazy consensus	Active committers of the relevant sub-project
New PMC Member	When a committer is proposed for the PMC	Lazy consensus	Active PMC members
Committer Removal	When removal of commit privileges is sought. - Note: Such actions will also be referred to the ASF - board by the PMC chair -	Consensus	Active PMC members (excluding the committer in question if a - member of the PMC). -
PMC Member Removal	When removal of a PMC member is sought. - Note: Such actions will also be referred to the - ASF board by the PMC chair -	Consensus	Active PMC members (excluding the member in question).

- - -

Voting Timeframes

- -

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.

- - - - + + + + + + + + + Ceki Gulcu + + Bylaws of the Logging Services Project + + + + + + + + + + + + + +

Bylaws

+ + + +

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. + +

+ + + +

The Logging Services is a project of the + + Apache Software + + Foundation. The foundation holds the copyright on Apache + + code including the code in the Logging Services codebase. The foundation FAQ + + explains the operation and background of the foundation. + +

+ + + +

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 Incubator project for + + more information on how Apache projects operate. + +

+ + + +

Roles and Responsibilities
How decisions are made

+ + + +

Roles and Responsibilities

+ + + +

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 + +

+ + + +

Users
Developers
Committers
+ + Project Management Committee (PMC) + +

+ + + +

Users

+ + + +

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. + +

+ + + +

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. + +

+ + + + + +

Developers

+ + + + + +

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. + +

+ + + +

Committers

+ + + +

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. + +

+ + + +

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. + +

+ + + +

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).

+ + + +

All Apache committers are required to have a signed + + Contributor License Agreement (CLA) on file with the Apache + + Software Foundation. There is a Committer + + FAQ which provides more details on the requirements for + + Committers.

+ + + +

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. + +

+ + + +

Project Management Committee + +

+ + + +

The Project Management Committee (PMC) for Apache Logging Services was + + created by a resolution of the board + + of the Apache Software Foundation on 18^th 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 + +

+ + + +

Deciding what is distributed as products of the Apache Logging Services project. + + In particular all releases must be approved by the PMC + +
Maintaining the project's shared resources, including the codebase + + repository, mailing lists, websites. + +
Speaking on behalf of the project. + +
Resolving license disputes regarding products of the project + +
Nominating new PMC members and committers + +
Maintaining these bylaws and other guidelines of the project + +

+ + + +

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. + +

+ + + +

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. + +

+ + + +

Decision Making + + + +

+ + + +

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. + +

+ + + +

Voting

+ + + +

Decisions regarding the project are made by votes on the + + primary project mailing list (general@logging.apache.org). Where + + necessary, PMC voting may take place on the private Logging + + Services PMC mailing list. Votes are clearly indicated by + + subject line starting with [VOTE] or [PMC-VOTE]. Votes may + + contain multiple items for approval and these should be clearly + + separated. Voting is carried out by replying to the vote + + mail. Voting may take four flavours + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+1	"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" + +
+0	This vote indicates a willingness for the action under + + consideration to go ahead. The voter, however will not be able + + to help. + +
-0	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. + +
-1	This is a negative vote. On issues where consensus is required, + + this vote counts as a veto. 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. + +

+ + + +

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.

+ + + +

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.

+ + + +

Approvals

+ + + +

These are the types of approvals that can be sought. Different + + actions require different types of approvals

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Consensus	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. + +
Lazy Consensus	Lazy consensus requires 3 binding +1 votes and no binding vetoes.
+ + Lazy Majority + +	A lazy majority vote requires 3 binding +1 votes and more binding +1 + + votes that -1 votes. + +
Lazy Approval	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. + +
2/3 Majority	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 + +

+ + + +

Vetoes

+ + + +

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. + +

+ + + +

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.

+ + + +

Actions

+ + + +

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. + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Action	Description	Approval	Binding Votes
Code Change	A change made to the codebase of a sub-project and committed + + by a committer. This includes source code, documentation, + + website content, etc. + +	Lazy approval and then lazy consensus.	Active committers of the relevant sub-project.
Release Plan	Defines the timetable and actions for a release. The plan also + + nominates a Release Manager.	Lazy majority	Active committers of the relevant sub-project
Product Release	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. + + + + This step ensures the overall supervision by the Logging + + Services PMC over its sub-projects. + +	Lazy Majority	Active PMC members
Adoption of New Codebase	+ + + + 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. + + + + This also covers the creation of new sub-projects within + + the project + +	2/3 majority	Active PMC members
Modification of the Bylaws	Modification of this document	2/3 majority	Active PMC members
New Committer	When a new committer is proposed for a sub-project. + + + + The PMC must be informed of the result of the + + sub-project's vote. + + + + + +	Lazy consensus	Active committers of the relevant sub-project
New PMC Member	When a committer is proposed for the PMC	Lazy consensus	Active PMC members
Committer Removal	When removal of commit privileges is sought. + + Note: Such actions will also be referred to the ASF + + board by the PMC chair + +	Consensus	Active PMC members (excluding the committer in question if a + + member of the PMC). + +
PMC Member Removal	When removal of a PMC member is sought. + + Note: Such actions will also be referred to the + + ASF board by the PMC chair + +	Consensus	Active PMC members (excluding the member in question).

+ + + + + +

Voting Timeframes

+ + + +

This is the project general mailing list. This is where ideas, + + suggestions, and comments are exchanged that deal with the + + overall Logging Services project. READ: This is + + not a place to ask technical questions related to log4j, 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 this + + page. + +

+ + + +

+ +

Log4cxx lists

+ + + +

log4cxx-user list

+ + + +

+ + Medium Traffic + + Subscribe + + Unsubscribe + + Guidelines + +
+ + Archives: + + MARC, + + GMANE, + + and apache.org mod_mbox, + + eyebrowse + +

+ + + +

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. + +

+ + + + + +

log4cxx-dev list

+ + + +

+ + Medium Traffic + + Subscribe + + Unsubscribe + + Guidelines + +
Archives: + + MARC, + + GMANE, + + and apache.org mod_mbox, + + eyebrowse

+ + + + + +

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. + +

+ + + + + +

+ +

Log4j lists

+ + + +

log4j-user list

+ + + +

+ + Medium Traffic + + Subscribe + + Unsubscribe + + Guidelines + +
Archives: + + MARC, + + GMANE, + + and apache.org mod_mbox, + + eyebrowse

+ + + + + +

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. + +

+ + + + + +

log4j-dev list

+ + + +

+ + Medium Traffic + + Subscribe + + Unsubscribe + + Guidelines + +
Archives: + + MARC, + + GMANE, + + and apache.org mod_mbox, + + eyebrowse

+ + + +

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. + +

+ + + + + +

+ +

Log4net lists

+ + + +

log4net-user list

+ + + +

+ + Medium Traffic + + Subscribe + + Unsubscribe + + Guidelines + +
Archives: + + MARC, + + GMANE, + + and apache.org mod_mbox, + + eyebrowse

+ + + +

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. + +

+ + + + + +

log4net-dev list

+ + + +

+ + Medium Traffic + + Subscribe + + Unsubscribe + + Guidelines + +
Archives: + + MARC + + and apache.org mod_mbox, + + eyebrowse

+ + + +

- -

  -   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.
  -

- - - - - - + + + + + + + + + Ceki Gulcu + + Mission Statement for the Logging Services Project + + + + + + + + + + + + + +

Mission statement

+ + + +

The mission of the Logging Services project is the development + + and maintanance of open-source software for tracing and logging of + + application behavior. + +

+ + + +

Board resolution

+ + + +

Logging Services project was created by the following resolution + + of the Board of Directors, dated 2003-12-17. + +

+ + + +

  +
  +   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.
  +
  +

+ + + + + + + + + + + + + 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 @@ -1,55 +1,109 @@ - - - - - Ceki Gulcu - Yoav Shapira - News and Status - - - - -

- -

11 January 2005 - log4cxx graduates from the incubator

- -

The Incubator PMC has voted to graduate log4cxx. log4cxx is - now a subproject of the Apache Logging Services Project. -

- -

22nd of January 2004 - Logging Services PMC has voted for the -adoption of log4cxx, log4net and log4php

- -

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. -

- -

We heartily welcome the new projects.

- -

17th December 2003 - Creation of the Logging Services Project

- -

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 - here. -

- -

-Got News? -

- -

If you would like to submit an item for posting to this page, send -an email with the subject [NEWS] to the general at logging dot -apache dot org mailing list.. -

- + + + + + + + + + Ceki Gulcu + + Yoav Shapira + + News and Status + + + + + + + + + +

+ + + +

11 January 2005 - log4cxx graduates from the incubator

+ + + +

The Incubator PMC has voted to graduate log4cxx. log4cxx is + + now a subproject of the Apache Logging Services Project. + +

+ + + +

22nd of January 2004 - Logging Services PMC has voted for the + +adoption of log4cxx, log4net and log4php

+ + + +

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. + +

+ + + +

We heartily welcome the new projects.

+ + + +

17th December 2003 - Creation of the Logging Services Project

+ + + +

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 + + here. + +

+ + + +

+ +Got News? + +

+ + + +

If you would like to submit an item for posting to this page, send + +an email with the subject [NEWS] to the general at logging dot + +apache dot org mailing list.. + +

+ +

+ + + \ 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 @@ -1,213 +1,418 @@ - - - - - Ceki Gulcu - Who we are - - - - - - - -

List of developers

- - -

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. -

- - - - - -

PMC members

Curt Arnold -
Curt is the current lead for the log4cxx project. He is also a - regular contributor to the log4j project. -
-
Nicko Cadell -
Nicko is the current lead for the log4net project.
-
Scott Deboy -
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. -
-

Ceki Gülcü - - - - - - -

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 The - complete log4j manual.

Jacob Kjome - -
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. :-) -
-
Yoav Shapira - - - - - -
- -
Yoav Shapira contributes numerous Apache and other open-source - projects: you can read more about him at - YoavShapira.com. -
-
-

Paul Smith - - - - -

- -

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.

Mark Womack - - - - - -

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.

- -

Active committers

- -

Jim Moore -

Jim is often seen answering tough question from log4j users.

- - -

Emeritus committers

- -

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.

- -

Mathias Bogaert - -
While not lurking on the serverside, Mathias - mends the log4j documentation.
-
James P. Cakalic -
Jim is the original author of the PatternLayout and the - NTEventLogAppender.
-

Paul Glezen - - - - - - - -

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.

Anders Kristensen - -
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.
-
Jon Skeet - -
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. -
-
Chris Taylor - - - - - - - - -

Chris is the author NTEventLogAppender. In around 1832, he - ported our previous GNU-make build system to, at the time little - known but promising, Apache - Ant.
-
-

- - - - - + + + + + + + + + Ceki Gulcu + + Who we are + + + + + + + + + + + + + + + +

List of developers

+ + + + + +

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. + +

+ + + + + + + + + + + +

PMC members

+ +

Curt Arnold + +
Curt is the current lead for the log4cxx project. He is also a + + regular contributor to the log4j project. + +
+ +
Nicko Cadell + +
Nicko is the current lead for the log4net project.
+ +
Scott Deboy + +
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. + +
+ +

Ceki Gülcü + + + + + + + + + + + + + +

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 The + + complete log4j manual.

+ +

Jacob Kjome + + + +
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. :-) + +
+ +

Yoav Shapira + + + + + + + + + + + +

+ + + +

Yoav Shapira contributes numerous Apache and other open-source + + projects: you can read more about him at + + YoavShapira.com. + +

+ +

Paul Smith + + + + + + + + + +

+ + + +

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.

+ +

Mark Womack + + + + + + + + + + + +

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.

+ +

+ + + +

Active committers

+ + + +

Jim Moore + +

Jim is often seen answering tough question from log4j users.

+ +

+ + + + + +

Emeritus committers

+ + + +

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.

+ + + +

Mathias Bogaert + + + +
While not lurking on the serverside, Mathias + + mends the log4j documentation.
+ +
James P. Cakalic + +
Jim is the original author of the PatternLayout and the + + NTEventLogAppender.
+ +

Paul Glezen + + + + + + + + + + + + + + + +

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.

+ +

Anders Kristensen + + + +
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.
+ +
Jon Skeet + + + +
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. + +
+ +

Chris Taylor + + + + + + + + + + + + + + + + + +

Chris is the author NTEventLogAppender. In around 1832, he + + ported our previous GNU-make build system to, at the time little + + known but promising, Apache + + Ant.

+ +

+ + + + + + + + + + + \ 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 @@ -1,44 +1,88 @@ - - - - Logging Services - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + Logging Services + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +