Skip to content

Project Steering Committee (PSC)

Christian Mayer edited this page Jun 11, 2014 · 4 revisions

This document is finally adopted by the project and passed the voting process of the newly formed PSC!

This document describes how the SHOGun Project Steering Committee determines its membership, and makes decisions on SHOGun project issues. The document was based on OpenLayers Project Steering Committee page and GeoServer Project Steering Committee page

General Information

The primary role of the PSC is to make decisions relating to project management.

In brief, the committee votes on proposals on the SHOGun DEV-mailing-list. Proposals are available for review for at least three days.

Detailed Process

  1. Proposals are written up and submitted on the SHOGun DEV-mailing-list for discussion and voting, by any interested person or party, not just committee members.
  2. Proposals need to be available for review for at least three business days before a final decision can be made.
  3. Respondents may vote "+1" to indicate support for the proposal and a willingness to support implementation.
  4. Respondents may vote "-1" to veto a proposal, but must provide clear reasoning and alternate approaches to resolving the problem within the two days.
  5. Anyone may comment on proposals on the list, but only members of the Project Steering Committee's votes will be counted.
  6. A proposal will be accepted if it receives +2 (including the proposer) and no vetos (-1).
  7. If a proposal is vetoed, and it cannot be revised to satisfy all parties, then it can be resubmitted for an override vote in which a majority of all eligible voters indicating +1 is sufficient to pass it. Note that this is a majority of all committee members, not just those who actively vote.
  8. Upon completion of discussion and voting the proposer should announce whether they are proceeding (proposal accepted) or are withdrawing their proposal (vetoed).

When is a Vote Required?

  • Before any changes that could cause backward compatibility issues or changes the published API.
  • Before adding substantial amounts of new code.
  • Issues of procedure.
  • When releases should take place.
  • Anything that might be controversial.
  • New PSC Member

Future PSC members

A new PSC member can be nominated at any time. Voting for a new PSC is done by current active PSC members. There is no hard limit to the number of PSC members, but we want a relatively active PSC. PSC nominations are generally given in recognition to very significant contributions to the project. Membership is open to non-technical people, for example if someone is to make huge advances to the documentations or marketing of SHOGun, for example.

Current PSC-Members

  • Till Adams
  • Marc Jansen
  • Christian Mayer