|Author:||Dan Little (inspired by MapServer RFC23 http://mapserver.org/development/rfc/ms-rfc-23.html#rfc23)|
|Contact:||danlittle at ...|
This document describes how the GeoMOOSE Project Steering Committee determines membership, and makes decisions on all aspects of the GeoMOOSE project - both technical and non-technical.
Examples of PSC management responsibilities:
In brief the project team votes on proposals on GeoMOOSE. Proposals are available for review for at least two days, and a single veto is sufficient to delay progress though ultimately a majority of members can pass a proposal.
The PSC is made up of individuals consisting of technical contributors (e.g. developers) and prominent members of the GeoMOOSE user community. There is no set number of members for the PSC although the initial desire is to set the membership at six.
Any member of the GeoMOOSE mailing list may nominate someone for committee membership at any time. Only existing PSC committee members may vote on new members. Nominees must receive a majority vote from existing members to be added to the PSC.
If for any reason a PSC member is not able to fully participate then they certainly are free to step down. If a member is not active (e.g. no voting, no IRC or email participation) for a period of two months then the committee reserves the right to seek nominations to fill that position. Should that person become active again (hey, it happens) then they would certainly be welcome, but would require a nomination.
Members should take an active role guiding the development of new features they feel passionate about. Once a change request has been accepted and given a green light to proceed does not mean the members are free of their obligation. PSC members voting “+1” for a change request are expected to stay engaged and ensure the change is implemented and documented in a way that is most beneficial to users. Note that this applies not only to change requests that affect code, but also those that affect the web site, technical infrastructure, policies and standards.
PSC members are expected to participate in pre-scheduled development meetings. If known in advance that a member cannot attend a meeting, the member should let the meeting organizer know via e-mail.
PSC members are expected to be active on the GeoMOOSE mailing lists, subject to open source mailing list etiquette.
Non-developer members of the PSC are not expected to respond to coding level questions on the mailing list, however they are expected to provide their thoughts and opinions on user level requirements and compatibility issues when RFC discussions take place.
Initial members are: