cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r863028 - in /websites/staging/cloudstack/trunk/content: ./ bylaws.html
Date Fri, 24 May 2013 20:31:11 GMT
Author: buildbot
Date: Fri May 24 20:31:11 2013
New Revision: 863028

Log:
Staging update by buildbot for cloudstack

Added:
    websites/staging/cloudstack/trunk/content/bylaws.html
Modified:
    websites/staging/cloudstack/trunk/content/   (props changed)

Propchange: websites/staging/cloudstack/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri May 24 20:31:11 2013
@@ -1 +1 @@
-1486189
+1486210

Added: websites/staging/cloudstack/trunk/content/bylaws.html
==============================================================================
--- websites/staging/cloudstack/trunk/content/bylaws.html (added)
+++ websites/staging/cloudstack/trunk/content/bylaws.html Fri May 24 20:31:11 2013
@@ -0,0 +1,338 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <title>Apache CloudStack Project Bylaws</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+
+    <link href="/css/bootstrap.css" rel="stylesheet">
+    <link href="/css/bootstrap-responsive.css" rel="stylesheet">
+    <link href="/css/font-awesome.css" rel="stylesheet">
+
+    
+
+    
+    
+        <!-- Twitter Bootstrap and jQuery after this line. -->
+        <script src="http://code.jquery.com/jquery-latest.js"></script>
+        <script src="js/bootstrap.js"</script>
+        <script>
+            $('.dropdown-toggle').dropdown();
+            $('.nav-collapse').collapse();
+        </script>
+  </head>
+  <body>
+
+    <div class="navbar navbar-inverse navbar-fixed-top">
+      <div class="navbar-inner">
+          <a href="/index.html"><img class="logo" src="/images/logo-sm.png"></a>
+          <div class="navbar-search">
+              <form name="search" id="search" action="http://www.google.com/search" method="get">
+                  <input value="cloudstack.apache.org" name="sitesearch" type="hidden"/>

+                  <input class="span2" type="text" name="q" id="query">
+                  <button type="submit" id="submit">Search <i class="icon-search"></i></button>
+              </form>
+          </div>
+      </div>
+    </div>
+
+    <header class="main" id="overview">
+    <div class="container">
+    </div>
+    </header>
+
+    <div class="container-fluid">
+        <div class="row-fluid">
+            <div class="span3">
+                <ul class="nav nav-list navbar well">
+                    <li>
+                    <h4>Sitemap
+                        <i class="icon-sitemap"></i>
+                    </h4></li>
+                    <hr>
+                    <li><h5>Apache CloudStack</h5></li>
+                    <li><a href="http://cloudstack.apache.org/downloads.html">
+                        <i class="icon-chevron-right"></i>
+                    Downloads</a></li>
+                    <li><a href="https://blogs.apache.org/cloudstack/">
+                        <i class="icon-chevron-right"></i>
+                    News</a></li>
+                    <li><a href="http://cloudstack.apache.org/about.html">
+                        <i class="icon-chevron-right"></i>
+                        About</a></li>
+                    <li><a href="http://cloudstack.apache.org/who.html">
+                        <i class="icon-chevron-right"></i>
+                        Who We Are</a></li>
+                <hr>
+                <li><h5>Community</h5></li>
+                <li><a href="http://cloudstack.apache.org/contribute.html">
+                    <i class="icon-chevron-right"></i>
+                    Get Involved
+                </a></li>
+                <li><a href="http://cloudstack.apache.org/cloudstack-faq.html">
+                    <i class="icon-chevron-right"></i>
+                    CloudStack FAQ
+                </a></li>
+                <li><a href="http://cloudstack.apache.org/mailing-lists.html">
+                    <i class="icon-chevron-right"></i>
+                    Mailing Lists</a></li>
+                <li><a href="http://lanyrd.com/topics/apache-cloudstack/">
+                    <i class="icon-chevron-right"></i>
+                    Events &amp; Meetups</a></li>
+                <hr>
+                <li><h5>Development</h5></li>
+                <li><a href="http://cloudstack.apache.org/develop/environment.html">
+                    <i class="icon-chevron-right"></i>
+                    Development Environment</a></li>
+                <li><a href="http://cloudstack.apache.org/develop/non-committer.html">
+                    <i class="icon-chevron-right"></i>
+                    Contributing for Non-Committers</a></li>
+                <li><a href="http://cloudstack.apache.org/develop/developer-faq.html">
+                    <i class="icon-chevron-right"></i>
+                    Developer's FAQ</a></li>
+                <li><a href="http://cloudstack.apache.org/develop/coding-conventions.html">
+                    <i class="icon-chevron-right"></i>
+                    Coding Conventions</a></li>
+                <hr>
+                <li><h5>Documentation</h5></li>
+                <li><a href="http://cloudstack.apache.org/docs">
+                    <i class="icon-chevron-right"></i>
+                    CloudStack Documentation</a></li>
+                <li><a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Home">
+                    <i class="icon-chevron-right"></i>
+                    Apache CloudStack Wiki</a></li>
+                <li><a href="http://cloudstack.apache.org/docs/api/index.html">
+                    <i class="icon-chevron-right"></i>
+                    API Documentation</a></li>
+                <hr>
+                <li><h5>Apache Software Foundation</h5></li>
+                <li><a href="http://www.apache.org/">
+                    <i class="icon-chevron-right"></i>
+                    Apache Software Foundation</a></li>
+                <li><a href="http://www.apache.org/foundation/thanks.html">
+                    <i class="icon-chevron-right"></i>
+                    ASF Sponsors</a></li>
+                <li><a href="http://www.apache.org/security/">
+                    <i class="icon-chevron-right"></i>
+                    Security</a></li>
+                </ul>
+            </div>
+            <div class="span9">
+        <p> <h1 id="1-introduction">1. Introduction</h1>
+<p>1.1. This document defines the bylaws under which the Apache CloudStack project
+operates. It defines the roles and responsibilities of the project, who may
+vote, how voting works, how conflicts are resolved and specifies the rules for
+specific project actions.</p>
+<p>1.2. CloudStack is a project of the Apache Software Foundation. The foundation
+holds the trademark on the name "CloudStack" and copyright on Apache code
+including the code in the CloudStack codebase. The foundation FAQ explains the
+operation and background of the foundation.</p>
+<p>1.3. CloudStack operates under a set of principles known collectively as the
+"Apache Way". Those principles are: Transparancy, consensus, non-affiliation,
+respect for fellow developers, and meritocracy, in no specific order.</p>
+<h1 id="2-roles-and-responsibilities">2. 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>2.1. Users</p>
+<p>The most important participants in the project are people who use our software.
+Users can contribute to the Apache projects by providing feedback to
+developers in
+the form of bug reports and feature suggestions. As well, users can
+participate in
+the Apache community by helping other users on mailing lists and user support
+forums. Users who participate in the project through any mechanism are
+considered
+to be Contributors.</p>
+<p>2.2. Contributors</p>
+<p>Contributors are all of the volunteers who are contributing time, code,
+documentation, or resources to the CloudStack Project. Contributions are not
+just code, but can be any combination of documentation, testing, user support,
+code, code reviews, bug reporting, community organizing, project marketing, or
+numerous other activities that help promote and improve the Apache CloudStack
+project and community.</p>
+<p>A Contributor that makes sustained, welcome contributions to the project may be
+invited to become a Committer by the PMC. The invitation will be at the
+discretion of a supporting PMC member.</p>
+<p>2.3. Committers</p>
+<p>The project's Committers are responsible for the project's technical management.
+Committers have access to all project source control repositories. Committers
+may cast binding votes on any technical discussion regarding the project (or any
+sub-project).</p>
+<p>2.3.1. Committer access is by invitation only and must be approved by a lazy
+consensus of the active PMC members.</p>
+<p>2.3.2. All Apache Committers are required to have a signed Individual
+Contributor License Agreement (ICLA) on file with the Apache Software
+Foundation. There is a Committer FAQ which provides more details on the
+requirements for Committers at Apache.</p>
+<p>2.3.3. A Committer who makes a sustained contribution to the project may be
+invited by the PMC to become a member of the PMC, after approval of the PMC.</p>
+<p>2.4. Project Management Committee</p>
+<p>The Project Management Committee (PMC) for Apache CloudStack is responsible to
+the board and the ASF for the management and oversight of the Apache CloudStack
+codebase.</p>
+<p>2.4.1. The responsibilities of the PMC include:</p>
+<p>2.4.1.1. Fostering, supporting and growing the project's community.</p>
+<p>2.4.1.2. Deciding what is distributed as products of the Apache CloudStack
+project. In particular all releases must be approved by the PMC.</p>
+<p>2.4.1.3. Maintaining the project's shared resources, including the codebase
+repository, mailing lists, websites.</p>
+<p>2.4.1.4. Speaking on behalf of the project.</p>
+<p>2.4.1.5. Resolving license disputes regarding products of the project.</p>
+<p>2.4.1.6. Nominating new PMC members and committers.</p>
+<p>2.4.1.7. Maintaining these bylaws and other guidelines of the project.</p>
+<p>2.4.2. Membership of the PMC is by invitation only and must be approved by a
+lazy consensus of active PMC members.</p>
+<p>2.4.3. A PMC member is considered "emeritus" by their own declaration. An
+emeritus member may request reinstatement to the PMC. Such reinstatement is
+subject to lazy consensus of the active PMC members.</p>
+<p>2.4.4. "Active PMC members" are all non-emeritus PMC members.</p>
+<p>2.4.4. 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
+CloudStack) and has primary responsibility to the board for the management of
+the projects within the scope of the CloudStack PMC. The chair reports to the
+board quarterly on developments within the CloudStack project. The chair must
+be an active PMC member.</p>
+<p>2.4.5. If the current chair of the PMC resigns, or the term of the
+current chair expires, the PMC will attempt to reach consensus on a new
+chair through discussion, confirming that consensus via a vote to
+recommend a new chair using a lazy 2/3 majority voting method.
+In the case that consensus is not achieved, the PMC
+will vote for a chair using Single Transferable Vote (STV) voting.
+Due to the fact that the discussions are about specific individuals,
+this vote would be held on the cloudstack-private mailing list.
+The decision must be ratified by the Apache board.</p>
+<p>2.4.6. The role of PMC chair will have a one year term.  The intention
+of this term is to allow for a rotation of the role amongst the PMC
+members.  This intention does not prohibit the PMC from selecting the
+same chair to serve consecutive terms.</p>
+<h1 id="3-decision-making">3. Decision Making</h1>
+<p>This section defines how voting is performed, the types of approvals, and which
+types of decision require which type of approval.</p>
+<p>3.1. Voting</p>
+<p>3.1.1. Decisions regarding the project are made by votes on the primary project
+development mailing list (dev@cloudstack.apache.org). Where necessary,
+PMC voting may take place on the private CloudStack 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.</p>
+<p>3.1.2. Voting may take four flavors:</p>
+<p>3.1.2.1. +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"</p>
+<p>3.1.2.2. +0 This vote indicates a willingness for the action under consideration
+to go ahead. The voter, however will not be able to help.</p>
+<p>3.1.2.3. -0 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.</p>
+<p>3.1.2.4. -1 This is a negative vote. On issues where consensus is required, this
+vote counts as a veto if binding. 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.</p>
+<p>3.1.3. All participants in the CloudStack 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 CloudStack community. For PMC decisions, only the votes of
+PMC members are binding.</p>
+<p>3.1.4. Voting can also be applied to changes made to the CloudStack codebase.
+These typically take the form of a veto (-1) in reply to the commit message sent
+when the commit is made.</p>
+<p>3.1.5. Non-binding -1 votes are not considered to be vetos for any decision.</p>
+<p>3.2. Approvals</p>
+<p>There are three types of approvals that can be sought. Section 3.4 describes
+actions and types of approvals needed for each action.</p>
+<p>3.2.1. Lazy Consensus - Lazy consensus requires 3 binding +1 votes and no
+binding -1 votes.</p>
+<p>3.2.2. Lazy Majority - A lazy majority vote requires 3 binding +1 votes and more
+binding +1 votes than binding -1 votes.</p>
+<p>3.2.3. Lazy 2/3 Majority - Lazy 2/3 majority votes requires at least 3 binding
+votes and twice as many binding +1 votes as binding -1 votes.</p>
+<p>3.3. Vetoes</p>
+<p>3.3.1. Vetoes are only possible in a lazy consensus vote.</p>
+<p>3.3.2. 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>3.3.3. 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>
+<p>3.4. Actions</p>
+<p>This section describes the various actions which are undertaken within the
+project, the roles that have the right to start a vote on the action, the
+corresponding approval required for that action and those who have binding
+votes over the action.</p>
+<p>3.4.1. Technical Decisions</p>
+<p>Technical decisions should normally be made by the entire community
+using consensus&nbsp;gathering, and not through formal voting.</p>
+<p>Technical decisions must be made on a project development mailing list.</p>
+<p>During the consensus gathering process, technical decisions may be vetoed by any
+Committer with a valid reason.</p>
+<p>If a formal vote is started for a technical decision, the vote will be held as a
+lazy&nbsp;consensus&nbsp;of active committers.</p>
+<p>Any user, contributor, committer or PMC member can initiate a technical desicion
+making process.</p>
+<p>3.4.2. Release Plan</p>
+<p>Defines the timetable and work items for a release. The plan also nominates a
+Release Manager.</p>
+<p>A lazy majority of active committers is required for approval.</p>
+<p>Any active committer or PMC member may call a vote. The vote must occur on a
+project development mailing list.</p>
+<p>3.4.3. Product Release</p>
+<p>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.</p>
+<p>Lazy Majority of active PMC members is required for approval.</p>
+<p>Any active committer or PMC member may call a vote. The vote must occur on a
+project development mailing list.</p>
+<p>3.4.4. Adoption of New Codebase</p>
+<p>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.</p>
+<p>This also covers the creation of new sub-projects within the project.</p>
+<p>Lazy 2/3 majority of active PMC members.</p>
+<p>Any active committer or PMC member may call a vote. The vote must occur on a
+project development mailing list.</p>
+<p>3.4.5. New Committer</p>
+<p>When a new committer is proposed for the project.</p>
+<p>Lazy consensus of active PMC members.</p>
+<p>Any active PMC member may call a vote. The vote must occur on the PMC private
+mailing list.</p>
+<p>3.4.6. New PMC Member</p>
+<p>When a committer is proposed for the PMC.</p>
+<p>Lazy consensus of active PMC members.</p>
+<p>Any active PMC member may call a vote. The vote must occur on the PMC private
+mailing list.</p>
+<p>3.4.7. Committer Removal</p>
+<p>When removal of commit privileges is sought. Note: Such actions will also be
+referred to the ASF board by the PMC chair</p>
+<p>Lazy 2/3 majority of active PMC members (excluding the committer in question if
+a member of the PMC).</p>
+<p>Any active PMC member may call a vote. The vote must occur on the PMC private
+mailing list.</p>
+<p>3.4.8. PMC Member Removal</p>
+<p>When removal of a PMC member is sought. Note: Such actions will also be referred
+to the ASF board by the PMC chair.</p>
+<p>Lazy 2/3 majority of active PMC members (excluding the member in question)</p>
+<p>Any active PMC member may call a vote. The vote must occur on the PMC private
+mailing list.</p>
+<p>3.4.9. Modifying Bylaws</p>
+<p>Modifying this document.</p>
+<p>Lazy majority of active PMC members</p>
+<p>Any active committer or PMC member may call a vote. The vote must occur on a
+project development mailing list.</p>
+<p>3.5. Voting Timeframes</p>
+<p>Formal votes are open for a period of at least 72 hours to allow all active
+voters time to consider the vote.</p> </p>
+            </div>
+        </div>
+
+      <hr>
+      <footer>
+      <p>Copyright © 2013 The Apache Software Foundation, Licensed under the Apache
License, Version 2.0. <br/>
+      "Apache", "CloudStack", "Apache CloudStack", and the Apache feather logos are registered
trademarks or trademarks of The Apache Software Foundation.</p>
+      </footer>
+    </div>
+
+  </body>
+</html>



Mime
View raw message