Author: ptgoetz
Date: Fri Mar 20 04:04:51 2015
New Revision: 1667927
URL: http://svn.apache.org/r1667927
Log:
add missed generated file
Added:
storm/site/publish/documentation/BYLAWS.html
Added: storm/site/publish/documentation/BYLAWS.html
URL:
http://svn.apache.org/viewvc/storm/site/publish/documentation/BYLAWS.html?rev=1667927&view=auto
==============================================================================
--- storm/site/publish/documentation/BYLAWS.html (added)
+++ storm/site/publish/documentation/BYLAWS.html Fri Mar 20 04:04:51 2015
@@ -0,0 +1,324 @@
+<!DOCTYPE html>
+<html>
+
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <meta name="description" content="">
+ <meta name="author" content="">
+ <link rel="icon" href="/assets/favicon.ico">
+
+ <title>Apache Storm Project Bylaws</title>
+
+ <!-- Bootstrap core CSS -->
+ <link href="/assets/css/bootstrap.min.css" rel="stylesheet">
+ <!-- Bootstrap theme -->
+ <link href="/assets/css/bootstrap-theme.min.css" rel="stylesheet">
+
+ <!-- Custom styles for this template -->
+ <link href="/assets/css/theme.css" rel="stylesheet">
+
+ <link href="/css/main.css" rel="stylesheet">
+
+ <!-- Just for debugging purposes. Don't actually copy these 2 lines! -->
+ <!--[if lt IE 9]><script
src="../../assets/js/ie8-responsive-file-warning.js"></script><![endif]-->
+ <script src="/assets/js/ie-emulation-modes-warning.js"></script>
+
+ <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media
queries -->
+ <!--[if lt IE 9]>
+ <script
src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js";></script>
+ <script
src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js";></script>
+ <![endif]-->
+ </head>
+
+
+
+ <body>
+ <div class="container">
+ <!-- Fixed navbar -->
+ <nav class="navbar navbar-default navbar-fixed-top" role="navigation">
+ <div class="container">
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle collapsed"
data-toggle="collapse" data-target="#navbar" aria-expanded="false"
aria-controls="navbar">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <a class="navbar-brand" href="/">Apache Storm<!-- <img alt="Apache
Storm" src="/images/storm_logo_tagline_color.png"></a> -->
+ </div>
+ <div id="navbar" class="navbar-collapse collapse">
+ <ul class="nav navbar-nav">
+ <li><a href="/">Home</a></li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown"
role="button" aria-expanded="false">About<span class="caret"></span></a>
+ <ul class="dropdown-menu" role="menu">
+ <li><a href="/about/integrates.html">About</a></li>
+ <li><a
href="/documentation/Contributing-to-Storm.html">Contributing</a></li>
+ <li><a href="/documentation/BYLAWS.html">Bylaws</a></li>
+ </ul>
+ </li>
+ <li><a href="/downloads.html">Download</a></li>
+ <li><a href="/documentation/Home.html">Documentation</a></li>
+ <li><a href="/news.html">News</a></li>
+ </ul>
+ </div><!--/.nav-collapse -->
+ </div>
+ </nav>
+
+
+
+
+
+ <!-- Documentation -->
+<!-- <div class="container"> -->
+
+ <header class="post-header">
+ <h1 class="post-title">Apache Storm Project Bylaws</h1>
+ <p class="post-meta"></p>
+ </header>
+
+ <article class="post-content">
+ <h2 id="roles-and-responsibilities">Roles and Responsibilities</h2>
+
+<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>
+
+<h3 id="users:">Users:</h3>
+
+<p>The most important participants in the project are people who use our
software. The majority of our developers start out as users and guide their
development efforts from the user's perspective.</p>
+
+<p>Users contribute to the Apache projects by providing feedback to developers
in the form of bug reports and feature suggestions. As well, users participate
in the Apache community by helping other users on mailing lists and user
support forums.</p>
+
+<h3 id="contributors:">Contributors:</h3>
+
+<p>Contributors are all of the volunteers who are contributing time, code,
documentation, or resources to the Storm Project. 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>
+
+<h3 id="committers:">Committers:</h3>
+
+<p>The project's Committers are responsible for the project's
technical management. Committers have access to all project source
repositories. Committers may cast binding votes on any technical discussion
regarding storm.</p>
+
+<p>Committer access is by invitation only and must be approved by lazy
consensus of the active PMC members. A Committer is considered emeritus by
their own declaration or by not contributing in any form to the project for
over six months. An emeritus Committer may request reinstatement of commit
access from the PMC. Such reinstatement is subject to lazy consensus approval
of active PMC members.</p>
+
+<p>All Apache Committers are required to have a signed Contributor License
Agreement (CLA) on file with the Apache Software Foundation. There is a <a
href="https://www.apache.org/dev/committers.html";>Committers' FAQ</a> which
provides more details on the requirements for Committers.</p>
+
+<p>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, testing, etc.</p>
+
+<h3 id="project-management-committee(pmc):">Project Management
Committee(PMC):</h3>
+
+<p>The PMC is responsible to the board and the ASF for the management and
oversight of the Apache Storm codebase. The responsibilities of the PMC
include:</p>
+
+<ul>
+<li>Deciding what is distributed as products of the Apache Storm project. In
particular all releases must be approved by the PMC.</li>
+<li>Maintaining the project's shared resources, including the codebase
repository, mailing lists, websites.</li>
+<li>Speaking on behalf of the project.</li>
+<li>Resolving license disputes regarding products 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>Membership of the PMC is by invitation only and must be approved by a
consensus approval of active PMC members. A PMC member is considered
"emeritus" by their 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. Such reinstatement is subject to consensus approval
of the active PMC members.</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 Storm) and has
primary responsibility to the board for the management of the projects within
the scope of the Storm PMC. The chair reports to the board quarterly on
developments within the Storm project.</p>
+
+<p>The chair of the PMC is rotated annually. When the chair is rotated or if
the current chair of the PMC resigns, the PMC votes to recommend a new chair
using Single Transferable Vote (STV) voting. See <a
href="http://wiki.apache.org/general/BoardVoting";>http://wiki.apache.org/general/BoardVoting</a>
for specifics. The decision must be ratified by the Apache board.</p>
+
+<h2 id="voting">Voting</h2>
+
+<p>Decisions regarding the project are made by votes on the primary project
development mailing list (<a
href="mailto:[email protected]";>[email protected]</a>). Where
necessary, PMC voting may take place on the private Storm PMC mailing list.
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:</p>
+
+<table><thead>
+<tr>
+<th>Vote</th>
+<th>Meaning</th>
+</tr>
+</thead><tbody>
+<tr>
+<td>+1</td>
+<td>'Yes,' 'Agree,' or 'the action should be
performed.'</td>
+</tr>
+<tr>
+<td>+0</td>
+<td>Neutral about the proposed action.</td>
+</tr>
+<tr>
+<td>-0</td>
+<td>Mildly negative, but not enough so to want to block it.</td>
+</tr>
+<tr>
+<td>-1</td>
+<td>This is a negative vote. 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 Storm project are encouraged to show their
agreement with or against a particular action by voting. 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 in the wider Storm community. For PMC decisions, only the votes of
active PMC members are binding.</p>
+
+<p>Voting can also be applied to changes already made to the Storm codebase.
These typically take the form of a veto (-1) in reply to the commit message
sent when the commit is made. Note that this should be a rare occurrence. All
efforts should be made to discuss issues when they are still patches before the
code is committed.</p>
+
+<p>Only active (i.e. non-emeritus) Committers and PMC members have binding
votes.</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><thead>
+<tr>
+<th>Approval Type</th>
+<th>Criteria</th>
+</tr>
+</thead><tbody>
+<tr>
+<td>Consensus Approval</td>
+<td>Consensus approval requires 3 binding +1 votes and no binding vetoes.</td>
+</tr>
+<tr>
+<td>Majority Approval</td>
+<td>Majority approval requires at least 3 binding +1 votes and more +1 votes
than -1 votes.</td>
+</tr>
+<tr>
+<td>Lazy Consensus</td>
+<td>Lazy consensus requires no -1 votes ('silence gives assent').</td>
+</tr>
+<tr>
+<td>2/3 Majority</td>
+<td>2/3 majority votes requires at least 3 votes and twice as many +1 votes as
-1 votes.</td>
+</tr>
+</tbody></table>
+
+<h3 id="vetoes">Vetoes</h3>
+
+<p>A valid, binding veto cannot be overruled. If a veto is cast, it must be
accompanied by a valid reason explaining the reasons for the veto. The validity
of a veto, if challenged, can be confirmed by anyone who has a binding vote.
This does not necessarily signify agreement with the veto - merely that the
veto is valid.</p>
+
+<p>If you disagree with a valid veto, you must lobby the person casting the
veto to withdraw their veto. If a veto is not withdrawn, any 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.</p>
+
+<table><thead>
+<tr>
+<th>Actions</th>
+<th>Description</th>
+<th>Approval</th>
+<th>Binding Votes</th>
+<th>Minimum Length</th>
+<th>Mailing List</th>
+</tr>
+</thead><tbody>
+<tr>
+<td>Code Change</td>
+<td>A change made to a source code of the project and committed by a
Committer.</td>
+<td>A minimum of one +1 from a Committer other than the one who authored the
patch, and no -1s. The code can be committed after the first +1. If a -1 is
received to the patch within 7 days after the patch was posted, it may be
reverted immediately if it was already merged.</td>
+<td>Active Committers</td>
+<td>1 day from initial patch (<strong>Note:</strong> Committers should
consider allowing more time for review based on the complexity and/or impact of
the patch in question.)</td>
+<td>JIRA or Github pull ( with notification sent to <a
href="mailto:[email protected]";>[email protected]</a>)</td>
+</tr>
+<tr>
+<td>Non-Code Change</td>
+<td>A change made to a repository of the project and committed by a Committer.
This includes documentation, website content, etc., but not source code, unless
only comments are being modified.</td>
+<td>Lazy Consensus</td>
+<td>Active Committers</td>
+<td>At the discression of the Committer</td>
+<td>JIRA or Github pull (with notification sent to <a
href="mailto:[email protected]";>[email protected]</a>)</td>
+</tr>
+<tr>
+<td>Product Release</td>
+<td>A vote is required to accept a proposed release as an official release of
the project. Any Committer may call for a release vote at any point in
time.</td>
+<td>Majority Approval</td>
+<td>Active PMC members</td>
+<td>3 days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></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 and
submodules within the project as well as merging of feature branches.</td>
+<td>2/3 Majority</td>
+<td>Active PMC members</td>
+<td>6 days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></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 days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></td>
+</tr>
+<tr>
+<td>New PMC Member</td>
+<td>When a member is proposed for the PMC.</td>
+<td>Consensus Approval</td>
+<td>Active PMC members</td>
+<td>3 days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></td>
+</tr>
+<tr>
+<td>Emeritus PMC Member re-instatement</td>
+<td>When an emeritus PMC member requests to be re-instated as an active PMC
member.</td>
+<td>Consensus Approval</td>
+<td>Active PMC members</td>
+<td>6 days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></td>
+</tr>
+<tr>
+<td>Emeritus Committer re-instatement</td>
+<td>When an emeritus Committer requests to be re-instated as an active
Committer.</td>
+<td>Consensus Approval</td>
+<td>Active PMC members</td>
+<td>6 days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></td>
+</tr>
+<tr>
+<td>Committer Removal</td>
+<td>When removal of commit privileges is sought. Note: Such actions will also
be referred to the ASF board by the PMC chair.</td>
+<td>2/3 Majority</td>
+<td>Active PMC members (excluding the Committer in question if a member of the
PMC).</td>
+<td>6 Days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></td>
+</tr>
+<tr>
+<td>PMC Member Removal</td>
+<td>When removal of a PMC member is sought. Note: Such actions will also be
referred to the ASF board by the PMC chair.</td>
+<td>2/3 Majority</td>
+<td>Active PMC members (excluding the member in question).</td>
+<td>6 Days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></td>
+</tr>
+<tr>
+<td>Modifying Bylaws</td>
+<td>Modifying this document.</td>
+<td>2/3 Majority</td>
+<td>Active PMC members</td>
+<td>6 Days</td>
+<td><a href="mailto:[email protected]";>[email protected]</a></td>
+</tr>
+</tbody></table>
+
+ </article>
+
+<!-- </div> -->
+
+
+
+ <hr/>
+<div id="footer" class="container text-center">
+
+ <p class="text-muted credit"><p>
+Copyright © 2014 <a href="http://www.apache.org";>Apache Software
Foundation</a>. All Rights Reserved. Apache Storm, Apache, the Apache feather
logo, and the Apache Storm project logos are trademarks of The Apache Software
Foundation. All other marks mentioned may be trademarks or registered
trademarks of their respective owners.</p>
+
+</div>
+
+ <!-- Bootstrap core JavaScript
+ ================================================== -->
+ <!-- Placed at the end of the document so the pages load faster -->
+ <script
src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js";></script>
+ <script src="/assets/js/bootstrap.min.js"></script>
+ <script src="/assets/js/docs.min.js"></script>
+ <!-- IE10 viewport hack for Surface/desktop Windows 8 bug -->
+ <script src="/assets/js/ie10-viewport-bug-workaround.js"></script>
+ </div>
+
+ </body>
+
+</html>
