| | 17 | |
| | 18 | = Project Management Committee Guidelines = |
| | 19 | |
| | 20 | Author: Jeroen Ticheler[[BR]] |
| | 21 | Contact: Jeroen.Ticheler@fao.org[[BR]] |
| | 22 | Status: Draft proposal |
| | 23 | |
| | 24 | == Summary == |
| | 25 | |
| | 26 | This document describes how the !GeoNetwork Project Management Committee determines membership, and makes decisions on !GeoNetwork opensource project issues. |
| | 27 | |
| | 28 | In brief the committee votes on proposals on the [https://lists.sourceforge.net/mailman/listinfo/geonetwork-devel geonetwork-dev] mailinglist. 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. |
| | 29 | |
| | 30 | == Detailed Process == |
| | 31 | |
| | 32 | 1. Proposals are written up and submitted on the geonetwork-dev mailing list for discussion and voting, by any interested party, not just committee members. |
| | 33 | 2. Proposals need to be available for review for at least two business days before a final decision can be made. |
| | 34 | 3. Respondents may vote "+1" to indicate support for the proposal and a willingness to support implementation. |
| | 35 | 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. |
| | 36 | 5. 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. |
| | 37 | 6. Anyone may comment on proposals on the list, but only members of the Project Management Committee's votes will be counted. |
| | 38 | 7. A proposal will be accepted if it receives +2 (including the proposer) and no vetos (-1). |
| | 39 | 8. 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. |
| | 40 | 9. Upon completion of discussion and voting the proposer should announce whether they are proceeding (proposal accepted) or are withdrawing their proposal (vetoed). |
| | 41 | 10. The Chair gets a vote. |
| | 42 | 11. The Chair is responsible for keeping track of who is a member of the Project Management Committee. |
| | 43 | 12. Addition and removal of members from the committee, as well as selection of a Chair should be handled as a proposal to the committee. The selection of a new Chair also requires approval of the OSGeo board. |
| | 44 | 13. The Chair adjudicates in cases of disputes about voting. |
| | 45 | |
| | 46 | == When is Vote Required? == |
| | 47 | |
| | 48 | * Anything that could cause backward compatibility issues. |
| | 49 | * Adding substantial amounts of new code. |
| | 50 | * Changing inter-subsystem APIs, or objects. |
| | 51 | * Issues of procedure. |
| | 52 | * When releases should take place. |
| | 53 | * Anything that might be controversial. |
| | 54 | |
| | 55 | == Observations == |
| | 56 | |
| | 57 | * The Chair is the ultimate adjudicator if things break down. |
| | 58 | * The absolute majority rule can be used to override an obstructionist veto, but it is intended that in normal circumstances vetoers need to be convinced to withdraw their veto. We are trying to reach consensus. |
