@@ -202,7 +202,7 @@
</table>
<p>
This document defines the bylaws under which the Apache Ant project
operates. It defines the the roles and responsibilities of the
operates. It defines the roles and responsibilities of the
project, who may vote, how voting works, how conflicts are resolved,
etc.
</p>
@@ -234,7 +234,7 @@
<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 the following sections
within the project. The roles are defined in the following sections
</p>
<ul>
<li><a href="#Users">Users</a></li>
@@ -260,7 +260,7 @@
</p>
<p>
Users contribute to the Apache projects by providing feedback to
developers in the the form of bug reports and feature suggestions. As
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>
@@ -300,7 +300,7 @@
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 fromt he PMC. Such reinstatement is
reinstatement of commit access from t he PMC. Such reinstatement is
subject to lazy consensus of active PMC members.
</p>
<p>
@@ -314,7 +314,7 @@
which provides more details on the requirements for Committers
</p>
<p>
A committer who makes a sustained contibution to the project may be
A committer who makes a sustained contr ibution 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.
@@ -333,7 +333,7 @@
<a href="mission.html">resolution</a> of the board of the Apache
Software Foundation on 18<sup>th</sup> November 2002. The PMC is
responsible to the board and the ASF for the management and oversight
of the Apache Ant codebase. The responsibilites of the PMC include
of the Apache Ant codebase. The responsibiliti es of the PMC include
</p>
<ul>
<li>Deciding what is distributed as products of the Apache Ant project.
@@ -456,7 +456,7 @@
This is a negative vote. On issues where consensus is required,
this vote counts as a <strong>veto</strong>. All vetoes must
contain an explanation of why the veto is appropriate. Vetoes with
no explanation are void. IT may also be appropriate for a -1 vote
no explanation are void. It may also be appropriate for a -1 vote
to include an alternative course of action.
</td>
@@ -539,7 +539,7 @@
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 L azy consensus approval must be obtained.
lazy majority or l azy consensus approval must be obtained.
</td>
</tr>
@@ -555,7 +555,7 @@
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 stronly supported. To pass this vote requires at least 2/3 of
are strong ly supported. To pass this vote requires at least 2/3 of
binding vote holders to vote +1
</td>
@@ -573,14 +573,14 @@
<p>
A valid, binding veto cannot be overruled. If a veto is cast, it must be
accompanied by a valid reason explaining the reasons for the veto. The
validity of a veto, if challene ged, can be confirmed by anyone who has
validity of a veto, if challenged, can be confirmed by anyone who has
a binding vote. This does not necessarily signify agreement with the
veto - merely that the veto is valid.
</p>
<p>
If you disagree with a valid veto, you must lobby the person casting
the veto to withdraw their veto. If a veto is not withdrawn, the action
that has been vetoed b ust be reversed in a timely manner.
that has been vetoed m ust be reversed in a timely manner.
</p>
<br/>
<a name="Actions"></a>
@@ -593,7 +593,7 @@
</table>
<p>
This section describes the various actions which are undertaken within
the project, the correspnding approval required for that action and
the project, the correspo nding approval required for that action and
those who have binding votes over the action.
</p>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -631,7 +631,7 @@
<td colspan="1" rowspan="1"
valign="top" align="left">
Lazy Approval and then L azy consensus.
Lazy approval and then l azy consensus.
</td>
<td colspan="1" rowspan="1"
@@ -656,7 +656,7 @@
<td colspan="1" rowspan="1"
valign="top" align="left">
Lazy M ajority
Lazy m ajority
</td>
<td colspan="1" rowspan="1"
@@ -676,7 +676,7 @@
When a release of one of the project's products is ready, a vote is
required to accept the release as an official release of the
P roject.
p roject.
</td>
<td colspan="1" rowspan="1"
@@ -695,14 +695,14 @@
<tr>
<td colspan="1" rowspan="1"
valign="top" align="left">
<strong>Adoption of new c odebase</strong>
<strong>Adoption of New C odebase</strong>
</td>
<td colspan="1" rowspan="1"
valign="top" align="left">
When the codebase for an existing, released product is to be
replaced with an alternative codebase. Alternative codebases
may be developed in the project's source code reposity according
may be developed in the project's source code repositor y according
to the
<a href="http://incubator.apache.org/rules-for-revolutionaries.html">
Rules for Revolutionaries</a>. If such a vote fails to gain approval,
@@ -712,7 +712,7 @@
<td colspan="1" rowspan="1"
valign="top" align="left">
2/3 M ajority
2/3 m ajority
</td>
<td colspan="1" rowspan="1"
@@ -800,7 +800,7 @@
<tr>
<td colspan="1" rowspan="1"
valign="top" align="left">
<strong>PMC m ember Removal</strong>
<strong>PMC M ember Removal</strong>
</td>
<td colspan="1" rowspan="1"
valign="top" align="left">
Bruce Atherton