couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nsla...@apache.org
Subject svn commit: r1615232 - in /couchdb/site: bylaws.v1.html bylaws.v2.html
Date Fri, 01 Aug 2014 21:11:25 GMT
Author: nslater
Date: Fri Aug  1 21:11:24 2014
New Revision: 1615232

URL: http://svn.apache.org/r1615232
Log:
Removed data- attributes

Modified:
    couchdb/site/bylaws.v1.html
    couchdb/site/bylaws.v2.html

Modified: couchdb/site/bylaws.v1.html
URL: http://svn.apache.org/viewvc/couchdb/site/bylaws.v1.html?rev=1615232&r1=1615231&r2=1615232&view=diff
==============================================================================
--- couchdb/site/bylaws.v1.html (original)
+++ couchdb/site/bylaws.v1.html Fri Aug  1 21:11:24 2014
@@ -24,7 +24,7 @@
 <h1>2. Roles and Responsibilities</h1>
 <p><strong>The ASF&nbsp;<a href="https://www.apache.org/foundation/how-it-works.html#roles">defines
a set of roles</a> 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.</strong>
 <p><span><span>Your role is bestowed on you by your peers in recognition
of your past contributions to the project and your position of trust within the community.
It is not tied to your job, your current employer, or your current activity level. We are
interested in you as an individual and we&nbsp;understand that your interactions with
the project may change over time.</span></span>
-<p><span><span>Roles are never rescinded because of inactivity, unless
that inactivity is causing a problem for the project. Fortunately, our decision making process
means that inactivity is very rarely a problem. Roles will be rescinded if the <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-ProjectBylaws(WIP)-2.4.ProjectManagementCommittee"
data-anchor="ProjectBylaws(WIP)-2.4.ProjectManagementCommittee" data-linked-resource-default-alias="ProjectBylaws(WIP)-2.4.ProjectManagementCommittee"
data-base-url="https://cwiki.apache.org/confluence">Project Management Committee</a>
(or <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-ProjectBylaws(WIP)-2.4.ProjectManagementCommittee"
data-anchor="ProjectBylaws(WIP)-2.4.ProjectManagementCommittee" data-linked-resource-default-alias="ProjectBylaws(WIP)-2.4.ProjectManagementCommittee"
data-base-url="https://cwiki.apache.org/confluence">PMC</a>, see 2.4. below) be
 lieves the individual is no longer able to responsibly discharge the duty of the role.</span></span>
+<p><span><span>Roles are never rescinded because of inactivity, unless
that inactivity is causing a problem for the project. Fortunately, our decision making process
means that inactivity is very rarely a problem. Roles will be rescinded if the <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-ProjectBylaws(WIP)-2.4.ProjectManagementCommittee">Project
Management Committee</a> (or <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-ProjectBylaws(WIP)-2.4.ProjectManagementCommittee">PMC</a>,
see 2.4. below) believes the individual is no longer able to responsibly discharge the duty
of the role.</span></span>
 <p><span>We understand that you have many roles in life. We use a hat metaphor
to talk about these roles. For instance, y</span><span>ou might have your work
hat as well as several ASF hats.&nbsp;</span><span>We expect you to know when
to wear the appropriate hat, and to comport yourself in a manner befitting the interests of
the Foundation when interacting with the project. Failure to do this is a serious&nbsp;</span><span>dereliction</span><span>&nbsp;of
duty.</span>
 <p><span>Sometimes it is a good idea to tell people which hat you are wearing.
For instance, the PMC Chair might start an informal email by stating they are not wearing
the PMC Chair's hat, just to be clear about how the statements ought to be interpreted.</span>
 <p><span>We expect you to act in good faith. This is very important for a community
that depends so heavily on trust.</span>
@@ -43,7 +43,7 @@
 <li>Project (blogging, marketing, design, UX, branding, etc)
 <li>Documentation (documentation, localisation/internationalisation, etc.)
 <li>Code (new features, bug fixing, quality assurance, release management etc.)</ul>
-<p>More details are available in <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Contributor+Guide"
data-linked-resource-id="40511227" data-linked-resource-type="page" data-linked-resource-default-alias="Contributor
Guide" data-base-url="https://cwiki.apache.org/confluence">the contributor guide</a>.
If any of these things sound interesting to you, we welcome your help.
+<p>More details are available in <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Contributor+Guide">the
contributor guide</a>. If any of these things sound interesting to you, we welcome your
help.
 <p>The role of committer is mandated at the Foundation level. Unfortunately, the usual
definition of that word—being someone who commits code—can mean that non-coders
are never given binding votes on a project. We think that's a problem. C<span>ontributions
come in many shapes and sizes. Indeed, many of those non-code contributions are what the project
needs the most.</span>
 <p>To make this clear, we have chosen to define a committer as someone who is <em>committed</em>.
We mean this in the sense of being loyal to the project and its interests. It is a position
of trust, not an expectation of activity level. Anyone who is supportive of the community
and the project will be considered as a candidate for being a committer.
 <p>As a matter of convenience, committers are also given write access to all of the
public project infrastructure, including source control repositories, website, issue tracker,
wiki, and blog. Access to social media accounts, and other third-party services, will be granted
upon request.
@@ -52,7 +52,7 @@
 <p>A committer who makes a sustained contribution to the project may be invited to
become a&nbsp;<em>Project Management Committee</em> (PMC) member.
 <h2>2.4. Project Management Committee</h2>
 <p><strong>The <em>Project Management Committee</em> (PMC) is responsible
for the management of the project.</strong>
-<p><span>At the most basic level, the role of the PMC is oversight. The PMC must
ensure that all relevant</span> <span>bylaws</span><span>&nbsp;</span><span>,</span>
<span>policies, and procedures</span><span>&nbsp;</span> <span><span>are
adhered to. These exist at the Foundation-level and the project-level. See the <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+affairs"
data-linked-resource-id="39621747" data-linked-resource-type="page" data-linked-resource-default-alias="Project
affairs" data-base-url="https://cwiki.apache.org/confluence">project affairs</a>&nbsp;page
for more information.</span></span>
+<p><span>At the most basic level, the role of the PMC is oversight. The PMC must
ensure that all relevant</span> <span>bylaws</span><span>&nbsp;</span><span>,</span>
<span>policies, and procedures</span><span>&nbsp;</span> <span><span>are
adhered to. These exist at the Foundation-level and the project-level. See the <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+affairs">project
affairs</a>&nbsp;page for more information.</span></span>
 <p>Beyond this requirement, the primary goal of the PMC is to invest in the long term
wellbeing of the community.&nbsp;<span>For this reason, one of the most basic tasks
of the PMC is the recruitment and management of project contributors. We believe that the
size, diversity, and health of the community is essential for the quality, stability, and
robustness of project and it's social structures.</span>
 <p>Actives of the PMC include, but are not limited to:
 <ul>
@@ -146,8 +146,8 @@
 <td colspan="1">"Extremely unhappy with this proposal."
 <td colspan="1">-1</table>
 <p>There are three types of voting: informal, formal, and vetos. An informal vote is
a quick way to get people's feelings on something.&nbsp;<span>A formal vote, on
the other hand, requires an approval model and a decision type. More detail on approval models,
vetos and decision types is available in sections 3.4, 3.5., and 3.6.<br></span>
-<p>All formal voting must be done in an email thread&nbsp;with the appropriate&nbsp;<a
href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-4.1.SubjectTags"
data-anchor="4.1.SubjectTags" data-linked-resource-default-alias="4.1.SubjectTags" data-base-url="https://cwiki.apache.org/confluence">subject
tag</a><span>.&nbsp;</span><span>Formal votes may contain multiple
items for approval and these should be clearly separated. Formal voting is then carried out
by replying to the vote mail.&nbsp;</span><span>Formal votes are open for
a period of at least 72 hours to allow all active voters time to consider the vote. Votes
can be held open longer than this at the discretion of the person who initiated the vote.</span>
-<p><span>Votes on <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-ProjectBylaws(WIP)-3.6.DecisionTypes"
data-anchor="ProjectBylaws(WIP)-3.6.DecisionTypes" data-linked-resource-default-alias="ProjectBylaws(WIP)-3.6.DecisionTypes"
data-base-url="https://cwiki.apache.org/confluence">PMC decisions</a> are binding
if they are cast by a PMC member. For all other purposes, votes are binding if they are cast
by a committer. However, it is important to remember that all participants on a list get a
vote. And you are encouraged to vote, even if your vote is not binding. This is a good way
to get involved in the project and helps to inform the decision-making process.</span>
+<p>All formal voting must be done in an email thread&nbsp;with the appropriate&nbsp;<a
href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-4.1.SubjectTags">subject
tag</a><span>.&nbsp;</span><span>Formal votes may contain multiple
items for approval and these should be clearly separated. Formal voting is then carried out
by replying to the vote mail.&nbsp;</span><span>Formal votes are open for
a period of at least 72 hours to allow all active voters time to consider the vote. Votes
can be held open longer than this at the discretion of the person who initiated the vote.</span>
+<p><span>Votes on <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-ProjectBylaws(WIP)-3.6.DecisionTypes">PMC
decisions</a> are binding if they are cast by a PMC member. For all other purposes,
votes are binding if they are cast by a committer. However, it is important to remember that
all participants on a list get a vote. And you are encouraged to vote, even if your vote is
not binding. This is a good way to get involved in the project and helps to inform the decision-making
process.</span>
 <p>You are encouraged to use an informal voting model to take a quick poll or to wrap
up a discussion, whether you are a committer yet or not. These votes are informal and can
be initiated by anyone. Binding votes are only needed for project-level decision-making.
 <h2>3.4. Approval Models</h2>
 <p><strong>We use four different approval models for formal voting</strong>:

Modified: couchdb/site/bylaws.v2.html
URL: http://svn.apache.org/viewvc/couchdb/site/bylaws.v2.html?rev=1615232&r1=1615231&r2=1615232&view=diff
==============================================================================
--- couchdb/site/bylaws.v2.html (original)
+++ couchdb/site/bylaws.v2.html Fri Aug  1 21:11:24 2014
@@ -6,7 +6,7 @@
 <h1>Table of Contents</h1>
 <p>TODO
 <h1>1. Introduction</h1>
-<p>This document defines the bylaws under which the Apache CouchDB&nbsp;project
operates. It defines the&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-2.RolesandResponsibilities"
data-anchor="2.RolesandResponsibilities" data-linked-resource-default-alias="2.RolesandResponsibilities"
data-base-url="https://cwiki.apache.org/confluence">roles and responsibilities</a>&nbsp;<span>within</span>&nbsp;the
project, who may vote, how&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.3.Voting"
data-anchor="3.3.Voting" data-linked-resource-default-alias="3.3.Voting" data-base-url="https://cwiki.apache.org/confluence">voting</a>&nbsp;works,
how conflicts are resolved, and voting rules for specific&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.6.DecisionTypes"
data-anchor="3.6.Decisio
 nTypes" data-linked-resource-default-alias="3.6.DecisionTypes" data-base-url="https://cwiki.apache.org/confluence">decision
types</a>.
+<p>This document defines the bylaws under which the Apache CouchDB&nbsp;project
operates. It defines the&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-2.RolesandResponsibilities">roles
and responsibilities</a>&nbsp;<span>within</span>&nbsp;the project,
who may vote, how&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.3.Voting">voting</a>&nbsp;works,
how conflicts are resolved, and voting rules for specific&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.6.DecisionTypes">decision
types</a>.
 <p>This document is written for anyone who wishes to participate in the project.&nbsp;<strong>If
this is your first time through this document, read this introduction, then read all the bolded
text</strong>&nbsp;<strong>for a summary of the bylaws.</strong>&nbsp;Then,
as you need more detail, read past the bolded text for an expanded explanation.
 <p>CouchDB is a project of the&nbsp;<em>Apache Software Foundation</em>&nbsp;(ASF).
Apache CouchDB, CouchDB, and the CouchDB logo are trademarks of the ASF. The project resources
are licensed to the public under the&nbsp;<a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache
License 2.0</a>. Releases are made in the form of official signed source code archives.&nbsp;The&nbsp;<a
href="https://www.apache.org/foundation/faq.html">ASF FAQ</a>&nbsp;explains the
operation and background of the Foundation.
 <p>CouchDB operates under a set of common principles known collectively as&nbsp;<a
href="https://www.apache.org/foundation/how-it-works.html">the Apache Way</a>:&nbsp;
@@ -24,7 +24,7 @@
 <h1>2. Roles and Responsibilities</h1>
 <p><strong>The ASF&nbsp;<a href="https://www.apache.org/foundation/how-it-works.html#roles">defines
a set of roles</a>&nbsp;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.</strong>
 <p><span>Your role is bestowed on you by your peers in recognition of your past
contributions to the project and your position of trust within the community. It is not tied
to your job, your current employer, or your current activity level. We are interested in you
as an individual and we&nbsp;understand that your interactions with the project may change
over time.</span>
-<p><span>Roles are never rescinded because of inactivity, unless that inactivity
is causing a problem for the project. Fortunately, our decision making process means that
inactivity is very rarely a problem. Roles will be rescinded if the&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-2.4.ProjectManagementCommittee"
data-anchor="2.4.ProjectManagementCommittee" data-linked-resource-default-alias="2.4.ProjectManagementCommittee"
data-base-url="https://cwiki.apache.org/confluence">Project Management Committee</a>&nbsp;(or&nbsp;<a
href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-2.4.ProjectManagementCommittee"
data-anchor="2.4.ProjectManagementCommittee" data-linked-resource-default-alias="2.4.ProjectManagementCommittee"
data-base-url="https://cwiki.apache.org/confluence">PMC</a>, see 2.4. below) believes
the individual is no longer able to responsibly disc
 harge the duty of the role.</span>
+<p><span>Roles are never rescinded because of inactivity, unless that inactivity
is causing a problem for the project. Fortunately, our decision making process means that
inactivity is very rarely a problem. Roles will be rescinded if the&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-2.4.ProjectManagementCommittee">Project
Management Committee</a>&nbsp;(or&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-2.4.ProjectManagementCommittee">PMC</a>,
see 2.4. below) believes the individual is no longer able to responsibly discharge the duty
of the role.</span>
 <p><span>We understand that you have many roles in life. We use a hat metaphor
to talk about these roles. For instance, y</span><span>ou might have your work
hat as well as several ASF hats.&nbsp;</span><span>We expect you to know when
to wear the appropriate hat, and to comport yourself in a manner befitting the interests of
the Foundation when interacting with the project. Failure to do this is a serious&nbsp;</span><span>dereliction</span><span>&nbsp;of
duty.</span>
 <p><span>Sometimes it is a good idea to tell people which hat you are wearing.
For instance, the PMC Chair might start an informal email by stating they are not wearing
the PMC Chair's hat, just to be clear about how the statements ought to be interpreted.</span>
 <p><span>We expect you to act in good faith. This is very important for a community
that depends so heavily on trust.</span>
@@ -43,7 +43,7 @@
 <li>Project (blogging, marketing, design, UX, branding, etc)
 <li>Documentation (documentation, localisation/internationalisation, etc.)
 <li>Code (new features, bug fixing, quality assurance, release management etc.)</ul>
-<p>More details are available in&nbsp;<a href="https://cwiki.apache.org/confluence/display/COUCHDB/Contributor+Guide"
data-linked-resource-id="40511227" data-linked-resource-type="page" data-linked-resource-default-alias="Contributor
Guide" data-base-url="https://cwiki.apache.org/confluence">the contributor guide</a>.
If any of these things sound interesting to you, we welcome your help.
+<p>More details are available in&nbsp;<a href="https://cwiki.apache.org/confluence/display/COUCHDB/Contributor+Guide">the
contributor guide</a>. If any of these things sound interesting to you, we welcome your
help.
 <p>The role of committer is mandated at the Foundation level. Unfortunately, the usual
definition of that word—being someone who commits code—can mean that non-coders
are never given binding votes on a project. We think that's a problem. C<span>ontributions
come in many shapes and sizes. Indeed, many of those non-code contributions are what the project
needs the most.</span>
 <p>To make this clear, we have chosen to define a committer as someone who is&nbsp;<em>committed</em>.
We mean this in the sense of being loyal to the project and its interests. It is a position
of trust, not an expectation of activity level. Anyone who is supportive of the community
and the project will be considered as a candidate for being a committer.
 <p>As a matter of convenience, committers are also given write access to all of the
public project infrastructure, including source control repositories, website, issue tracker,
wiki, and blog. Access to social media accounts, and other third-party services, will be granted
upon request.
@@ -52,7 +52,7 @@
 <p>A committer who makes a sustained contribution to the project may be invited to
become a&nbsp;<em>Project Management Committee</em>&nbsp;(PMC) member.
 <h2>2.4. Project Management Committee</h2>
 <p><strong>The&nbsp;<em>Project Management Committee</em>&nbsp;(PMC)
is responsible for the management of the project.</strong>
-<p><span>At the most basic level, the role of the PMC is oversight. The PMC must
ensure that all relevant&nbsp;</span><span>bylaws</span><span>&nbsp;</span><span>,&nbsp;</span><span>policies,
and procedures</span><span>&nbsp;</span><span>&nbsp;are adhered
to. These exist at the Foundation-level and the project-level. See the&nbsp;<a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+affairs"
data-linked-resource-id="39621747" data-linked-resource-type="page" data-linked-resource-default-alias="Project
affairs" data-base-url="https://cwiki.apache.org/confluence">project affairs</a>&nbsp;page
for more information.</span>
+<p><span>At the most basic level, the role of the PMC is oversight. The PMC must
ensure that all relevant&nbsp;</span><span>bylaws</span><span>&nbsp;</span><span>,&nbsp;</span><span>policies,
and procedures</span><span>&nbsp;</span><span>&nbsp;are adhered
to. These exist at the Foundation-level and the project-level. See the&nbsp;<a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+affairs">project
affairs</a>&nbsp;page for more information.</span>
 <p>Beyond this requirement, the primary goal of the PMC is to invest in the long term
wellbeing of the community.&nbsp;<span>For this reason, one of the most basic tasks
of the PMC is the recruitment and management of project contributors. We believe that the
size, diversity, and health of the community is essential for the quality, stability, and
robustness of project and its social structures.</span>
 <p><span>Activities</span>&nbsp;of the PMC include, but are not limited
to:
 <ul>
@@ -78,15 +78,15 @@
 <p>This section explains our approach to decision making and the formal structures
we have in place to make this as easy as possible.
 <p><strong>In descending&nbsp;order of preference, we prefer that decisions
are made via:</strong>
 <ul>
-<li><strong><a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.1.LazyConsensus"
data-anchor="3.1.LazyConsensus" data-linked-resource-default-alias="3.1.LazyConsensus" data-base-url="https://cwiki.apache.org/confluence">Lazy
consensus</a>&nbsp;or&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.5.RTCandVetos"
data-anchor="3.5.RTCandVetos" data-linked-resource-default-alias="3.5.RTCandVetos" data-base-url="https://cwiki.apache.org/confluence">RTC</a></strong>
-<li><strong><a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.2.Discussion"
data-anchor="3.2.Discussion" data-linked-resource-default-alias="3.2.Discussion" data-base-url="https://cwiki.apache.org/confluence">Discussion-led
consensus gathering</a></strong>
-<li><strong><a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.3.Voting"
data-anchor="3.3.Voting" data-linked-resource-default-alias="3.3.Voting" data-base-url="https://cwiki.apache.org/confluence">Formal
voting</a></strong></ul>
+<li><strong><a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.1.LazyConsensus">Lazy
consensus</a>&nbsp;or&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.5.RTCandVetos">RTC</a></strong>
+<li><strong><a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.2.Discussion">Discussion-led
consensus gathering</a></strong>
+<li><strong><a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.3.Voting">Formal
voting</a></strong></ul>
 <p>Our goal is to build a community of trust, reduce mailing list traffic, and deal
with disagreements swiftly when they occur.
 <p>All decision making must happen on&nbsp;<a href="https://mail-archives.apache.org/mod_mbox/#couchdb">the
mailing lists</a>. Any discussion that takes place&nbsp;away from the lists (for
example on IRC or in person) must be brought to the lists before anything can be decided.
We have a saying: if it's not on the lists, it didn't happen. We take this approach so that
the greatest&nbsp;amount of people have a chance to participate.
 <p>Decisions should be made on the mailing list associated with the decision. For example,
marketing decisions happen on&nbsp;<a href="https://mail-archives.apache.org/mod_mbox/couchdb-marketing/">the
marketing list</a>. By default, anything without a specific list should be done in public
on the main development list. Anything that needs to be private will be done on the private
list.
 <p>Our decision making processes are designed to reduce blockages. It is understood
that people come and go as time permits. It is not practical to hear from everybody on every
decision. Sometimes, this means a decision will be taken while you are away from the project.
It is reasonable to bring such decisions up for discussion again, but this should be kept
to a minimum.
 <h2>3.1. Lazy Consensus</h2>
-<p><strong>When you are convinced that you know what the community would like
to see happen, you can assume that you already have permission and get on with the work.</strong>&nbsp;<strong>We
call this&nbsp;<a href="http://www.apache.org/foundation/glossary.html#LazyConsensus">lazy
consensus</a>.</strong>&nbsp;You don't have to insist that people discuss
or approve your plan, and you certainly don't need to call a vote. Just assume your plan is
okay unless someone says otherwise. This applies to anything in the list of&nbsp;<a
href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.6.DecisionTypes"
data-anchor="3.6.DecisionTypes" data-linked-resource-default-alias="3.6.DecisionTypes" data-base-url="https://cwiki.apache.org/confluence">decision
types</a>&nbsp;in section 3.6. where lazy consensus is allowed.
+<p><strong>When you are convinced that you know what the community would like
to see happen, you can assume that you already have permission and get on with the work.</strong>&nbsp;<strong>We
call this&nbsp;<a href="http://www.apache.org/foundation/glossary.html#LazyConsensus">lazy
consensus</a>.</strong>&nbsp;You don't have to insist that people discuss
or approve your plan, and you certainly don't need to call a vote. Just assume your plan is
okay unless someone says otherwise. This applies to anything in the list of&nbsp;<a
href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.6.DecisionTypes">decision
types</a>&nbsp;in section 3.6. where lazy consensus is allowed.
 <p>"It's easier to ask forgiveness than it is to get permission." —&nbsp;Grace
Hopper
 <p>Most actions are reversible. As long as you do your work in the open, the community
has plenty of opportunities to object. If someone does object, you must be prepared to roll
back your work.
 <p><span>Lazy consensus has two effects:</span>
@@ -145,9 +145,9 @@
 <td colspan="1">-1000
 <td colspan="1">"Extremely unhappy with this proposal."
 <td colspan="1">-1</table>
-<p>There are three types of voting: informal, formal, and vetos. An informal vote is
a quick way to get people's feelings on something.&nbsp;A formal vote, on the other hand,
requires an approval model and a&nbsp;<a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws"
data-linked-resource-default-alias="Project Bylaws" data-base-url="https://cwiki.apache.org/confluence">decision
type</a>. More detail on&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.4.ApprovalModels"
data-anchor="3.4.ApprovalModels" data-linked-resource-default-alias="3.4.ApprovalModels" data-base-url="https://cwiki.apache.org/confluence">approval
models</a>,&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.5.RTCandVetos"
data-anchor="3.5.RTCandVetos" data-linked-resource-default-alias="3.5.RTCandVetos" data-base-url="https://cwiki.apache.org/confluence"
 >vetos</a>, and&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.6.DecisionTypes"
data-anchor="3.6.DecisionTypes" data-linked-resource-default-alias="3.6.DecisionTypes" data-base-url="https://cwiki.apache.org/confluence">decision
types</a>&nbsp;is available in sections 3.4, 3.5., and 3.6 respectively.
-<p>All formal voting must be done in an email thread&nbsp;with the appropriate&nbsp;<a
href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-4.1.SubjectTags"
data-anchor="4.1.SubjectTags" data-linked-resource-default-alias="4.1.SubjectTags" data-base-url="https://cwiki.apache.org/confluence">subject
tag</a>.&nbsp;Formal votes may contain multiple items for approval and these should
be clearly separated. Formal voting is then carried out by replying to the vote mail.&nbsp;<span>Formal
votes are open for a period of at least 72 hours to allow all active voters time to consider
the vote. Votes can be held open longer than this at the discretion of the person who initiated
the vote.</span>
-<p><span>Votes on&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.6.DecisionTypes"
data-anchor="3.6.DecisionTypes" data-linked-resource-default-alias="3.6.DecisionTypes" data-base-url="https://cwiki.apache.org/confluence">PMC
decisions</a>&nbsp;are binding if they are cast by a PMC member. For all other purposes,
votes are binding if they are cast by a committer. However, it is important to remember that
all participants on a list get a vote. And you are encouraged to vote, even if your vote is
not binding. This is a good way to get involved in the project and helps to inform the decision-making
process.</span>
+<p>There are three types of voting: informal, formal, and vetos. An informal vote is
a quick way to get people's feelings on something.&nbsp;A formal vote, on the other hand,
requires an approval model and a&nbsp;<a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws"
>decision type</a>. More detail on&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.4.ApprovalModels">approval
models</a>,&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.5.RTCandVetos">vetos</a>,
and&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.6.DecisionTypes">decision
types</a>&nbsp;is available in sections 3.4, 3.5., and 3.6 respectively.
+<p>All formal voting must be done in an email thread&nbsp;with the appropriate&nbsp;<a
href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-4.1.SubjectTags">subject
tag</a>.&nbsp;Formal votes may contain multiple items for approval and these should
be clearly separated. Formal voting is then carried out by replying to the vote mail.&nbsp;<span>Formal
votes are open for a period of at least 72 hours to allow all active voters time to consider
the vote. Votes can be held open longer than this at the discretion of the person who initiated
the vote.</span>
+<p><span>Votes on&nbsp;<a href="https://cwiki.apache.org/confluence/plugins/viewsource/viewpagesrc.action?pageId=40511017#ProjectBylaws-3.6.DecisionTypes">PMC
decisions</a>&nbsp;are binding if they are cast by a PMC member. For all other purposes,
votes are binding if they are cast by a committer. However, it is important to remember that
all participants on a list get a vote. And you are encouraged to vote, even if your vote is
not binding. This is a good way to get involved in the project and helps to inform the decision-making
process.</span>
 <p>You are encouraged to use an informal voting model to take a quick poll or to wrap
up a discussion, whether you are a committer yet or not. These votes are informal and can
be initiated by anyone. Binding votes are only needed for project-level decision-making.
 <h2>3.4. Approval Models</h2>
 <p><strong>We use three different approval models for formal voting</strong>:



Mime
View raw message