Home

Castle Stronghold

Table of contents

  • 1 Apache Jakarta Bylaws
  • 2 Decisions

Bylaws

The Castle Project has a very active and healthy community. 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

Castle Project strictly follows the Apache Jakarta Bylaws.

Decisions

All contributors are encouraged to participate in decisions, but the decision itself is made by those that have Committer status in the Project. In other words, the Project is a "Minimum Threshold Meritocracy".

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 is 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:

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.

Google
Search WWW Search castleproject.org