Author: carnold Date: Fri Jul 20 21:39:48 2007 New Revision: 558241 URL: http://svn.apache.org/viewvc?view=rev&rev=558241 Log: Initial comment of Maven generated LS content Added: logging/site/trunk/docs/catalog.html (with props) logging/site/trunk/docs/charter.html (with props) logging/site/trunk/docs/css/ logging/site/trunk/docs/css/maven-base.css (with props) logging/site/trunk/docs/css/maven-theme.css (with props) logging/site/trunk/docs/css/print.css (with props) logging/site/trunk/docs/css/site.css (with props) logging/site/trunk/docs/guidelines.html (with props) logging/site/trunk/docs/images/collapsed.gif (with props) logging/site/trunk/docs/images/expanded.gif (with props) logging/site/trunk/docs/images/external.png (with props) logging/site/trunk/docs/images/icon_error_sml.gif (with props) logging/site/trunk/docs/images/icon_info_sml.gif (with props) logging/site/trunk/docs/images/icon_success_sml.gif (with props) logging/site/trunk/docs/images/icon_warning_sml.gif (with props) logging/site/trunk/docs/images/logos/ logging/site/trunk/docs/images/logos/maven-feather.png (with props) logging/site/trunk/docs/images/newwindow.png (with props) logging/site/trunk/docs/license.html (with props) logging/site/trunk/docs/log4j/ logging/site/trunk/docs/log4j/2.0/ logging/site/trunk/docs/log4j/2.0/index.html (with props) logging/site/trunk/docs/log4j/companions/ logging/site/trunk/docs/log4j/companions/index.html (with props) logging/site/trunk/docs/log4j/index.html (with props) logging/site/trunk/docs/log4php/ logging/site/trunk/docs/log4php/index.html (with props) logging/site/trunk/docs/mail-lists.html (with props) logging/site/trunk/docs/maintenance.html (with props) logging/site/trunk/docs/news.html (with props) logging/site/trunk/docs/project-info.html (with props) logging/site/trunk/docs/site/.htaccess logging/site/trunk/docs/source-repository.html (with props) logging/site/trunk/docs/team-list.html (with props) Modified: logging/site/trunk/docs/index.html (contents, props changed) logging/site/trunk/docs/site/binindex.html (contents, props changed) logging/site/trunk/docs/site/bugreport.html (contents, props changed) Added: logging/site/trunk/docs/catalog.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/catalog.html?view=auto&rev=558241 ============================================================================== --- logging/site/trunk/docs/catalog.html (added) +++ logging/site/trunk/docs/catalog.html Fri Jul 20 21:39:48 2007 @@ -0,0 +1,544 @@ + + + + + + + + + + + + + + Apache Logging Services Project - + Catalog + + + + + + + + +
+ +
+
+
+ + + + + +

The following logging related projects and products are developed by other parties and are provided + as a public service. No endorsement of these projects and products should be implied.

+ +

log4j related products

+ +
+ + +
DatedFileAppender
+ +
DatedFileAppender works in the same manner as + the Tomcat FileLogger. Contrary to + DailyRollingFileAppender shipping with log4j, log + file names generated by DatedFileAppender always + contain today's date. While this distinction seems minor, it + means you can reliably copy, compress, remove or manipulate a + day's log file shortly after midnight. With the + DailyRollingFileAppender, a day's log file is not + renamed until the first message is logged some time after + midnight. +
+ + + +
+ JDBCAppender +
+ +
A powerful JDBCAppender by Danko Mannhaupt + who continues the work of Thomas Fenner. You might find + this JDBCAppender more suitable then the one that ships with + log4j 1.2. +
+ + + +
+ Just4log +
+ +
Just4Log is a library to enhance dynamically the + performance of various logging systems inside a java + application. Dynamically because the sourcecode in java is not + modified but rather the optimization occurs on the compiled + ByteCode files. +
+ + +
log4Ant
+ +
log4Ant includes a complete bridge to the Log4J logging systemfor a robust build monitoring system. + These Ant components let you capture, map, and send Ant log messages and stdio output through your Log4J installation. Contact contact@jware.info +
+ + +
log4j400
+ +
Log4J400 includes MessageQueue and DataQueue Appenders for + the AS/400 (aka IBM iSeries). +
+ + + +
log4j2db
+ +
This Project provides a set of EJBs to store Log4J events + (received via JMS appender) in a database. The main aim is to + provide a toolset for a centralized, data-center suitable + logging. +
+ + + +
log4jME
+ +
Log4jME, or log4j MiniEdition, is based on the + same code as log4j. However, as the name indicates the + mini-edition is much smaller. It offers the same client + interface such that code compiled for log4jME is + compatible with log4j standard edition. You can choose to + upgrade to log4j standard edition at any time by replacing + log4jME.jar with log4j.jar in your + classpath. At this time, log4jME is only available through + ASF Subversion repository in the Logging Services Sandbox. +
+ + + +
log4Unit
+ +
Log4Unit is a JUnit extension + combining JUnit with Log4J. The intention is to create test + protocols for JUnit. + +

JUnit is asymmetrical in the sense that it focusses on the + documentation of test failures and errors. Successful + execution of a test case is not further documented. In order + to obtain a test protocol that documents the initial settings, + the test case execution and its results, a logging component + is required. Log4J as the current de facto standard is + selected for this extension. +

+
+ + + +
Log4Web (commercial)
+ +
Log4Web is a J2EE web application, designed to web-enable + system log files that have been generated by log4j. +
+ + + +
+ Log Tag +
+
A custom log tag library from the Jakarta + Taglibs project.
+ + + +
LogWeb
+ +
LogWeb is a web interface for configuring log4j at runtime + within a servlet container. Every log4j feature of is + configurable through this interface. +
+ + + + +
+ SNMPTrapAppender +
+ +
An appender to send formatted logging event strings to a + specified managment host (typically, a MLM of some sort, but + could also be an SNMP management console) in the form of an + SNMP trap. +
+ + + +
XpoLog +
+ +
Log view and analysis application which enables web + browsing and analysis over logs. +
+ + + +
+
+

Other Logging Frameworks

+
+ +
log4php
+ +
Log4Php is a PHP port of log4j framework. It supports xml configuration, + logging to files, stdout/err, syslog, socket, configurable + output layouts and logging levels.
+ + +
log4c
+ +
ANSI C functions and macros for flexible logging to files + and other destinations. It is modeled after log4j. It follows + the log4j API within the limits of reason. Intended for use in time-space + critical environments.
+ + + +
log4cpp
+
A library of C++ classes for flexible logging to files, + syslog, IDSA and other destinations modeled after log4j.
+ + + +
log4cplus
+
Log4cplus is a simple to use C++ logging API providing + thread-safe, flexible, and arbitrarily granular control over + log management and configuration. It is modeled after the Java + log4j API.
+ + + +
log4E
+ +
The Goanna project (Eiffel Web Services) now includes + log4E, a complete port of log4j. +
+ + +
Log::Log4perl
+ +
Log::Log4perl is a Perl port of log4j by Kevin Goess and + Mike Schilli. The authors made sure that their port was as + close as possible to the original implementation. Even the + configuration files are similar! The project is still being + enhanced, however the current release is stable and has been + released to CPAN. +
+ + +
log4LS
+ +
Log4LS is a LotusScript library package and is used to get + logging statements to a Domino database, sent by mail or + written to a file. It is modeled after Jakarta log4j. +
+ + +
log4py
+ +
Log4Py is a python logging module similar to log4j. It + supports logging to files or to stdout/stderr, variable + log-levels, configurable output formats and configuration via + configuration files. +
+ + + +
log4p
+
Another Python translation of log4j. This project no + longer seems to be maintained.
+ + + +
log4plsql
+ +
Log4plsql is a Oracle PL/SQL logging module similar to + log4j. It supports logging out-off transaction. It is useful + for logging, benchmarking and monitoring PL/SQL applications. +
+ + + +
qmmslog
+ +
Qmmslog is a port of log4j to the Qt/C++ platform. +
+ + +
log4r
+
A Powerful Logger for Ruby. +

Log4r features an extremely flexible logging library for + Ruby. Killer features include a heiarchial logging system + of any number of levels, logger inheritance, multiple + output destinations, tracing, custom formatting and more. + Log4r was inspired by log4j. Log4r provides the defining + features of log4j and some of its own features that just + might make log4j users envious.

+
+ + +
+ +

If you would like your software to be listed here, then send a note to the general@logging.apache.org + list.

+ +
+ + + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/catalog.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: logging/site/trunk/docs/charter.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/charter.html?view=auto&rev=558241 ============================================================================== --- logging/site/trunk/docs/charter.html (added) +++ logging/site/trunk/docs/charter.html Fri Jul 20 21:39:48 2007 @@ -0,0 +1,339 @@ + + + + + + + + + + + + + + Apache Logging Services Project - + Charter of the Logging Services PMC + + + + + + + +
+ +
+
+
+ + + +

Charter 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. +
+ + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/charter.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: logging/site/trunk/docs/css/maven-base.css URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/css/maven-base.css?view=auto&rev=558241 ============================================================================== --- logging/site/trunk/docs/css/maven-base.css (added) +++ logging/site/trunk/docs/css/maven-base.css Fri Jul 20 21:39:48 2007 @@ -0,0 +1,148 @@ +body { + margin: 0px; + padding: 0px; +} +img { + border:none; +} +table { + padding:0px; + width: 100%; + margin-left: -2px; + margin-right: -2px; +} +acronym { + cursor: help; + border-bottom: 1px dotted #feb; +} +table.bodyTable th, table.bodyTable td { + padding: 2px 4px 2px 4px; + vertical-align: top; +} +div.clear{ + clear:both; + visibility: hidden; +} +div.clear hr{ + display: none; +} +#bannerLeft, #bannerRight { + font-size: xx-large; + font-weight: bold; +} +#bannerLeft img, #bannerRight img { + margin: 0px; +} +.xleft, #bannerLeft img { + float:left; + text-shadow: #7CFC00; +} +.xright, #bannerRight img { + float:right; + text-shadow: #7CFC00; +} +#banner { + padding: 0px; +} +#banner img { + border: none; +} +#breadcrumbs { + padding: 3px 10px 3px 10px; +} +#leftColumn { + width: 170px; + float:left; + overflow: auto; +} +#bodyColumn { + margin-right: 1.5em; + margin-left: 197px; +} +#legend { + padding: 8px 0 8px 0; +} +#navcolumn { + padding: 8px 4px 0 8px; +} +#navcolumn h5 { + margin: 0; + padding: 0; + font-size: small; +} +#navcolumn ul { + margin: 0; + padding: 0; + font-size: small; +} +#navcolumn li { + list-style-type: none; + background-image: none; + background-repeat: no-repeat; + background-position: 0 0.4em; + padding-left: 16px; + list-style-position: outside; + line-height: 1.2em; + font-size: smaller; +} +#navcolumn li.expanded { + background-image: url(../images/expanded.gif); +} +#navcolumn li.collapsed { + background-image: url(../images/collapsed.gif); +} +#poweredBy { + text-align: center; +} +#navcolumn img { + margin-top: 10px; + margin-bottom: 3px; +} +#poweredBy img { + display:block; + margin: 20px 0 20px 17px; + border: 1px solid black; + width: 90px; + height: 30px; +} +#search img { + margin: 0px; + display: block; +} +#search #q, #search #btnG { + border: 1px solid #999; + margin-bottom:10px; +} +#search form { + margin: 0px; +} +#lastPublished { + font-size: x-small; +} +.navSection { + margin-bottom: 2px; + padding: 8px; +} +.navSectionHead { + font-weight: bold; + font-size: x-small; +} +.section { + padding: 4px; +} +#footer { + padding: 3px 10px 3px 10px; + font-size: x-small; +} +#breadcrumbs { + font-size: x-small; + margin: 0pt; +} +.source { + padding: 12px; + margin: 1em 7px 1em 7px; +} +.source pre { + margin: 0px; + padding: 0px; +} Propchange: logging/site/trunk/docs/css/maven-base.css ------------------------------------------------------------------------------ svn:mime-type = text/css Added: logging/site/trunk/docs/css/maven-theme.css URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/css/maven-theme.css?view=auto&rev=558241 ============================================================================== --- logging/site/trunk/docs/css/maven-theme.css (added) +++ logging/site/trunk/docs/css/maven-theme.css Fri Jul 20 21:39:48 2007 @@ -0,0 +1,141 @@ +body { + padding: 0px 0px 10px 0px; +} +body, td, select, input, li{ + font-family: Verdana, Helvetica, Arial, sans-serif; + font-size: 13px; +} +code{ + font-family: Courier, monospace; + font-size: 13px; +} +a { + text-decoration: none; +} +a:link { + color:#36a; +} +a:visited { + color:#47a; +} +a:active, a:hover { + color:#69c; +} +#legend li.externalLink { + background: url(../images/external.png) left top no-repeat; + padding-left: 18px; +} +a.externalLink, a.externalLink:link, a.externalLink:visited, a.externalLink:active, a.externalLink:hover { + background: url(../images/external.png) right center no-repeat; + padding-right: 18px; +} +#legend li.newWindow { + background: url(../images/newwindow.png) left top no-repeat; + padding-left: 18px; +} +a.newWindow, a.newWindow:link, a.newWindow:visited, a.newWindow:active, a.newWindow:hover { + background: url(../images/newwindow.png) right center no-repeat; + padding-right: 18px; +} +h2 { + padding: 4px 4px 4px 6px; + border: 1px solid #999; + color: #900; + background-color: #ddd; + font-weight:900; + font-size: x-large; +} +h3 { + padding: 4px 4px 4px 6px; + border: 1px solid #aaa; + color: #900; + background-color: #eee; + font-weight: normal; + font-size: large; +} +h4 { + padding: 4px 4px 4px 6px; + border: 1px solid #bbb; + color: #900; + background-color: #fff; + font-weight: normal; + font-size: large; +} +h5 { + padding: 4px 4px 4px 6px; + color: #900; + font-size: normal; +} +p { + line-height: 1.3em; + font-size: small; +} +#breadcrumbs { + border-top: 1px solid #aaa; + border-bottom: 1px solid #aaa; + background-color: #ccc; +} +#leftColumn { + margin: 10px 0 0 5px; + border: 1px solid #999; + background-color: #eee; +} +#navcolumn h5 { + font-size: smaller; + border-bottom: 1px solid #aaaaaa; + padding-top: 2px; + color: #000; +} + +table.bodyTable th { + color: white; + background-color: #bbb; + text-align: left; + font-weight: bold; +} + +table.bodyTable th, table.bodyTable td { + font-size: 1em; +} + +table.bodyTable tr.a { + background-color: #ddd; +} + +table.bodyTable tr.b { + background-color: #eee; +} + +.source { + border: 1px solid #999; +} +dl { + padding: 4px 4px 4px 6px; + border: 1px solid #aaa; + background-color: #ffc; +} +dt { + color: #900; +} +#organizationLogo img, #projectLogo img, #projectLogo span{ + margin: 8px; +} +#banner { + border-bottom: 1px solid #fff; +} +.errormark, .warningmark, .donemark, .infomark { + background: url(../images/icon_error_sml.gif) no-repeat; +} + +.warningmark { + background-image: url(../images/icon_warning_sml.gif); +} + +.donemark { + background-image: url(../images/icon_success_sml.gif); +} + +.infomark { + background-image: url(../images/icon_info_sml.gif); +} + Propchange: logging/site/trunk/docs/css/maven-theme.css ------------------------------------------------------------------------------ svn:mime-type = text/css Added: logging/site/trunk/docs/css/print.css URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/css/print.css?view=auto&rev=558241 ============================================================================== --- logging/site/trunk/docs/css/print.css (added) +++ logging/site/trunk/docs/css/print.css Fri Jul 20 21:39:48 2007 @@ -0,0 +1,7 @@ +#banner, #footer, #leftcol, #breadcrumbs, .docs #toc, .docs .courtesylinks, #leftColumn, #navColumn { + display: none !important; +} +#bodyColumn, body.docs div.docs { + margin: 0 !important; + border: none !important +} Propchange: logging/site/trunk/docs/css/print.css ------------------------------------------------------------------------------ svn:mime-type = text/css Added: logging/site/trunk/docs/css/site.css URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/css/site.css?view=auto&rev=558241 ============================================================================== --- logging/site/trunk/docs/css/site.css (added) +++ logging/site/trunk/docs/css/site.css Fri Jul 20 21:39:48 2007 @@ -0,0 +1 @@ + Propchange: logging/site/trunk/docs/css/site.css ------------------------------------------------------------------------------ svn:mime-type = text/css Added: logging/site/trunk/docs/guidelines.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/guidelines.html?view=auto&rev=558241 ============================================================================== --- logging/site/trunk/docs/guidelines.html (added) +++ logging/site/trunk/docs/guidelines.html Fri Jul 20 21:39:48 2007 @@ -0,0 +1,1092 @@ + + + + + + + + + + + + + + Apache Logging Services Project - + + Guidelines of the Logging Services Project + + + + + + + + +
+ +
+
+
+ + + + + + + + + + + + + + + + +

Guidelines

+ + + +

This document defines the guidelines 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 

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

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

+ + + + + + + + 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" + +
+0This vote indicates a willingness for the action under + + consideration to go ahead. The voter, however will not be able + + to help. + +
-0This 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. + +
-1This 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

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConsensusFor 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 ConsensusLazy 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 ApprovalAn 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 MajoritySome 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. + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ActionDescriptionApprovalBinding Votes
Code ChangeA 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 majorityActive 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 MajorityActive 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 majorityActive PMC members
Modification of the BylawsModification of this document2/3 majorityActive PMC members
New CommitterWhen a new committer is proposed for a sub-project. + + + +

The PMC must be informed of the result of the + + sub-project's vote. + +

+ + + +
Lazy consensusActive committers of the relevant sub-project
New PMC MemberWhen a committer is proposed for the PMCLazy consensusActive 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

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

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

+ + + + + + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/guidelines.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: logging/site/trunk/docs/images/collapsed.gif URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/collapsed.gif?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/collapsed.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: logging/site/trunk/docs/images/expanded.gif URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/expanded.gif?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/expanded.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: logging/site/trunk/docs/images/external.png URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/external.png?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/external.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: logging/site/trunk/docs/images/icon_error_sml.gif URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/icon_error_sml.gif?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/icon_error_sml.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: logging/site/trunk/docs/images/icon_info_sml.gif URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/icon_info_sml.gif?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/icon_info_sml.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: logging/site/trunk/docs/images/icon_success_sml.gif URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/icon_success_sml.gif?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/icon_success_sml.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: logging/site/trunk/docs/images/icon_warning_sml.gif URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/icon_warning_sml.gif?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/icon_warning_sml.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: logging/site/trunk/docs/images/logos/maven-feather.png URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/logos/maven-feather.png?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/logos/maven-feather.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: logging/site/trunk/docs/images/newwindow.png URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/images/newwindow.png?view=auto&rev=558241 ============================================================================== Binary file - no diff available. Propchange: logging/site/trunk/docs/images/newwindow.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Modified: logging/site/trunk/docs/index.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/index.html?view=diff&rev=558241&r1=558240&r2=558241 ============================================================================== --- logging/site/trunk/docs/index.html (original) +++ logging/site/trunk/docs/index.html Fri Jul 20 21:39:48 2007 @@ -1,171 +1,289 @@ - - - - - - - + + + + + + + + + + + + + + Apache Logging Services Project - + Welcome to Apache Logging Services + + + + + + + +
+ +
+
+
- - - - - - - - - - - - - - - - - - - - - - Logging Services - Welcome - - - - - - - - - - - - -
-
- -

Welcome to Logging Services Project @ Apache

-

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

-

The Logging Services project is intended to provide - cross-language logging services for purposes of application - debugging and auditing. -

-

We should also mention that thanks to the relentless efforts of - many developers, we have a basic level of interoperability between the following projects: -

-
    -
  • Log4Cxx (c++)
  • -
  • Log4j
  • -
  • Log4Net
  • -
  • Log4Perl
  • -
  • Log4PHP
  • -
  • Log4PLSQL
  • -
  • JDK1.4's util.logging framework
  • - -
-

There is still much work ahead bringing in the various projects to - work together within the Logging Services Project. The process is - likely to take a little while. In the mean time, we will continue - to do what we like best, that is developing open source software. -

-

- This is a project of the Apache Software Foundation (ASF). Like all - Apache projects, we encourage a collaborative, consensus-based - development process. We offer an open and pragmatic software - license, and we strive to create software of the highest - quality. The ASF is organized into several projects, which like - Logging Services project may contain multiple sub-projects. For more - about these projects, visit the ASF Project - Page. -

- - -
- - - - - -
- Copyright © 1999-2006, Apache Software Foundation -
- - - - - -
- - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - +

Welcome to Apache Logging Services

+

The Apache Logging Services Project creates and maintains open-source software related + to the logging of application behavior and released at no charge + to the public.

+ +

The products of the Apache Logging Services Project included three logging frameworks: log4j + for Java, log4cxx for C++ and log4net for the Microsoft .NET framework + and a log viewer and analysis tool: Chainsaw.

+

Apache Logging Services is also sponsoring the incubation of log4php.

+
+
+ +
+ + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/index.html ('svn:eol-style' removed) Propchange: logging/site/trunk/docs/index.html ------------------------------------------------------------------------------ svn:mime-type = text/html