Author: nslater
Date: Thu Aug 15 22:55:18 2013
New Revision: 1514527
URL: http://svn.apache.org/r1514527
Log:
Edit for non-technical decisions and other minor changes (following vote)
Modified:
cloudstack/site/trunk/content/bylaws.mdtext
Modified: cloudstack/site/trunk/content/bylaws.mdtext
URL:
http://svn.apache.org/viewvc/cloudstack/site/trunk/content/bylaws.mdtext?rev=1514527&r1=1514526&r2=1514527&view=diff
==============================================================================
--- cloudstack/site/trunk/content/bylaws.mdtext (original)
+++ cloudstack/site/trunk/content/bylaws.mdtext Thu Aug 15 22:55:18 2013
@@ -198,41 +198,64 @@ votes over the action.
3.4.1. Technical Decisions
+A technical decision is any decision that involves changes to the source code
+that we distribute in our official releases.
+
Technical decisions should normally be made by the entire community using
-consensus gathering, and not through formal voting.
+discussion-lead consensus gathering, and not through formal voting.
-Technical decisions must be made on a project development mailing list.
+Technical decisions must be made on the project development mailing list.
During the consensus gathering process, technical decisions may be vetoed by
any Committer with a valid reason.
If a formal vote is started for a technical decision, the vote will be held as
-a lazy consensus of active committers.
+a lazy consensus of active committers.
+
+Any user, contributor, committer, or PMC member can initiate a technical
+decision making process.
+
+3.4.2. Non-Technical Decisions
+
+A non-technical decisions is any decision that does not involve changes to the
+source code that we distribute in our official releases.
+
+Non-technical decisions should normally be made by the entire community using
+discussion-lead consensus-building, and not through formal voting.
+
+Non-technical decisions can be made on whichever project mailing list is most
+appropriate.
+
+Non-technical decisions cannot be vetoed, but if there is strong opposition
+a formal vote can be used to resolve the dispute.
+
+If a formal vote is started for a non-technical decision, the vote will be held
+as a lazy 2/3 majority of active committers.
-Any user, contributor, committer or PMC member can initiate a technical
+Any user, contributor, committer, or PMC member can initiate a non-technical
decision making process.
-3.4.2. Release Plan
+3.4.3. Release Plan
Defines the timetable and work items for a release. The plan also nominates a
Release Manager.
A lazy majority of active committers is required for approval.
-Any active committer or PMC member may call a vote. The vote must occur on a
+Any active committer or PMC member may call a vote. The vote must occur on the
project development mailing list.
-3.4.3. Product Release
+3.4.4. 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 of active PMC members is required for approval.
-Any active committer or PMC member may call a vote. The vote must occur on a
+Any active committer or PMC member may call a vote. The vote must occur on the
project development mailing list.
-3.4.4. Adoption of New Codebase
+3.4.5. Adoption of New Codebase
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
@@ -242,10 +265,10 @@ This also covers the creation of new sub
Lazy 2/3 majority of active PMC members.
-Any active committer or PMC member may call a vote. The vote must occur on a
+Any active committer or PMC member may call a vote. The vote must occur on the
project development mailing list.
-3.4.5. New Committer
+3.4.6. New Committer
When a new committer is proposed for the project.
@@ -254,7 +277,7 @@ Lazy consensus of active PMC members.
Any active PMC member may call a vote. The vote must occur on the PMC private
mailing list.
-3.4.6. New PMC Member
+3.4.7. New PMC Member
When a committer is proposed for the PMC.
@@ -263,7 +286,7 @@ Lazy consensus of active PMC members.
Any active PMC member may call a vote. The vote must occur on the PMC private
mailing list.
-3.4.7. Committer Removal
+3.4.8. Committer Removal
When removal of commit privileges is sought. Note: Such actions will also be
referred to the ASF board by the PMC chair
@@ -274,7 +297,7 @@ a member of the PMC).
Any active PMC member may call a vote. The vote must occur on the PMC private
mailing list.
-3.4.8. PMC Member Removal
+3.4.9. PMC Member Removal
When removal of a PMC member is sought. Note: Such actions will also be
referred to the ASF board by the PMC chair.
@@ -284,13 +307,13 @@ Lazy 2/3 majority of active PMC members
Any active PMC member may call a vote. The vote must occur on the PMC private
mailing list.
-3.4.9. Modifying Bylaws
+3.4.10. Modifying Bylaws
Modifying this document.
Lazy majority of active PMC members
-Any active committer or PMC member may call a vote. The vote must occur on a
+Any active committer or PMC member may call a vote. The vote must occur on the
project development mailing list.
3.5. Voting Timeframes
