You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by ns...@apache.org on 2014/08/01 23:20:49 UTC
svn commit: r1615235 - in /couchdb/site: bylaws.v1.html bylaws.v2.html
Author: nslater
Date: Fri Aug 1 21:20:49 2014
New Revision: 1615235
URL: http://svn.apache.org/r1615235
Log:
Remove br elements
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=1615235&r1=1615234&r2=1615235&view=diff
==============================================================================
--- couchdb/site/bylaws.v1.html (original)
+++ couchdb/site/bylaws.v1.html Fri Aug 1 21:20:49 2014
@@ -2,7 +2,7 @@
<body>
<p>
-<p><em>These bylaws were officially adopted by the CouchDB PMC as of 2014-07-27 23:59 UTC.<br></em>
+<p><em>These bylaws were officially adopted by the CouchDB PMC as of 2014-07-27 23:59 UTC.</em>
<h1>Table of Contents</h1>
<p>TODO
<h1>1. Introduction</h1>
@@ -64,14 +64,14 @@
<li>Branding and events coordination
<li>Press and analyst relations</ul>
<p>PMC members are held to a much higher standard than regular community members. This includes strict hat wearing, equitable decision making, and exemplary conduct. People look to PMC members for cues about how to behave. It is important that all PMC members understand the responsibility that they bear, and that they are individually committed to improving themselves and the project.
-<p>While security issues and release management are worked by the PMC, the PMC typically delegates responsibility to the CouchDB committers.<br>
+<p>While security issues and release management are worked by the PMC, the PMC typically delegates responsibility to the CouchDB committers.
<h2>2.5. Chair</h2>
<p><strong>The project Chair is a PMC member responsible for Foundation level administrative tasks.</strong> It is not a technical leadership position, meaning the Chair has no special say in ordinary project decisions. But we do think of it as a cultural leadership position. Accordingly, position on cultural issues is something to consider when electing a Chair.
<p>The Chair is elected by the PMC but appointed by the ASF Board via a Board resolution. The Chair is an officer of the Apache Software Foundation (with an official title of <em>Vice President, Apache CouchDB</em>) and has primary responsibility to the Board for the management of the project. The Chair is the eyes and ears of the Board, and reports quarterly on developments within the project.
<p>The chair has primary responsibility to the Board, and has the power to establish rules and procedures for the day to day management of the communities for which the PMC is responsible, including the composition of the PMC itself.
<p>Remember that, as in any meeting, the chair is a facilitator and their role within the PMC is to ensure that everyone has a chance to be heard and to enable meetings to flow smoothly. There is no concept of "leader" in the Apache way.
<p>If the current Chair resigns, or the term of the Chair expires, the PMC will hold a Chair election.
-<p>The Chair has a 12 month term. The intention of this term is to allow for a rotation of the role amongst the PMC members. This does not prohibit the PMC from selecting the same Chair to serve consecutive terms.<br>
+<p>The Chair has a 12 month term. The intention of this term is to allow for a rotation of the role amongst the PMC members. This does not prohibit the PMC from selecting the same Chair to serve consecutive terms.
<h2>2.6. Board of Directors</h2>
<p><strong>The Chair is responsible for the project to the Board of Directors (the Board) of the ASF.</strong> The Board is the nine-person legal governing body of the ASF, elected by the <a href="http://apache.org/foundation/members.html">members</a> of the Foundation. The Board provides the oversight of the Foundation's activities and operation, and has the responsibility of applying and enforcing the <a href="http://apache.org/foundation/bylaws.html">ASF's bylaws</a>.
<h1>3. Decision Making</h1>
@@ -145,14 +145,14 @@
<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. 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>
+<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. 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.
<p>All formal voting must be done in an email thread with the appropriate <a href="https://cwiki.apache.org/confluence/display/COUCHDB/Project+Bylaws#ProjectBylaws-4.1.SubjectTags">subject tag</a>. 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. 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.
<p>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.
<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>:
<ul>
-<li>RTC (see section 3.5)<br>
+<li>RTC (see section 3.5)
<ul>
<li>Requires one binding +1 vote and no vetos</ul>
<li>Majority approval
Modified: couchdb/site/bylaws.v2.html
URL: http://svn.apache.org/viewvc/couchdb/site/bylaws.v2.html?rev=1615235&r1=1615234&r2=1615235&view=diff
==============================================================================
--- couchdb/site/bylaws.v2.html (original)
+++ couchdb/site/bylaws.v2.html Fri Aug 1 21:20:49 2014
@@ -2,7 +2,7 @@
<body>
<p>
-<p><em>These bylaws were officially adopted by the CouchDB PMC as of 2014-07-27 23:59 UTC and last modified on 2014-07-31 14:00 UTC.<br></em>
+<p><em>These bylaws were officially adopted by the CouchDB PMC as of 2014-07-27 23:59 UTC and last modified on 2014-07-31 14:00 UTC.</em>
<h1>Table of Contents</h1>
<p>TODO
<h1>1. Introduction</h1>
@@ -65,14 +65,14 @@
<li>Branding and events coordination
<li>Press and analyst relations</ul>
<p>PMC members are held to a much higher standard than regular community members. This includes strict hat wearing, equitable decision making, and exemplary conduct. People look to PMC members for cues about how to behave. It is important that all PMC members understand the responsibility that they bear, and that they are individually committed to improving themselves and the project.
-<p>While security issues and release management are the responsibility of the PMC, the PMC typically delegates this to committers.<br>
+<p>While security issues and release management are the responsibility of the PMC, the PMC typically delegates this to committers.
<h2>2.5. Chair</h2>
<p><strong>The project Chair is a PMC member responsible for Foundation level administrative tasks.</strong> It is not a technical leadership position, meaning the Chair has no special say in ordinary project decisions. But we do think of it as a cultural leadership position. Accordingly, position on cultural issues is something to consider when electing a Chair.
<p>The Chair is elected by the PMC but appointed by the ASF Board via a Board resolution. The Chair is an officer of the Apache Software Foundation (with an official title of <em>Vice President, Apache CouchDB</em>) and has primary responsibility to the Board for the management of the project. The Chair is the eyes and ears of the Board, and reports quarterly on developments within the project.
<p>The chair has primary responsibility to the Board, and has the power to establish rules and procedures for the day to day management of the communities for which the PMC is responsible, including the composition of the PMC itself.
<p>Remember that, as in any meeting, the Chair is a facilitator and their role within the PMC is to ensure that everyone has a chance to be heard and to enable meetings to flow smoothly.
<p>If the current Chair resigns, or the term of the Chair expires, the PMC will hold a Chair election.
-<p>The Chair has a 12 month term. The intention of this term is to allow for a rotation of the role amongst the PMC members. This does not prohibit the PMC from selecting the same Chair to serve consecutive terms.<br>
+<p>The Chair has a 12 month term. The intention of this term is to allow for a rotation of the role amongst the PMC members. This does not prohibit the PMC from selecting the same Chair to serve consecutive terms.
<h2>2.6. Board of Directors</h2>
<p><strong>The Chair is responsible for the project to the Board of Directors (the Board) of the ASF.</strong> The Board is the nine-person legal governing body of the ASF, elected by the <a href="http://apache.org/foundation/members.html">members</a> of the Foundation. The Board provides the oversight of the Foundation's activities and operation, and has the responsibility of applying and enforcing the <a href="http://apache.org/foundation/bylaws.html">ASF's bylaws</a>.
<h1>3. Decision Making</h1>
@@ -153,10 +153,10 @@
<h2>3.4. Approval Models</h2>
<p><strong>We use three different approval models for formal voting</strong>:
<ul>
-<li>RTC (see section 3.5)<br>
+<li>RTC (see section 3.5)
<ul>
<li>Requires one binding +1 vote and no vetos</ul>
-<li>Lazy majority<br>
+<li>Lazy majority
<ul>
<li>Requires three binding +1 votes and more binding +1 votes than binding -1 votes</ul>
<li>Lazy 2/3 majority