The Shibboleth Project, as distinct from the , is a traditional open source software project that is self-governing, under the control of the project's participants, known as Committers. Of course, this independence extends only so far, since the project's viability financially is dependent on the Consortium's success in attracting financial support for our work. To formalize the relationship, the Consortium's primary Operating Resolution, adopted in conjunction with the initial charter, contains a pair of sections, 4 and 5, that describe the Project's organization and governance, and the expectations placed on its participants.
Without repeating that material here, the highlights are:
- Project participants are known as Committers, signifying they have commit access to our source code respository. Committer status is reviewed at least annually.
- Important or contentious project decisions are in the hands of a Project Management Committee, or PMC, which is a subset of the Committers. Voting, in the rare cases it is necessary, is done by seeking 3 yes votes and 0 no votes on an issue, and then discussion on any objecting votes to attempt to reach consensus.
- The Consortium Board has the right to request the removal of a Committer in rare circumstances but the final authority rests with the PMC.
All Committers agree to participate in the project subject to the resolutions passed by the Consortium Board, and may choose to withdraw their participation in the event that resolutions are passed with which they do not agree. At the present time, this consists of the following:
- Code Contribution Policy (DRAFT, not yet approved)
The policy for code contributions to the project by both Committers and outside contributors is described on the Code Contribution Policy page. It is subject to approval by the Consortium Board.