CAS is governed by a Project Management Committee (PMC) modeled after Apache-style PMCs.
The PMC is composed of members and a chair who has executive authority over the committee and reports to the Apereo board. The most common authority exercised by the chair is to appoint additional PMC members as necessary. Thus the chair may bootstrap the committee. The board may appoint a chair in extreme circumstances (i.e. dysfunction, defunct), but the chair is typically appointed by PMC vote. CAS project developers with commit access to the official project source code repository are automatically PMC members; thus a committer is a PMC member. The PMC chair may or may not be a committer.
All voting MUST be conducted over a period of at least 72 hours on a project mailing list; more time SHOULD be allotted for special situations such as holidays and other occasions where large numbers of PMC members may be offline for longer-than-normal periods. Voting is by lazy consensus where at least two +1 votes is sufficient to move forward and a single -1 vote is sufficient to block a proposal. All PMC member votes are equal; the chair has no veto power. Voting SHOULD strive for consensus.
The following discussion from the cas-dev mailing list hopefully clarifies voting procedure:
does voting stop after two +1 or one -1 (I.e. is it a race to see who responds first) or is it not tallied until the voting period closes?
Voting is open for at least 72h. Any measure is effectively dead with a -1 vote, so if a -1 comes in a minute after voting starts there's really no point in waiting any longer. The value of a 72h window is that it affords more time for dissenters. The voting process is intended to emphasize and produce consensus, which is the most important aspect.
The nomination of a committer requires a vote: a majority of +1 is required and no -1. The vote must happen privately on the cas-pmc mailing list.
Communication happens primarily by public mailing lists. Exceptions are issues that require discretion or confidentiality; private lists are the appropriate channel in those situations. Communication may also occur through other appropriate channels as needed, such as video/voice conference calls, IRC and IM. No official decisions may be made via any means other than voting on a project mailing list; if it didn't happen on list, it didn't happen. Discussions that occur in side channels such as IRC and IM SHOULD be summarized on a mailing list when they may impact decision making processes. The commitee SHOULD make an effort to meet periodically via a high-bandwidth synchronous medium such as in-person meetings at conferences or voice/video conference calls.
PMC members agree to abide by and enforce Apereo foundation legal policy and foundation branding/marketing policies. PMC members SHOULD notify of intent to leave or become inactive in order to facilitate replacement or recruitment of new members.