Our Project Management Committee (PMC) bylaws are based on Castle Project's one.

Decisions are made upon votes so everybody has a chance to speak out their minds, however, after a decision is made, everybody is required to embrace it.

Apache Jakarta Bylaws

The PMC for Stormwind is defined as in the Apache Jakarta Bylaws, so here's a modified version of their bylaws.

The Stormwind Project Management Committee (PMC) was formed in September 2007, and is responsible oversight of all projects under the Stormwind banner. The list of current members can be found in our Projects' Teams page.

Roles

The PMC is responsible for the strategic direction and success of the Stormwind Community. This governing body is expected to ensure its composing projects' welfare and guide its' overall directions.

Membership

PMC members may resign at any time. The Chairman may resign as Chairman at any time without resigning membership to the PMC.

Committers are nominated for the PMC by an existing PMC member and a vote then follows. A commiter may be expelled with a 3/4 approval from the PMC. The Chairman is not subject to such a measure.

Voting

Binary PMC voting is a majority-approval variant, with a minimum of 3All Contributors are encouraged to participate in decisions, but the decision itself is made by those that have Committer status in the Project.

Any subscriber to the list may vote on any issue or action item. However, the only binding votes are those cast by a Committer. If the vote is about a change to the source code or documentation and the primary author is a Contributor and not a Committer, the primary author of what's being changed may also cast a binding vote on that issue.

The act of voting carries certain obligations. Voting members are not only stating their opinion, they are also agreeing to help do the work.

Each vote can be made in one of three flavors:

• 1 - "Yes," "Agree," or "the action should be performed." On some issues this is only binding if the voter has tested the action on their own system(s).
• 0 - "Abstain," "no opinion". An abstention may have detrimental effects if too many people abstain.
• -1 - "No." On issues where consensus is required, this vote counts as a veto. All vetos must contain an explanation of why the veto is appropriate. Vetos with no explanation are void. No veto can be overruled. If you disagree with the veto, you should lobby the person who cast the veto. Voters intending to veto an action item should make their opinions known to the group immediately so that the problem can be remedied as early as possible.

An action requiring consensus approval must receive at least 3 binding 1 votes and no binding vetos. An action requiring majority approval must receive at least 3 binding 1 votes and more 1 votes than -1 votes. All other action items are considered to have lazy approval until somebody votes -1, after which point they are decided by either consensus or majority vote, depending on the type of action item.

A week is deemed a fair length for a vote.

Creation of Sub-Projects

New sub-projects may be added to the Stormwind tree of projects, as long as there's a PMC voting approving the admission.

New Sub-Projects must abide by all the rules specified by the Stormwind Project which include, but not only:

• Coding Conventions
• Code Coverage
• Licensing Style
• Integration with other projects in the Community (not required, but important)

The rules to be applied for new sub-projects will be in the Sub-Project request area.