This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 6b03cd655 Automatic Site Publish by Buildbot
6b03cd655 is described below
commit 6b03cd655a4a234f4339cfa2ca0f1191ab8735a8
Author: buildbot <us...@infra.apache.org>
AuthorDate: Fri Sep 27 19:24:51 2024 +0000
Automatic Site Publish by Buildbot
---
output/contributor/bylaws.html | 495 +++++++++---------------------
output/contributor/consensusBuilding.html | 2 +-
output/contributor/lazyConsensus.html | 192 ------------
output/contributor/voting.html | 226 --------------
output/contributors-guide/index.html | 2 -
output/feed.xml | 4 +-
output/governance/lazyConsensus.html | 11 -
output/governance/voting.html | 11 -
output/redirects.json | 2 +-
9 files changed, 157 insertions(+), 788 deletions(-)
diff --git a/output/contributor/bylaws.html b/output/contributor/bylaws.html
index 51e66b2eb..4f52d77fb 100644
--- a/output/contributor/bylaws.html
+++ b/output/contributor/bylaws.html
@@ -115,148 +115,133 @@
<h1 class="title">Bylaws</h1>
- <p>This is version 3 of the bylaws. Community work actively
continues on the
-bylaws, and so key segments of them are subject to change.</p>
+ <p>This is version 4 of our project’s bylaws and is subject to
change.</p>
<h1 id="introduction">Introduction</h1>
-<p>This document defines the bylaws under which the Apache Accumulo project
-operates. It defines the roles and responsibilities of the project, who may
-vote, how voting works, how conflicts are resolved, etc.</p>
+<p>Accumulo is a project of the <a
href="https://www.apache.org/foundation";>Apache Software Foundation (ASF)</a>.
+More details about the Foundation can be found on its pages.</p>
-<p>Accumulo is a project of the <a
href="https://www.apache.org/foundation";>Apache Software Foundation</a>. The
-foundation holds the copyright on Apache code including the code in the
-Accumulo codebase. The <a
href="https://www.apache.org/foundation/faq";>foundation FAQ</a> explains the
operation
-and background of the foundation.</p>
-
-<p>Accumulo 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
+<p>Accumulo is a typical ASF project, operating under a set of principles known
+collectively as <a href="https://www.apache.org/theapacheway";>The Apache
Way</a>. If you are new to ASF
development, please refer to the <a
href="https://incubator.apache.org";>Incubator project</a> for more
-information on how Apache projects operate. Terms used at the ASF are defined
-in the <a href="https://www.apache.org/foundation/glossary";>ASF
glossary</a>.</p>
+information on how ASF projects operate.</p>
+
+<p>Terms used at the ASF are defined in the <a
href="https://www.apache.org/foundation/glossary";>ASF glossary</a>.</p>
+
+<p>While this project generally follows standard procedures used by most
projects
+across the ASF, the purpose of this document is to define bylaws that apply
+specifically to the Accumulo project. These bylaws establish ground rules for
+handling situations where either there is no standard procedure within the ASF,
+or where we’ve chosen to diverge from those procedures. If a situation is not
+covered by these bylaws, then it is assumed that we will follow standard
+procedures established by the Foundation. If standard procedures do not exist,
+then a decision should be made following a discussion on an appropriate mailing
+list for the project.</p>
<h1 id="roles-and-responsibilities">Roles and Responsibilities</h1>
-<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>
+<p>The roles in this project, and their associated responsibilities, are the
+standard roles defined within the Foundation’s <a
href="https://www.apache.org/foundation/how-it-works";>own documents</a>.</p>
-<h2 id="users">Users</h2>
+<p>This project establishes the following additional procedures for specific
+roles below.</p>
-<p>The most important participants in the project are people who use our
software.
-The majority of our contributors start out as users and guide their development
-efforts from the user’s perspective.</p>
+<h2 id="committers">Committers</h2>
-<p>Users contribute to the Apache projects by providing feedback to
contributors
-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>
+<p>The Committer role is defined by <a
href="https://www.apache.org/foundation/how-it-works";>the Foundation</a>.
Additional
+information can be found on the <a
href="https://www.apache.org/dev/committers";>Committers page</a>.</p>
-<h2 id="contributors">Contributors</h2>
+<p>Upon acceptance of an invitation to become a committer, it is the accepting
+committer’s responsibility to update their status on the Accumulo web page
+accordingly, and to make updates as needed.</p>
-<p>All of the volunteers who are contributing time, code, documentation, or
-resources to the Accumulo project are considered contributors. A contributor
-that makes sustained, welcome contributions to the project may be invited to
-become a committer, though the exact timing of such invitations depends on many
-factors.</p>
+<p>All committers should use their privileges carefully, and ask for help if
they
+are uncertain about the risks of any action.</p>
-<h2 id="committers">Committers</h2>
+<p>In order to maintain a low barrier to entry, and to encourage project growth
+and diversity of perspectives, it is the custom of the Accumulo project to also
+invite each committer to become a member of its Project Management Committee
+(PMC). However, this is not a requirement and the current PMC may elect to only
+invite a contributor to become a committer without inviting them to become a
+PMC member, depending on the circumstances. If invited to both, invitees may
+also decline the invitation to the PMC role and only accept the committer
role.</p>
+
+<h2 id="project-management-committee-pmc-member">Project Management Committee
(PMC) Member</h2>
-<p>The project’s committers are responsible for the project’s technical
-management. Committers have write access to the project’s code repositories and
-may cast binding votes on any technical discussion regarding Accumulo.
-Committer access is by invitation only and must be approved by consensus
-approval of the active PMC members. Upon acceptance of the invitation to become
-a committer, it is the accepting member’s responsibility to update their status
-on the Accumulo web page accordingly.</p>
-
-<p>A committer is considered emeritus, meaning inactive, by their own
declaration
-or by not reviewing patches or committing patches to the project for over six
-months. Emeritus members will be recognized by the PMC on the Accumulo web
-page, in honor of their past contributions. Emeritus members retain all voting
-and commit rights associated with their former designation and can move
-themselves out of emeritus status by sending an announcement of their return to
-the developer mailing list. It will be the returning member’s responsibility to
-update their status on the web page accordingly.</p>
-
-<p>An emeritus committer’s commit access may be disabled as part of routine
-security. Access shall not be removed without notifying the committer, and
-access shall be maintained if the committer wishes to leave it active. A
-committer’s commit access shall be reactivated upon the committer’s request to
-the PMC.</p>
-
-<p>All Apache committers are required to have a signed <a
href="https://www.apache.org/licenses/icla.txt";>Contributor License
-Agreement</a> (CLA) on file with the Apache Software Foundation. Under the
-terms of the CLA that all committers must sign, a committer’s primary
-responsibility is to ensure that all code committed to Apache Accumulo is
-licensed appropriately and meets those criteria set forth in the CLA (including
-both original works and patches committed on behalf of other contributors).
-There is a <a href="https://www.apache.org/dev/committers";>Committer FAQ</a>
which provides more details on the
-requirements for committers.</p>
-
-<p>It is the custom of the Accumulo project to also invite each committer to
-become a member of the Accumulo PMC.</p>
-
-<h2 id="project-management-committee">Project Management Committee</h2>
-
-<p>The role of the PMC, from a Foundation perspective, is <a
href="https://www.apache.org/foundation/how-it-works.html#pmc";>oversight</a>.
-The main role of the PMC is not code and not coding, but to ensure that all
-legal issues are addressed, that procedure is followed, and that each and every
-release is the product of the community as a whole. That is key to our
-litigation protection mechanisms.</p>
-
-<p>Secondly, the role of the PMC is to further the long-term development and
-health of the community as a whole, and to ensure that balanced and wide scale
-peer review and collaboration does happen. Within the ASF, we worry about any
-community which centers around a few individuals who are working virtually
-uncontested. We believe that this is detrimental to quality, stability, and
-robustness of both code and long term social structures.</p>
-
-<p>The responsibilities of the PMC include:</p>
+<p>The PMC Member role is defined by <a
href="https://www.apache.org/foundation/how-it-works";>the Foundation</a>.
Additional
+information can be found in the <a href="https://www.apache.org/dev/pmc";>PMC
Guide</a>.</p>
+
+<p>Some specific responsibilities of the PMC for Accumulo include:</p>
<ul>
- <li>Deciding what is distributed as products of the Apache Accumulo
project.</li>
- <li>Maintaining the project’s shared resources, including the code
repository, mailing lists, and websites.</li>
- <li>Protecting and ensuring proper use of Apache trademarks by the project
and by other parties.</li>
- <li>Speaking on behalf of the project.</li>
- <li>Nominating new PMC members and committers.</li>
- <li>Maintaining these bylaws and other guidelines of the project.</li>
+ <li>Voting on releases to determine what is distributed as a product of the
Accumulo project</li>
+ <li>Maintaining the project’s shared resources, including the code
repository, mailing lists, and websites</li>
+ <li>Protecting ASF trademarks, including the Accumulo name and logo, and
ensuring their proper use by others</li>
+ <li>Subscribing to the private mailing list and engaging in decisions and
discussions</li>
+ <li>Speaking on behalf of the project</li>
+ <li>Nominating new PMC members and committers</li>
+ <li>Maintaining these bylaws and other guidelines of the project</li>
</ul>
<p>In particular, PMC members must understand both our project’s criteria and
ASF
-criteria for voting on a <a
href="https://www.apache.org/dev/release#management";>release</a>. See the <a
href="https://www.apache.org/dev/pmc";>PMC
-Guide</a> for more information on PMC responsibilities.</p>
-
-<p>Membership of the PMC is by invitation only and must be approved by a
consensus
-approval of active PMC members. Upon acceptance of the invitation to become a
-PMC member, it is the accepting member’s responsibility to update their status
-on the Accumulo web page accordingly.</p>
-
-<p>A PMC member is considered emeritus, meaning inactive, by their own
declaration
-or by not contributing in any form to the project for over six months. Emeritus
-members will be recognized by the PMC on the Accumulo web page, in honor of
-their past contributions. Emeritus members retain all voting and commit rights
-associated with their former designation and can move themselves out of
-emeritus status by sending an announcement of their return to the developer
-mailing list. It will be the returning member’s responsibility to update their
-status on the web page accordingly.</p>
-
-<p>The chair of the PMC is appointed by the ASF board. The chair is an office
-holder of the Apache Software Foundation (Vice President, Apache Accumulo) and
-has primary responsibility to the board for the management of the projects
-within the scope of the Accumulo PMC. The chair reports to the board quarterly
-on developments within the Accumulo project.</p>
-
-<p>When the current chair of the PMC resigns, the PMC votes to recommend a new
-chair using consensus approval, but the decision must be ratified by the Apache
-board.</p>
-
-<h2 id="release-manager">Release Manager</h2>
+criteria for voting on a <a
href="https://www.apache.org/dev/release#management";>release</a>.</p>
+
+<p>Upon acceptance of an invitation to become a PMC member, it is the accepting
+member’s responsibility to update their status on the Accumulo web page
+accordingly, and to make updates as needed.</p>
+
+<p>Because the PMC is a role within the Foundation, changes to PMC membership
+follow criteria established by the board. In general, this means that the board
+chooses who gets added or removed from the PMC, but they may delegate that
+authority to existing PMC members or the PMC chair. However, it is this
+project’s practice to collectively make decisions about PMC additions among the
+existing PMC members on the project’s private mailing list. Accordingly, the
+existing PMC members will conduct a vote before inviting new PMC members, so
+long as that vote can be done without violating the board’s current procedures.
+Depending on the current board procedures, this vote may be merely advisory.
+Additionally, no vote will be conducted without first being preceded by a
+discussion period of at least 72 hours.</p>
+
+<p>PMC members may voluntarily resign from the PMC at any time by their own
+request, and following the appropriate procedures for PMC membership changes
+established by the board. These former members will be recognized as “Emeritus”
+PMC members on the Accumulo web site, in honor of their past contributions.
+Having resigned from the PMC role, these former members will no longer have any
+privileges of PMC membership, such as binding votes for releases or other
+project decisions. However, they will retain any committer privileges, and may
+retain access to the PMC’s private mailing list. Emeritus PMC members, having
+voluntarily resigned, may request to rejoin the PMC and restore their
+privileges, without a vote of the existing PMC members, provided that all other
+procedures for PMC membership changes established by the board are
followed.</p>
+
+<h2 id="pmc-chair">PMC Chair</h2>
+
+<p>The chair of the PMC (PMC Chair) is appointed by the ASF board. The chair
is an
+office holder of the Apache Software Foundation (Vice President, Apache
+Accumulo) and has primary responsibility to the board for the management of the
+projects within the scope of the Accumulo PMC. The chair reports to the board
+quarterly on developments within the Accumulo project.</p>
+
+<p>The current PMC members may at any time vote to recommend a new chair (such
as
+when the current chair declares their desire to resign from the role), but the
+decision must be ratified by the Apache board before the recommended person can
+assume the role.</p>
+
+<p>In the event that the PMC Chair is delegated any special authority by the
board
+to make decisions for the project, that they will first make a good faith
+effort to achieve consensus from the existing PMC members, and will act without
+such consensus only if necessary. For example, if the board delegates the
+authority to make additions to the PMC membership, the chair should follow the
+discussion and advisory vote procedure described in the previous section of
+these bylaws.</p>
+
+<h1 id="releases">Releases</h1>
<p>The <a href="https://www.apache.org/dev/release-publishing";>ASF release
process</a> defines the <a
href="https://www.apache.org/dev/release-publishing#release_manager";>release
manager</a> as an individual responsible for shepherding a new
-project release. Any committer may serve as a release manager. The release
-manager for a release is chosen as part of the release plan.</p>
+project release. Any committer may serve as a release manager by initiating a
+release candidate and starting a vote for a release.</p>
<p>At a minimum, a release manager is responsible for packaging a release
candidate for a vote and signing and publishing an approved release candidate.
@@ -267,8 +252,9 @@ An Accumulo release manager is also expected to:</p>
<li>ensure that required release testing is being conducted</li>
<li>track whether the release is on target for its expected release date</li>
<li>adjust release plan dates to reflect the latest estimates</li>
- <li>determine if a re-plan may be needed and, if so, call a vote</li>
- <li>call votes on release candidates</li>
+ <li>terminate a release vote by either withdrawing a release candidate from
consideration, if needed</li>
+ <li>tally the votes and record the vote result after a release vote period
has elapsed</li>
+ <li>ensure any post-release tasks are performed, such as updating the
website and publishing artifacts</li>
</ul>
<p>Details on <a href="/contributor/making-release">making</a> and <a
href="/contributor/verifying-release">verifying</a> a release are available
@@ -277,10 +263,9 @@ on the Accumulo website.</p>
<h1 id="decision-making">Decision Making</h1>
<p>Within the Accumulo project, different types of decisions require different
-forms of approval. For example, the previous section describes several
-decisions which require ‘consensus approval’. This section defines how voting
-is performed, the types of approvals, and which types of decision require which
-type of approval.</p>
+forms of approval. For example, the previous section describes ‘consensus’ from
+the existing PMC members. Consensus in that case can be achieved through a
+<a
href="https://www.apache.org/foundation/glossary#ConsensusApproval";>consensus
approval vote</a>.</p>
<h2 id="voting">Voting</h2>
@@ -288,226 +273,52 @@ type of approval.</p>
development mailing list: d...@accumulo.apache.org. Where necessary, PMC voting
may take place on the private Accumulo PMC mailing list:
priv...@accumulo.apache.org. Votes are clearly indicated by a subject line
-starting with [VOTE]. A vote message may only pertain to a single item’s
-approval; multiple items should be separated into multiple messages. Voting is
-carried out by replying to the vote mail. A vote may take on one of four forms,
-defined below.</p>
-
-<table class="table">
- <thead>
- <tr>
- <th>Vote</th>
- <th>Meaning</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>+1</td>
- <td><em>Yes</em>, <em>Agree</em>, or <em>The action should be
performed</em>. In general, this vote also indicates a willingness on the
behalf of the voter to <em>make it happen</em>.</td>
- </tr>
- <tr>
- <td>+0</td>
- <td>This vote indicates a willingness for the action under consideration
to go ahead. The voter, however, will not be able to help.</td>
- </tr>
- <tr>
- <td>-0</td>
- <td>This vote indicates that the voter does not, in general, agree with
the proposed action but is not concerned enough to prevent the action going
ahead.</td>
- </tr>
- <tr>
- <td>-1</td>
- <td><em>No</em>, <em>Disagree</em>, or <em>The action should not be
performed</em>. 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.</td>
- </tr>
- </tbody>
-</table>
-
-<p>All participants in the Accumulo project are encouraged to vote. 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 across the wider Accumulo community. For PMC decisions, only the
-votes of active PMC members are binding.</p>
-
-<p>See the <a href="/contributor/voting">voting page</a> for more details on
the mechanics of voting.</p>
+starting with <code class="language-plaintext
highlighter-rouge">[VOTE]</code>. After the vote period has elapsed, the
initiator of the
+vote, or their designee, closes it by replying to the thread with the vote
+results. That result email should use the same subject line preceded by
+<code class="language-plaintext highlighter-rouge">[RESULT][VOTE]</code>.
Voting is carried out by replying to the vote mail and
+continues until the vote is closed. If a vote thread becomes inactive and
+remains open for too long, without a response from the initiator, the PMC Chair
+may close the vote.</p>
+
+<p>All participants in the Accumulo project are encouraged to vote. However,
some
+votes are non-binding (such as votes from non-PMC members during a release
+vote). Non-binding votes are still useful to gain insight into the community’s
+view of the vote topic.</p>
+
+<p>Each person gets only a single vote. You can change your vote by replying to
+the same vote thread to explain the change prior to the vote being closed.</p>
+
+<p>For more information on how to vote, see the Foundation’s page on
+<a href="https://www.apache.org/foundation/voting";>voting</a>.</p>
+
+<p>The Foundation defines voting criteria for procedural issues, code
+modifications, and releases. Most formal votes will be <a
href="https://www.apache.org/foundation/glossary#ConsensusApproval";>consensus
+approval</a>. Release votes, however, follow <a
href="https://www.apache.org/foundation/glossary#MajorityApproval";>majority
+approval</a>. Other decisions, when necessary, can often be made through
+<a href="https://www.apache.org/foundation/glossary#LazyConsensus";>lazy
consensus</a>. In the case of an objection for a lazy consensus vote,
+or the desire for explicit consensus, one can initiate a formal vote
thread.</p>
+
+<p>All votes should last a minimum of 72 hours.</p>
<h2 id="commit-then-review-ctr">Commit Then Review (CTR)</h2>
-<p>Voting can also be applied to changes to the Accumulo codebase. Under the
-Commit Then Review policy, committers can make changes to the codebase without
-seeking approval beforehand, and the changes are assumed to be approved unless
-an objection is raised. Only if an objection is raised must a vote take place
-on the code change.</p>
-
-<p>For some code changes, committers may wish to get feedback from the
community
-before making the change. It is acceptable for a committer to seek approval
-before making a change if they so desire.</p>
-
-<h2 id="approvals">Approvals</h2>
-
-<p>These are the types of approvals that can be sought. Different actions
require
-different types of approvals.</p>
-
-<table class="table">
- <thead>
- <tr>
- <th>Approval Type</th>
- <th>Definition</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>Consensus Approval</td>
- <td>A consensus approval vote passes with 3 binding +1 votes and no
binding vetoes.</td>
- </tr>
- <tr>
- <td>Majority Approval</td>
- <td>A majority approval vote passes with 3 binding +1 votes and more
binding +1 votes than -1 votes.</td>
- </tr>
- <tr>
- <td>Lazy Approval (or Lazy Consensus)</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 majority
approval or consensus approval must be obtained. Lazy Approval can be either
<em>stated</em> or <em>assumed</em>, as detailed on the <a
href="/contributor/lazyConsensus">lazy consensus page</a>.</td>
- </tr>
- </tbody>
-</table>
-
-<h2 id="vetoes">Vetoes</h2>
-
-<p>A valid, binding veto cannot be overruled. If a veto is cast, it must be
-accompanied by a valid reason explaining 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, but merely that the veto is
valid.</p>
-
-<p>If you disagree with a valid veto, you must lobby the person casting the
veto
-to withdraw their veto. If a veto is not withdrawn, the action that has been
-vetoed must be reversed in a timely manner.</p>
-
-<h2 id="actions">Actions</h2>
-
-<p>This section describes the various actions which are undertaken within the
-project, the corresponding approval required for that action and those who have
-binding votes over the action. It also specifies the minimum length of time
-that a vote must remain open, measured in days. In general, votes should not be
-called at times when it is known that interested members of the project will be
-unavailable.</p>
-
-<p>For Code Change actions, a committer may choose to employ assumed or stated
-Lazy Approval under the <a href="#commit-then-review-ctr">CTR</a> policy.
Assumed Lazy Approval has no minimum
-length of time before the change can be made.</p>
-
-<table class="table">
- <thead>
- <tr>
- <th>Action</th>
- <th>Description</th>
- <th>Approval</th>
- <th>Binding Votes</th>
- <th>Min. Length (days)</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>Code Change</td>
- <td>A change made to a codebase of the project. This includes source
code, documentation, website content, etc.</td>
- <td>Lazy approval, moving to consensus approval upon veto</td>
- <td>Active committers</td>
- <td>1</td>
- </tr>
- <tr>
- <td>Release Plan</td>
- <td>Defines the timetable and actions for an upcoming release. The plan
also nominates a Release Manager.</td>
- <td>Lazy approval, moving to majority approval upon veto</td>
- <td>Active committers</td>
- <td>3</td>
- </tr>
- <tr>
- <td>Release Plan Cancellation</td>
- <td>Cancels an active release plan, due to a need to re-plan (e.g.,
discovery of a major issue).</td>
- <td>Majority approval</td>
- <td>Active committers</td>
- <td>3</td>
- </tr>
- <tr>
- <td>Product Release</td>
- <td>Accepts or rejects a release candidate as an official release of the
project.</td>
- <td>Majority approval</td>
- <td>Active PMC members</td>
- <td>3</td>
- </tr>
- <tr>
- <td>Adoption of New Codebase</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>Consensus approval</td>
- <td>Active PMC members</td>
- <td>7</td>
- </tr>
- <tr>
- <td>New Committer</td>
- <td>When a new committer is proposed for the project.</td>
- <td>Consensus approval</td>
- <td>Active PMC members</td>
- <td>3</td>
- </tr>
- <tr>
- <td>New PMC Member</td>
- <td>When a committer is proposed for the PMC.</td>
- <td>Consensus approval</td>
- <td>Active PMC members</td>
- <td>3</td>
- </tr>
- <tr>
- <td>New PMC Chair</td>
- <td>When a new PMC chair is chosen to succeed an outgoing chair.</td>
- <td>Consensus approval</td>
- <td>Active PMC members</td>
- <td>3</td>
- </tr>
- <tr>
- <td>Modifying Bylaws</td>
- <td>Modifying this document.</td>
- <td>Consensus approval</td>
- <td>Active PMC members</td>
- <td>7</td>
- </tr>
- </tbody>
-</table>
-
-<p>No other voting actions are defined; all other actions should presume Lazy
-Approval (defaulting to Consensus Approval upon veto). If an action is voted on
-multiple times, or if a different approval type is desired, these bylaws should
-be amended to include the action.</p>
-
-<p>For the purposes of the “Adoption of New Codebase” action, the Accumulo
-codebase is defined as the Accumulo site content, primary project code, and all
-contributed code (“contribs”) as they exist in their respective repositories.
-Adoption of a new codebase generally refers to the creation of a new contrib
-repository, but could cover, for example, a rework of the project site, or
-merging a contrib project into the primary codebase.</p>
-
-<p>Voting actions for the removal of a committer or PMC member are
intentionally
-not defined. According to ASF rules, <a
href="https://www.apache.org/dev/committers#committer-set-term";>committer
status never
-expires</a> and <a href="https://www.apache.org/dev/pmc#pmc-removal";>PMC
members can only be removed with approval
-from the ASF Board</a>.</p>
-
-<h1 id="release-plans">Release Plans</h1>
-
-<p>The approval of a release plan begins the process of creating a new project
-release. The process ends when a release candidate is approved.</p>
-
-<p>An Accumulo release plan consists of at least the following:</p>
-
-<ul>
- <li>a version number</li>
- <li>a feature freeze date</li>
- <li>a code freeze date</li>
- <li>a release date</li>
- <li>the choice of a release manager</li>
-</ul>
-
-<p>After feature freeze, new features should not be accepted for the release.
-After code freeze, only critical fixes should be accepted for the release. The
-release manager guides the decision on accepting changes.</p>
-
-<p>All dates in a plan are estimates, as unforeseen issues may require delays.
The
-release manager may adjust dates as needed. In serious circumstances, the
-release manager may opt to call a re-plan vote.</p>
+<p>Accumulo follows a commit-then-review (CTR) policy. This means that
consensus
+is not required prior to committing. Committers can make changes to the
+codebase without seeking approval beforehand, and those changes are assumed to
+be approved unless an objection is raised afterwards. Only if an objection is
+raised must a vote take place on the code change.</p>
+
+<p>However, just because committers can do this, it does not mean it is always
a
+good idea. Committers are expected to use their privileges responsibly and to
+minimize risks. Therefore, it is often a good idea for committers to seek
+feedback through code reviews from the community. Code reviews are our standard
+practice and strongly encouraged for anything non-trivial. They are also
+strongly encouraged for new committers, even if a change is trivial. If
+approval is bypassed, and a problem occurs, committers may be expected to
+answer questions about their commit in order to understand what went wrong and
+how to avoid problems in the future. So, committers should take care to not
+abuse the CTR policy, and to use it sparingly and in ways they can justify.</p>
</div>
diff --git a/output/contributor/consensusBuilding.html
b/output/contributor/consensusBuilding.html
index 398b548ef..f0108edbe 100644
--- a/output/contributor/consensusBuilding.html
+++ b/output/contributor/consensusBuilding.html
@@ -162,7 +162,7 @@ add up the strength of feeling of the community and decide
if there is consensus
or not.</p>
<p>Once there is a clear consensus, members of the community can proceed with
-the work under the <a href="/contributor/lazyConsensus">lazy consensus</a>
model.</p>
+the work under the <a
href="https://www.apache.org/foundation/glossary#LazyConsensus";>lazy
consensus</a> model.</p>
</div>
diff --git a/output/contributor/lazyConsensus.html
b/output/contributor/lazyConsensus.html
deleted file mode 100644
index 0076f8054..000000000
--- a/output/contributor/lazyConsensus.html
+++ /dev/null
@@ -1,192 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<meta charset="utf-8">
-<meta http-equiv="X-UA-Compatible" content="IE=edge">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-
-<link rel="stylesheet" type="text/css"
href="/css/bootstrap/5.3.3/dist/css/bootstrap.css">
-<link rel="stylesheet" type="text/css"
href="/css/fontawesome/fontawesome-free-6.6.0-web/css/all.css">
-<link rel="stylesheet" type="text/css"
href="/css/datatables/bs5/dt-2.0.8/datatables.css">
-<link rel="stylesheet" type="text/css" href="/css/accumulo.css">
-
-<title>Lazy Consensus</title>
-
-<script type="text/javascript" src="/js/jquery/3.7.1/jquery.js"></script>
-<script type="text/javascript"
src="/js/bootstrap/5.3.3/dist/js/bootstrap.bundle.js"></script>
-<script type="text/javascript"
src="/js/datatables/bs5/dt-2.0.8/datatables.js"></script>
-<script type="text/javascript"
src="https://www.apachecon.com/event-images/snippet.js";></script>
-<script type="text/javascript" src="/js/accumulo.js"></script>
-</head>
-<body style="padding-top: 100px">
-
- <nav class="navbar navbar-expand-lg navbar-light fixed-top bg-light">
- <div class="container">
- <a class="navbar-brand" href="/">
- <img alt="Apache Accumulo" id="nav-logo" src="/images/accumulo-logo.png"
width="200">
- </a>
- <button class="navbar-toggler" type="button" data-bs-toggle="collapse"
data-bs-target="#navbar-items">
- <span class="navbar-toggler-icon"></span>
- </button>
- <div class="collapse navbar-collapse" id="navbar-items">
- <ul class="navbar-nav me-auto">
- <li class="nav-item"><a class="nav-link"
href="/downloads">Download</a></li>
- <li class="nav-item"><a class="nav-link" href="/tour">Tour</a></li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" role="button"
data-bs-toggle="dropdown">Releases</a>
- <ul class="dropdown-menu">
- <li><a class="dropdown-item" href="/release/accumulo-3.0.0/">3.0.0
(Latest non-LTM)</a></li>
- <li><a class="dropdown-item" href="/release/accumulo-2.1.3/">2.1.3
(Latest LTM)</a></li>
- <li><a class="dropdown-item"
href="/release/accumulo-1.10.4/">1.10.4 (Legacy LTM)</a></li>
- <li><a class="dropdown-item" href="/release/">Archive</a></li>
- </ul>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" role="button"
data-bs-toggle="dropdown">Documentation</a>
- <ul class="dropdown-menu">
- <li><a class="dropdown-item" href="/docs/2.x">User Manual
(2.x)</a></li>
- <li><a class="dropdown-item" href="/docs/2.x/apidocs">Javadocs
(2.x)</a></li>
- <li><a class="dropdown-item" href="/api">Public API</a></li>
- <li><a class="dropdown-item" href="/quickstart-1.x">Quickstart
(1.x)</a></li>
- <li><a class="dropdown-item"
href="/accumulo2-maven-plugin">Accumulo Maven Plugin</a></li>
- <li><a class="dropdown-item"
href="/1.10/accumulo_user_manual.html">User Manual (1.10)</a></li>
- <li><a class="dropdown-item" href="/1.10/apidocs">Javadocs
(1.10)</a></li>
- <li><a class="dropdown-item" href="/external-docs">External
Docs</a></li>
- <li><a class="dropdown-item" href="/docs-archive/">Archive</a></li>
- </ul>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" role="button"
data-bs-toggle="dropdown">Community</a>
- <ul class="dropdown-menu">
- <li><a class="dropdown-item" href="/contact-us">Contact Us</a></li>
- <li><a class="dropdown-item" href="/how-to-contribute">How To
Contribute</a></li>
- <li><a class="dropdown-item" href="/people">People</a></li>
- <li><a class="dropdown-item" href="/related-projects">Related
Projects</a></li>
- </ul>
- </li>
- <li class="nav-item"><a class="nav-link" href="/search">Search</a></li>
- </ul>
- <ul class="navbar-nav ms-auto">
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" role="button"
data-bs-toggle="dropdown">
- <img alt="Apache Software Foundation"
src="https://www.apache.org/foundation/press/kit/feather.svg"; width="15"/>
- </a>
- <ul class="dropdown-menu dropdown-menu-end">
- <li><a class="dropdown-item" href="https://www.apache.org";>Apache
Homepage <span class="fa-solid fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/licenses/";>License <span class="fa-solid
fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/foundation/sponsorship";>Sponsorship <span
class="fa-solid fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/security";>Security <span class="fa-solid
fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/foundation/thanks";>Thanks <span class="fa-solid
fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/foundation/policies/conduct";>Code of Conduct <span
class="fa-solid fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/foundation/policies/privacy.html";>Privacy
Policy<span class="fa-solid fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/events/current-event.html";>Current Event <span
class="fa-solid fa-up-right-from-square"></span></a></li>
- </ul>
- </li>
- </ul>
- </div>
- </div>
-</nav>
-
-
- <div class="container">
- <div class="row">
- <div class="col-md-12">
-
- <div id="non-canonical" style="display: none; background-color:
#F0E68C; padding-left: 1em;">
- Visit the official site at: <a
href="https://accumulo.apache.org";>https://accumulo.apache.org</a>
- </div>
- <div id="content">
-
- <h1 class="title">Lazy Consensus</h1>
-
- <p>The concept of “Lazy Consensus” is very important in our project.
Lazy
-Consensus means that when you are convinced that you know what the community
-would like to see happen you can simply assume that you already have consensus
-and get on with the work. You don’t have to insist people discuss and/or
-approve your plan, and you certainly don’t need to call a vote to get approval.
-You just assume you have the community’s support unless someone says
otherwise.</p>
-
-<p>We have a time machine (Subversion), this means that as long as you commit
-(or submit patches) early and often the community has plenty of opportunity
-to indicate disapproval. If you believe the community will support your action
-you can operate on lazy consensus as long as you are prepared to roll back
-any work should a valid objection is raised.</p>
-
-<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion</h2>
-
-<p>The key thing about lazy consensus is that it’s easier for people to agree,
-by doing nothing, than it is to object, which requires an
-alternative to be proposed. This has two effects, firstly people are less
-likely to object for the sake of it and secondly it cuts down on the amount
-of unnecessary mail traffic and discussion.</p>
-
-<p>Lazy consensus means we can avoid waiting for a community based decision
-before proceeding. However, it does require everyone who cares for the health
-of the project to watch what is happening, as it is happening. Objecting too
-far down the road will cause upset, but objecting (or asking for clarification
-of intent) early is likely to be greeted with relief that someone is watching
-and cares.</p>
-
-<h2 id="stating-lazy-consensus">Stating Lazy Consensus</h2>
-
-<p>Sometimes a member of the community will believe a specific action is the
correct
-one for the community but are not sure enough to proceed with the work under
the
-lazy consensus model. In these circumstances, they can state Lazy Consensus is
in
-operation.</p>
-
-<p>What this means is that they make a proposal and state that they will start
-implementing it in 72 hours unless someone objects. 72 hours is chosen because
-it accounts for different timezones and non-apache commitments.</p>
-
-<p>In this approach the original proposal is not insisting that there is a
discussion
-around their proposal, nor are they requesting that the community explicitly
-supports their actions. However, this differs from assuming lazy consensus
-since it allows space and time to <a
href="/contributor/consensusBuilding">express support or objections</a> and
corrections to
-the proposal before work begins.</p>
-
-<h2 id="silence-is-consent">Silence is consent</h2>
-
-<p>People may choose to indicate their support for the actions taken with a +1
-mail - quick and easy to read and reassuring for the implementer. However,
-remember, in a lazy consensus world silence is the equivalent to support. This
-can take some time to get used to.</p>
-
-
- </div>
-
-
-<footer>
-
- <p><a href="https://www.apache.org/foundation/contributing";><img
src="https://www.apache.org/images/SupportApache-small.png"; alt="Support the
ASF" id="asf-logo" height="100" /></a></p>
-
- <p>Copyright © 2011-2024 <a href="https://www.apache.org";>The Apache
Software Foundation</a>.
-Licensed under the <a href="https://www.apache.org/licenses/";>Apache License,
Version 2.0</a>.</p>
-
- <p>Apache®, the names of Apache projects and their logos, and the multicolor
feather
-logo are registered trademarks or trademarks of The Apache Software Foundation
-in the United States and/or other countries.</p>
-
-</footer>
-
-
- </div>
- </div>
- </div>
-</body>
-</html>
diff --git a/output/contributor/voting.html b/output/contributor/voting.html
deleted file mode 100644
index 388700974..000000000
--- a/output/contributor/voting.html
+++ /dev/null
@@ -1,226 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<meta charset="utf-8">
-<meta http-equiv="X-UA-Compatible" content="IE=edge">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-
-<link rel="stylesheet" type="text/css"
href="/css/bootstrap/5.3.3/dist/css/bootstrap.css">
-<link rel="stylesheet" type="text/css"
href="/css/fontawesome/fontawesome-free-6.6.0-web/css/all.css">
-<link rel="stylesheet" type="text/css"
href="/css/datatables/bs5/dt-2.0.8/datatables.css">
-<link rel="stylesheet" type="text/css" href="/css/accumulo.css">
-
-<title>Voting</title>
-
-<script type="text/javascript" src="/js/jquery/3.7.1/jquery.js"></script>
-<script type="text/javascript"
src="/js/bootstrap/5.3.3/dist/js/bootstrap.bundle.js"></script>
-<script type="text/javascript"
src="/js/datatables/bs5/dt-2.0.8/datatables.js"></script>
-<script type="text/javascript"
src="https://www.apachecon.com/event-images/snippet.js";></script>
-<script type="text/javascript" src="/js/accumulo.js"></script>
-</head>
-<body style="padding-top: 100px">
-
- <nav class="navbar navbar-expand-lg navbar-light fixed-top bg-light">
- <div class="container">
- <a class="navbar-brand" href="/">
- <img alt="Apache Accumulo" id="nav-logo" src="/images/accumulo-logo.png"
width="200">
- </a>
- <button class="navbar-toggler" type="button" data-bs-toggle="collapse"
data-bs-target="#navbar-items">
- <span class="navbar-toggler-icon"></span>
- </button>
- <div class="collapse navbar-collapse" id="navbar-items">
- <ul class="navbar-nav me-auto">
- <li class="nav-item"><a class="nav-link"
href="/downloads">Download</a></li>
- <li class="nav-item"><a class="nav-link" href="/tour">Tour</a></li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" role="button"
data-bs-toggle="dropdown">Releases</a>
- <ul class="dropdown-menu">
- <li><a class="dropdown-item" href="/release/accumulo-3.0.0/">3.0.0
(Latest non-LTM)</a></li>
- <li><a class="dropdown-item" href="/release/accumulo-2.1.3/">2.1.3
(Latest LTM)</a></li>
- <li><a class="dropdown-item"
href="/release/accumulo-1.10.4/">1.10.4 (Legacy LTM)</a></li>
- <li><a class="dropdown-item" href="/release/">Archive</a></li>
- </ul>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" role="button"
data-bs-toggle="dropdown">Documentation</a>
- <ul class="dropdown-menu">
- <li><a class="dropdown-item" href="/docs/2.x">User Manual
(2.x)</a></li>
- <li><a class="dropdown-item" href="/docs/2.x/apidocs">Javadocs
(2.x)</a></li>
- <li><a class="dropdown-item" href="/api">Public API</a></li>
- <li><a class="dropdown-item" href="/quickstart-1.x">Quickstart
(1.x)</a></li>
- <li><a class="dropdown-item"
href="/accumulo2-maven-plugin">Accumulo Maven Plugin</a></li>
- <li><a class="dropdown-item"
href="/1.10/accumulo_user_manual.html">User Manual (1.10)</a></li>
- <li><a class="dropdown-item" href="/1.10/apidocs">Javadocs
(1.10)</a></li>
- <li><a class="dropdown-item" href="/external-docs">External
Docs</a></li>
- <li><a class="dropdown-item" href="/docs-archive/">Archive</a></li>
- </ul>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" role="button"
data-bs-toggle="dropdown">Community</a>
- <ul class="dropdown-menu">
- <li><a class="dropdown-item" href="/contact-us">Contact Us</a></li>
- <li><a class="dropdown-item" href="/how-to-contribute">How To
Contribute</a></li>
- <li><a class="dropdown-item" href="/people">People</a></li>
- <li><a class="dropdown-item" href="/related-projects">Related
Projects</a></li>
- </ul>
- </li>
- <li class="nav-item"><a class="nav-link" href="/search">Search</a></li>
- </ul>
- <ul class="navbar-nav ms-auto">
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" role="button"
data-bs-toggle="dropdown">
- <img alt="Apache Software Foundation"
src="https://www.apache.org/foundation/press/kit/feather.svg"; width="15"/>
- </a>
- <ul class="dropdown-menu dropdown-menu-end">
- <li><a class="dropdown-item" href="https://www.apache.org";>Apache
Homepage <span class="fa-solid fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/licenses/";>License <span class="fa-solid
fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/foundation/sponsorship";>Sponsorship <span
class="fa-solid fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/security";>Security <span class="fa-solid
fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/foundation/thanks";>Thanks <span class="fa-solid
fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/foundation/policies/conduct";>Code of Conduct <span
class="fa-solid fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/foundation/policies/privacy.html";>Privacy
Policy<span class="fa-solid fa-up-right-from-square"></span></a></li>
- <li><a class="dropdown-item"
href="https://www.apache.org/events/current-event.html";>Current Event <span
class="fa-solid fa-up-right-from-square"></span></a></li>
- </ul>
- </li>
- </ul>
- </div>
- </div>
-</nav>
-
-
- <div class="container">
- <div class="row">
- <div class="col-md-12">
-
- <div id="non-canonical" style="display: none; background-color:
#F0E68C; padding-left: 1em;">
- Visit the official site at: <a
href="https://accumulo.apache.org";>https://accumulo.apache.org</a>
- </div>
- <div id="content">
-
- <h1 class="title">Voting</h1>
-
- <p>Occasionally a “feel” for consensus is not enough. Sometimes we
need to have a
-measurable consensus. For example, when voting in new committers or to approve
a
-release.</p>
-
-<h2 id="preparing-for-a-vote">Preparing for a Vote</h2>
-
-<p>Before calling a vote, it is important to ensure that the community is
given time to
-discuss the upcoming vote. This will be done by posting an email to the list
-indicating the intention to call a vote and the options available. By the time
a
-vote is called, there should already be <a href="consensusBuilding">consensus
in the community</a>. The vote
-itself is, normally, a formality.</p>
-
-<h2 id="calling-a-vote">Calling a Vote</h2>
-
-<p>Once it is time to call the vote a mail is posted with a subject starting
with
-“[VOTE]”. This enables the community members to ensure they do not miss an
important
-vote thread. It also indicates that this is not consensus building but a formal
-vote. The initiator is responsible for the vote. That means also to count the
votes
-and present the results. Everyone has 1 vote.</p>
-
-<h3 id="casting-your-vote">Casting Your Vote</h3>
-
-<p>The notation used in voting is:</p>
-
-<p>+1 (means I vote positive)
- You can say why you vote positive but it’s not a must-have.</p>
-
-<p>0 (means I have no strong opinion, aka abstention)</p>
-
-<p>-1 (means I vote negative because of the following reason)
- Yes, you must support your objection and provide an alternative course of
action
- that you are willing and able to implement (where appropriate).</p>
-
-<h4 id="example-for-a-vote-mail">Example for a vote mail:</h4>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>Address: private@
-Subject: [VOTE] John Doe should become a regular committer
-
-Text:
-"I would like to propose to vote in John Doe as committer. John has showed in
-the last months that he has the skills and oversight for improving things
(think
-about the last UI change of the "Find" dialog)."
-
-+1 (means I vote for John)
-0 (means I'm not for John but also not against to vote him in)
--1 (means I'm not for John because of the following reason(s):
-
-Voting time frame is finished 72 hours from now until June 30, 12:00 PM UTC.
-</code></pre></div></div>
-
-<h4 id="example-for-a-reply-mail">Example for a reply mail:</h4>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>Text:
-+1
-
-I like his work and want him to stay and to go on with his good improvements.
-</code></pre></div></div>
-
-<h4 id="example-for-a-result-mail">Example for a result mail:</h4>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>Subject: [VOTE][RESULTS] John Doe should become a
regular committer
-
-Text:
-Vote started Thu, Jun 27, 2011 at 12:00 PM UTC, voting is now closed.
-
-Voting results:
-
---- Numbers ---
-
-+1: 6
- 0: 0
--1: 0
-
---- Details ---
-
-+1 John
-+1 Jane
-+1 David
-+1 Dolores
-+1 Carl
-+1 Chris
-</code></pre></div></div>
-
-<p><a href="https://www.apache.org/foundation/voting";>See here for more
information</a> <br />
-<a href="https://community.apache.org/newcommitter";>See here for more mail
templates</a></p>
-
-
- </div>
-
-
-<footer>
-
- <p><a href="https://www.apache.org/foundation/contributing";><img
src="https://www.apache.org/images/SupportApache-small.png"; alt="Support the
ASF" id="asf-logo" height="100" /></a></p>
-
- <p>Copyright © 2011-2024 <a href="https://www.apache.org";>The Apache
Software Foundation</a>.
-Licensed under the <a href="https://www.apache.org/licenses/";>Apache License,
Version 2.0</a>.</p>
-
- <p>Apache®, the names of Apache projects and their logos, and the multicolor
feather
-logo are registered trademarks or trademarks of The Apache Software Foundation
-in the United States and/or other countries.</p>
-
-</footer>
-
-
- </div>
- </div>
- </div>
-</body>
-</html>
diff --git a/output/contributors-guide/index.html
b/output/contributors-guide/index.html
index 6bdf76c3a..f392a325d 100644
--- a/output/contributors-guide/index.html
+++ b/output/contributors-guide/index.html
@@ -175,8 +175,6 @@ developers use <a
href="https://www.jetbrains.com/idea/download";>IntelliJ</a> or
<ul>
<li><a href="/contributor/bylaws">Bylaws</a></li>
<li><a href="/contributor/consensusBuilding">Consensus Building</a></li>
- <li><a href="/contributor/lazyConsensus">Lazy Consensus</a></li>
- <li><a href="/contributor/voting">Voting</a></li>
</ul>
diff --git a/output/feed.xml b/output/feed.xml
index 5350707f4..08ef4ee96 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,8 +6,8 @@
</description>
<link>https://accumulo.apache.org/</link>
<atom:link href="https://accumulo.apache.org/feed.xml"; rel="self"
type="application/rss+xml"/>
- <pubDate>Thu, 19 Sep 2024 18:34:49 +0000</pubDate>
- <lastBuildDate>Thu, 19 Sep 2024 18:34:49 +0000</lastBuildDate>
+ <pubDate>Fri, 27 Sep 2024 19:24:44 +0000</pubDate>
+ <lastBuildDate>Fri, 27 Sep 2024 19:24:44 +0000</lastBuildDate>
<generator>Jekyll v4.3.4</generator>
diff --git a/output/governance/lazyConsensus.html
b/output/governance/lazyConsensus.html
deleted file mode 100644
index e3a7ab1f2..000000000
--- a/output/governance/lazyConsensus.html
+++ /dev/null
@@ -1,11 +0,0 @@
-<!DOCTYPE html>
-<html lang="en-US">
- <meta charset="utf-8">
- <title>Redirecting…</title>
- <link rel="canonical"
href="https://accumulo.apache.org/contributor/lazyConsensus.html";>
-
<script>location="https://accumulo.apache.org/contributor/lazyConsensus.html";</script>
- <meta http-equiv="refresh" content="0;
url=https://accumulo.apache.org/contributor/lazyConsensus.html";>
- <meta name="robots" content="noindex">
- <h1>Redirecting…</h1>
- <a href="https://accumulo.apache.org/contributor/lazyConsensus.html";>Click
here if you are not redirected.</a>
-</html>
diff --git a/output/governance/voting.html b/output/governance/voting.html
deleted file mode 100644
index 7016f799d..000000000
--- a/output/governance/voting.html
+++ /dev/null
@@ -1,11 +0,0 @@
-<!DOCTYPE html>
-<html lang="en-US">
- <meta charset="utf-8">
- <title>Redirecting…</title>
- <link rel="canonical"
href="https://accumulo.apache.org/contributor/voting.html";>
-
<script>location="https://accumulo.apache.org/contributor/voting.html";</script>
- <meta http-equiv="refresh" content="0;
url=https://accumulo.apache.org/contributor/voting.html";>
- <meta name="robots" content="noindex">
- <h1>Redirecting…</h1>
- <a href="https://accumulo.apache.org/contributor/voting.html";>Click here if
you are not redirected.</a>
-</html>
diff --git a/output/redirects.json b/output/redirects.json
index 9047e0ae7..8bc3a5afb 100644
--- a/output/redirects.json
+++ b/output/redirects.json
@@ -1 +1 @@
-{"/release_notes/1.5.1.html":"https://accumulo.apache.org/release/accumulo-1.5.1/","/release_notes/1.6.0.html":"https://accumulo.apache.org/release/accumulo-1.6.0/","/release_notes/1.5.2.html":"https://accumulo.apache.org/release/accumulo-1.5.2/","/release_notes/1.6.1.html":"https://accumulo.apache.org/release/accumulo-1.6.1/","/release_notes/1.6.2.html":"https://accumulo.apache.org/release/accumulo-1.6.2/","/release_notes/1.7.0.html":"https://accumulo.apache.org/release/accumulo-1.7.0/";
[...]
\ No newline at end of file
+{"/release_notes/1.5.1.html":"https://accumulo.apache.org/release/accumulo-1.5.1/","/release_notes/1.6.0.html":"https://accumulo.apache.org/release/accumulo-1.6.0/","/release_notes/1.5.2.html":"https://accumulo.apache.org/release/accumulo-1.5.2/","/release_notes/1.6.1.html":"https://accumulo.apache.org/release/accumulo-1.6.1/","/release_notes/1.6.2.html":"https://accumulo.apache.org/release/accumulo-1.6.2/","/release_notes/1.7.0.html":"https://accumulo.apache.org/release/accumulo-1.7.0/";
[...]
\ No newline at end of file
![https://www.apache.org/foundation/press/kit/feather.svg"](https://www.apache.org/foundation/press/kit/feather.svg"){kind=link}
![https://www.apache.org/images/SupportApache-small.png"](https://www.apache.org/images/SupportApache-small.png"){kind=link}