RFC3_PSC.dox 2.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152
  1. /*!
  2. \page rfc3_psc RFC 3: PSC Voting Procedures
  3. Author: GRASS PSC
  4. Contact: <a href="http://lists.osgeo.org/mailman/listinfo/grass-psc">grass-psc AT lists.osgeo.org</a>
  5. Status: Proposed
  6. \section introduction Introduction
  7. In brief, the PSC votes on proposals on the dedicated PSC mailing list.
  8. Proposals are available for review for at least four business days, and a
  9. single veto is sufficient to delay progress although ultimately a majority
  10. of committee members can pass a proposal.
  11. \section detailed_process Detailed Process
  12. -# Proposals are written up and submitted on the mailing list for
  13. discussion. Any committee member may call a vote on any proposal, although
  14. it is normal practice for the proposer to call the vote. Any interested
  15. party may subscribe to the list and join the discussion, but only committee
  16. members may vote. The PSC Chair gets a vote.
  17. -# Proposals need to be available for review for at least four business
  18. days before a vote can be closed. It is recognized that some more complex
  19. issues may require longer for discussion and deliberation: a vote should
  20. only be closed after the minimum time period has passed and sufficient
  21. discussion has taken place or no more progress is being made. The Chair
  22. may override this and prolong the discussion period or close a vote straight
  23. away if necessary (although the minimum time period for discussion/voting
  24. always applies).
  25. -# Respondents may vote "+1" to indicate support for the proposal and a
  26. willingness to support implementation.
  27. -# Respondents may vote "-1" to veto a proposal, but must provide clear
  28. reasoning and alternative approaches to resolving the problem within the
  29. period the issue is open for discussion/voting. Otherwise the veto will be
  30. considered invalid.
  31. -# A vote of -0 indicates mild disagreement, but has no effect. A 0
  32. indicates no opinion. A +0 indicate mild support, but has no effect.
  33. -# A proposal will be accepted if it receives +2 (including the proposer)
  34. and no vetoes (-1).
  35. -# The member who called the vote (normally the proposer) is responsible
  36. for collating votes and presenting the result to the PSC after closing the
  37. vote.
  38. -# The Chair adjudicates in cases of disputes over voting.
  39. -# If a proposal is vetoed, and it cannot be revised to satisfy all parties,
  40. then it can be resubmitted for an override vote in which a majority of all
  41. eligible voters indicating +1 is sufficient to pass it. Note that this is
  42. a majority of all committee members, not just those who actively vote.
  43. */