You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bookkeeper.apache.org by iv...@apache.org on 2014/12/12 12:03:31 UTC
svn commit: r1644860 - /bookkeeper/site/trunk/content/bylaws.textile
Author: ivank
Date: Fri Dec 12 11:03:31 2014
New Revision: 1644860
URL: http://svn.apache.org/r1644860
Log:
Formatting fixes for bylaws
Modified:
bookkeeper/site/trunk/content/bylaws.textile
Modified: bookkeeper/site/trunk/content/bylaws.textile
URL: http://svn.apache.org/viewvc/bookkeeper/site/trunk/content/bylaws.textile?rev=1644860&r1=1644859&r2=1644860&view=diff
==============================================================================
--- bookkeeper/site/trunk/content/bylaws.textile (original)
+++ bookkeeper/site/trunk/content/bylaws.textile Fri Dec 12 11:03:31 2014
@@ -1,4 +1,4 @@
-Title: BookKeeper Bylaws
+Title: Apache BookKeeper Project Bylaws
Notice: 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
@@ -16,17 +16,15 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-Apache BookKeeper Project Bylaws
-
-This is version 1 of the bylaws. Voted on 2014/12/11
+This is version 1 of the bylaws. The BookKeeper PMC ratified these bylaws by a 2/3 majority vote on 2014/12/11.
h1. Introduction
This document defines the bylaws under which the Apache BookKeeper project operates. It defines the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved, etc.
-BookKeeper is a project of the Apache Software Foundation. The foundation holds the copyright on Apache code including the code in the BookKeeper codebase. The foundation FAQ explains the operation and background of the foundation.
+BookKeeper is a project of the "Apache Software Foundation":http://www.apache.org/. The foundation holds the copyright on Apache code including the code in the BookKeeper codebase. The "foundation FAQ":http://www.apache.org/foundation/faq.html explains the operation and background of the foundation.
-BookKeeper is typical of Apache projects in that it operates under a set of principles, known collectively as the Apache Way. If you are new to Apache development, please refer to the Incubator project for more information on how Apache projects operate.
+BookKeeper is typical of Apache projects in that it operates under a set of principles, known collectively as the "Apache Way":http://incubator.apache.org/learn/theapacheway.html. If you are new to Apache development, please refer to the "Incubator project":http://incubator.apache.org for more information on how Apache projects operate.
h1. Roles and Responsibilities
@@ -50,7 +48,7 @@ Committer access is by invitation only a
Commit access can be revoked by a unanimous vote of all the active PMC members (except the committer in question if he or she is also a PMC member).
-All Apache committers are required to have a signed Contributor License Agreement on file with the Apache Software Foundation. There is a Committer FAQ which provides more details on the requirements for committers.
+All Apache committers are required to have a signed "Contributor License Agreement":http://www.apache.org/licenses/icla.txt on file with the Apache Software Foundation. There is a "Committer FAQ":http://www.apache.org/dev/committers.html which provides more details on the requirements for committers.
A committer who makes a sustained contribution to the project may be invited to become a member of the PMC. The form of contribution is not limited to code. It can also include code review, helping out users on the mailing lists, documentation, etc.
@@ -58,13 +56,13 @@ h2. Project Management Committee
The PMC is responsible to the board and the ASF for the management and oversight of the Apache BookKeeper codebase. The responsibilities of the PMC include:
- * Deciding what is distributed as products of the Apache BookKeeper project. In particular all releases must be approved by the PMC.
- * Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.
- * Speaking on behalf of the project.
- * Resolving license disputes regarding products of the project.
- * Nominating new PMC members and committers.
- * Maintaining these bylaws and other guidelines of the project.
- * Membership of the PMC is by invitation only and must be approved by a lazy consensus of active PMC members. A PMC member is considered emeritus by his or her own declaration or by not contributing in any form to the project for over six months. An emeritus member may request reinstatement to the PMC, which must be approved by a lazy consensus of active PMC members.
+* Deciding what is distributed as products of the Apache BookKeeper project. In particular all releases must be approved by the PMC.
+* Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.
+* Speaking on behalf of the project.
+* Resolving license disputes regarding products of the project.
+* Nominating new PMC members and committers.
+* Maintaining these bylaws and other guidelines of the project.
+* Membership of the PMC is by invitation only and must be approved by a lazy consensus of active PMC members. A PMC member is considered emeritus by his or her own declaration or by not contributing in any form to the project for over six months. An emeritus member may request reinstatement to the PMC, which must be approved by a lazy consensus of active PMC members.
Membership of the PMC can be revoked by an unanimous vote of all the active PMC members other than the member in question.
@@ -80,6 +78,7 @@ h2. Voting
Decisions regarding the project are made by votes on the primary project development mailing list dev@bookkeeper.apache.org. Where necessary, PMC voting may take place on the private BookKeeper PMC mailing list private@bookkeeper.apache.org. Votes are clearly indicated by subject line starting with [VOTE]. Votes may contain multiple items for approval and these should be clearly separated. Voting is carried out by replying to the vote mail. Voting may take four flavors.
+table(table).
| Vote | Meaning |
| +1 | 'Yes,' 'Agree,' or 'the action should be performed.' In general, this vote also indicates a willingness on the behalf of the voter in 'making it happen'. |
| +0 | This vote indicates a willingness for the action under consideration to go ahead. The voter, however will not be able to help. |
@@ -94,6 +93,7 @@ h2. Approvals
There are the types of approvals that can be sought. Different actions require different types of approvals.
+table(table).
| Approval Type | Definition |
| Consensus | For this to pass, all voters with binding votes must vote and there can be no binding vetoes (-1). Consensus votes are rarely required due to the impracticality of getting all eligible voters to cast a vote. |
| Lazy Consensus | Lazy consensus requires 3 binding + 1 votes and no binding vetoes. |
@@ -112,7 +112,8 @@ h2. Actions
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 business days. In general votes should not be called at times when it is known that interested members of the project will be unavailable.
-|_. Action |_. Description |_. Approval |_. Binding Votes |_. Minimum Length (days) |
+table(table).
+|_. Action |_. Description |_. Approval |_. Binding Votes |_. Min. Length (days) |
| Code Change | A change made to a codebase of the project and committed by a committer. This includes source code, documentation, website content, etc. | Lazy approval (not counting the vote of the contributor), moving to lazy majority if a -1 is received | Active committer | 1 |
| Release Plan | Defines the timetable and actions for a release. The plan also nominates a Release Manager. | Lazy majority | Active committers | 3 |
| Product Release | When a release of one of the project's products is ready, a vote is required to accept the release as an official release of the project. | Lazy Majority| Active PMC members | 3 |