logging-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r821586 - in /websites/staging/loggingtest/trunk/content: ./ css/site.css guidelines.html
Date Wed, 13 Jun 2012 12:44:39 GMT
Author: buildbot
Date: Wed Jun 13 12:44:38 2012
New Revision: 821586

Log:
Staging update by buildbot for loggingtest

Modified:
    websites/staging/loggingtest/trunk/content/   (props changed)
    websites/staging/loggingtest/trunk/content/css/site.css
    websites/staging/loggingtest/trunk/content/guidelines.html

Propchange: websites/staging/loggingtest/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jun 13 12:44:38 2012
@@ -1 +1 @@
-1349806
+1349807

Modified: websites/staging/loggingtest/trunk/content/css/site.css
==============================================================================
--- websites/staging/loggingtest/trunk/content/css/site.css (original)
+++ websites/staging/loggingtest/trunk/content/css/site.css Wed Jun 13 12:44:38 2012
@@ -28,6 +28,8 @@ limitations under the License.
 .content h3,
 .content h4 { margin-bottom: 10px; }
 
+.content h3 { margin-top: 20px; }
+
 blockquote { margin-top: 20px; font-weight: normal; }
 blockquote p { margin-bottom: 12px; font-size: 14px; text-align: justify; }
 blockquote ul { margin-left: 50px; font-size: 14px; }

Modified: websites/staging/loggingtest/trunk/content/guidelines.html
==============================================================================
--- websites/staging/loggingtest/trunk/content/guidelines.html (original)
+++ websites/staging/loggingtest/trunk/content/guidelines.html Wed Jun 13 12:44:38 2012
@@ -80,29 +80,17 @@
 
 <p>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.</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 "foundation <span class="caps">FAQ</span>":
http://www.apache.org/foundation/faq.html explains the operation and background of the foundation.</p>
+<p>The Logging Services is a project of the <a href="http://www.apache.org/foundation/"
class="external">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"
class="external">foundation <span class="caps">FAQ</span></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>
+<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" class="external">Incubator
project</a> for more information on how Apache projects operate.</p>
 
 <h2>Roles and Responsibilities</h2>
 
-<p>Apache projects define a set of roles with associated rights and responsibilities.
These roles govern what tasks an individual may perform within the project. The roles are
defined in the following sections</p>
-
-<ul>
-<li><a href="#Users">Users</a></li>
-<li><a href="#Developers">Developers</a></li>
-<li><a href="#Committers">Committers</a></li>
-<li><a href="#Project Management Committee"> Project Management Committee (PMC)</a></li>
-</ul>
+<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.</p>
 
 <h3>Users</h3>
 
-<p>The most important participants in the project are people who use our software.
The majority of our developers start out as users and guide their development efforts from
the user&#39;s perspective.</p>
+<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>
 
@@ -112,23 +100,23 @@
 
 <h3>Committers</h3>
 
-<p>The project&#39;s Committers are responsible for the project&#39;s technical
management. All committers have write access to the project&#39;s source repositories.
Committers may cast binding votes on any technical discussion regarding the project.</p>
+<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 <span class="caps">PMC </span>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 <span class="caps">PMC.</span>
Such reinstatement is subject to lazy consensus of active <span class="caps">PMC </span>members.</p>
 
 <p>Commit access can be revoked by a unanimous vote of all the active <span class="caps">PMC
</span>members (except the committer in question if they are also a <span class="caps">PMC
</span>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
<span class="caps">FAQ</span></a> which provides more details on the requirements
for Committers.</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"
class="external">Committer <span class="caps">FAQ</span></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 <span class="caps">PMC.</span> 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>Project Management Committee</h3>
 
-<p>The Project Management Committee (PMC) for Apache Logging Services was created by
a <a href="charter.html">resolution</a> of the board of the Apache Software Foundation
on 18<sup>th</sup> November 2002. The <span class="caps">PMC </span>is
responsible to the board and the <span class="caps">ASF </span>for the management
and oversight of the Apache Logging Services codebase. The responsibilities of the <span
class="caps">PMC </span>include</p>
+<p>The Project Management Committee (PMC) for Apache Logging Services was created by
a <a href="http://charter.html">resolution</a> of the board of the Apache Software
Foundation on 18<sup>th</sup> November 2002. The <span class="caps">PMC
</span>is responsible to the board and the <span class="caps">ASF </span>for
the management and oversight of the Apache Logging Services codebase. The responsibilities
of the <span class="caps">PMC </span>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 <span class="caps">PMC</span></li>
-<li>Maintaining the project&#39;s shared resources, including the codebase repository,
mailing lists, websites.</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 <span class="caps">PMC </span>members and committers</li>
@@ -137,7 +125,7 @@
 
 <p>Membership of the <span class="caps">PMC </span>is by invitation only
and must be approved by a lazy consensus of active <span class="caps">PMC </span>members.
A <span class="caps">PMC </span>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 <span class="caps">PMC.</span> Such reinstatement
is subject to lazy consensus of the active <span class="caps">PMC </span>members.
Membership of the <span class="caps">PMC </span>can be revoked by an unanimous
vote of all the active <span class="caps">PMC </span>members other than the member
in question.</p>
 
-<p>The chair of the <span class="caps">PMC </span>is appointed by the <span
class="caps">ASF </span>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 <span
class="caps">PMC.</span> The chair reports to the board quarterly on developments
within the Logging Services project. The <span class="caps">PMC </span>may consider
the position of <span class="caps">PMC </span>chair annually and if supported
by 2/3 Majority may recommend a new chair to the board. Ultimately, however, it is the board&#39;s
responsibility who it chooses to appoint as the <span class="caps">PMC </span>chair.</p>
+<p>The chair of the <span class="caps">PMC </span>is appointed by the <span
class="caps">ASF </span>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 <span
class="caps">PMC.</span> The chair reports to the board quarterly on developments
within the Logging Services project. The <span class="caps">PMC </span>may consider
the position of <span class="caps">PMC </span>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 <span class="caps">PMC </span>chair.</p>
 
 <h3>Decision making</h3>
 
@@ -157,33 +145,7 @@
 
 <p>These are the types of approvals that can be sought. Different actions require different
types of approvals.</p>
 
-<table class="table table-bordered">
-	<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&nbsp;Consensus</strong></td>
-		<td>Lazy consensus requires 3 binding +1 votes and no binding vetoes.</td>
-	</tr>
-	<tr>
-		<td><strong>Lazy&nbsp;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&nbsp;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&nbsp;Majority</strong></td>
-		<td>Some actions require a 2/3 majority of active committers or <span class="caps">PMC
</span>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<br />
-			threshold is designed to ensure such changes are strongly supported. To pass this vote
requires at least 2/3 of<br />
-			binding vote holders to vote +1</td>
-	</tr>
-</table>
+<table class="table table-bordered" cellspacing="0"><tr><th>Consensus</th><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><th>Lazy&nbsp;Consensus</th><td>Lazy
consensus requires 3 binding +1 votes and no binding vetoes.</td></tr><tr><th>Lazy&nbsp;Majority</th><td>A
lazy majority vote requires 3 binding +1 votes and more binding +1 votes that -1 votes.</td></tr><tr><th>Lazy&nbsp;Approval</th><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><th>2/3&nbsp;Majority</th><td>Some
actions require a 2/3 majority of active committers or <span class="caps">PMC </span>members
to pass. Such actions typically affect the foundation of the project (e.g. ado
 pting 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</h3>
 
@@ -204,8 +166,7 @@
 	</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>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>
@@ -217,21 +178,13 @@
 	</tr>
 	<tr>
 		<td><strong>Product Release</strong></td>
-		<td>
-			When a release of one of the sub-project&#39;s products is ready, a vote is required
to accept the release <br />
-			as an official release of the Logging Services project.<br />
-			This step ensures the overall supervision by the Logging Services <span class="caps">PMC
</span>over its sub-projects.<br />
-		</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. This step ensures
the overall supervision by the Logging Services <span class="caps">PMC </span>over
its sub-projects.</td>
 		<td>Lazy Majority</td>
 		<td><b>Active <span class="caps">PMC </span>members</b></td>
 	</tr>
 	<tr>
 		<td><strong>Adoption of New Codebase</strong></td>
-		<td>
-			When the codebase for an existing, released product is to be replaced with an alternative
codebase. If such a<br />
-				vote fails to gain approval, the existing code base will continue.<br />
-			This also covers the creation of new sub-projects within the project<br />
-		</td>
+		<td>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.</td>
 		<td>2/3 majority</td>
 		<td>Active <span class="caps">PMC </span>members</td>
 	</tr>
@@ -243,10 +196,7 @@
 	</tr>
 	<tr>
 		<td><strong>New Committer</strong></td>
-		<td>
-			When a new committer is proposed for a sub-project.<br />
-			The <span class="caps">PMC </span>must be informed of the result of the sub-project&#39;s
vote.<br />
-		</td>
+		<td>When a new committer is proposed for a sub-project.The <span class="caps">PMC
</span>must be informed of the result of the sub-project's vote.</td>
 		<td>Lazy consensus</td>
 		<td>Active committers of the relevant sub-project</td>
 	</tr>
@@ -258,19 +208,15 @@
 	</tr>
 	<tr>
 		<td><strong>Committer Removal</strong></td>
-		<td>
-			When removal of commit privileges is sought.<br />
-			<b>Note: </b> Such actions will also be referred to the <span class="caps">ASF
</span>board by the <span class="caps">PMC </span>chair.<br />
-		</td>
+		<td>When removal of commit privileges is sought.<br />
+			<strong>Note:</strong> Such actions will also be referred to the <span
class="caps">ASF </span>board by the <span class="caps">PMC </span>chair.</td>
 		<td>Consensus</td>
 		<td>Active <span class="caps">PMC </span>members (excluding the committer
in question if a member of the <span class="caps">PMC</span>).</td>
 	</tr>
 	<tr>
 		<td><strong><span class="caps">PMC</span> Member Removal</strong></td>
-		<td>
-			When removal of a <span class="caps">PMC </span>member is sought.<br />
-			<b>Note: </b> Such actions will also be referred to the <span class="caps">ASF
</span>board by the <span class="caps">PMC </span>chair<br />
-		</td>
+		<td>When removal of a <span class="caps">PMC </span>member is sought.<br
/>
+			<strong>Note:</strong> Such actions will also be referred to the <span
class="caps">ASF </span>board by the <span class="caps">PMC </span>chair.</td>
 		<td>Consensus</td>
 		<td>Active <span class="caps">PMC </span>members (excluding the member
in question).</td>
 	</tr>
@@ -282,7 +228,7 @@
 
 			</div>
 			<div class="footer">
-				<p>Copyright &Acirc;&copy; 2012 <a href="http://www.apache.org" class="external">The
Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0"
class="external">Apache Software License, Version 2.0</a>. Please read our <a
href="http://privacy-policy.html">privacy policy</a>.</p>
+				<p>Copyright © 2012 <a href="http://www.apache.org" class="external">The
Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0"
class="external">Apache Software License, Version 2.0</a>. Please read our <a
href="http://privacy-policy.html">privacy policy</a>.</p>
 
 <p>Apache, Apache chainsaw, Apache log4cxx, Apache log4j, Apache log4net, Apache log4php
and the Apache feather logo are trademarks of The Apache Software Foundation.	Oracle and Java
are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.</p>
 



Mime
View raw message