Changes between Version 3 and Version 4 of RFC/3_PSCVotingProcedures

Timestamp:

06/20/14 06:34:58 (11 years ago)

Author:

martinl

Comment:

4 -> 7 days

RFC/3_PSCVotingProcedures

@@ -18 +18 @@
 
  1. Proposals are written up and submitted on the mailing list for discussion. Any committee member may call a vote on any proposal, although it is normal practice for the proposer to call the vote. Any interested  party may subscribe to the list and join the discussion, but only committee  members may vote. The PSC Chair gets a vote.
- 1. Proposals need to be available for review for at least four business days before a vote can be closed. It is recognized that some more complex issues may require longer for discussion and deliberation: a vote should only be closed after the minimum time period has passed and sufficient discussion has taken place or no more progress is being made. The Chair may override this and prolong the discussion period or close a vote straight away if necessary (although the minimum time period for discussion/voting always applies).
+ 1. Proposals are available for review for at least seven days before a vote can be closed. It is recognized that some more complex issues may require longer for discussion and deliberation: a vote should only be closed after the minimum time period has passed and sufficient discussion has taken place or no more progress is being made. The Chair may override this and prolong the discussion period or close a vote straight away if necessary (although the minimum time period for discussion/voting always applies).
  1. Respondents may vote "+1" to indicate support for the proposal and a willingness to support implementation.
  1. Respondents may vote "-1" to veto a proposal, but must provide clear reasoning and alternative approaches to resolving the problem within the period the issue is open for discussion/voting. Otherwise the veto will be considered invalid.