| | 1 | = Fusion Project Steering Committee (PSC) Guidelines= |
| | 2 | |
| | 3 | * Written by Paul Spencer, based on OpenLayers [hhttp://trac.openlayers.org/wiki/SteeringCommittee Steering Committee]. |
| | 4 | |
| | 5 | == Summary == |
| | 6 | |
| | 7 | This document describes how the Fusion PSC determines its membership, and makes decisions on Fusion project issues. |
| | 8 | |
| | 9 | In brief, the committee votes on proposals on the Fusion [http://lists.osgeo.org/mailman/listinfo/fusion-dev developer's mailing list]. 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. |
| | 10 | |
| | 11 | == Detailed Process == |
| | 12 | |
| | 13 | 1. Proposals are written up and submitted on the Fusion [http://lists.osgeo.org/mailman/listinfo/fusion-dev developer's mailing list] for discussion and voting, by any interested party, not just committee members. |
| | 14 | 1. Proposals need to be available for review for at least two business days before a final decision can be made. |
| | 15 | 1. Respondents may vote "+1" to indicate support for the proposal and a willingness to support implementation. |
| | 16 | 1. Respondents may vote "-1" to veto a proposal, but must provide clear reasoning and alternate approaches to resolving the problem within the two days. |
| | 17 | 1. A vote of -0 indicates mild disagreement, but has no effect. A 0 indicates no opinion. A +0 indicate mild support, but has no effect. |
| | 18 | 1. Anyone may comment on proposals on the list, but only members of the PSC's votes will be counted. |
| | 19 | 1. A proposal will be accepted if it receives +2 (including the proposer) and no vetos (-1) ''except'' in the case where the issue requires a unanimous approval (see below). |
| | 20 | 1. 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. |
| | 21 | 1. Upon completion of discussion and voting the proposer should announce whether they are proceeding (proposal accepted) or are withdrawing their proposal (vetoed). |
| | 22 | 1. The Committee Chair is responsible for facilitating discussion of proposals, and is responsible for keeping track of who is a member of the PSC. |
| | 23 | 1. Addition and removal of members from the committee, as well as selection of a Chair should be handled as a proposal to the committee. |
| | 24 | 1. The Chair adjudicates in cases of disputes about voting. |
| | 25 | |
| | 26 | == When is a Vote Required? == |
| | 27 | |
| | 28 | * Before any changes that could cause backward compatibility issues or changes the published API. |
| | 29 | * Before adding substantial amounts of new code. |
| | 30 | * Issues of procedure. |
| | 31 | * When releases should take place. |
| | 32 | * Anything that might be controversial. |
| | 33 | |
| | 34 | == Issues Requiring Unanimous Approval == |
| | 35 | |
| | 36 | * Changing the License for the project or repositories |
| | 37 | |
| | 38 | == Bootstrapping == |
| | 39 | |
| | 40 | Paul Spencer, Jason Fournier, Mike Adair, Chris Claydon and Julien Samuel Lacroix are declared to be the founding PSC members. |
| | 41 | |
| | 42 | Jason Fournier is declared initial Chair of the Project Steering Committee. |
