Difference between revisions of "Request For Veto"

From MusicBrainz Wiki
m (stub -> {{stub}})
(Updating with some basic veto process detail)
Line 1: Line 1:
The last stage in a proposal on the Style mailinglist (see [[Style Council|StyleCouncil]]) to change a [[MusicBrainz]] guideline, practice, or policy.  Follows a [[Request For Comment|RequestForComment]].  
+
<dl><dt>RFV
 +
<dd>The last stage in a proposal on the Style mailinglist (see [[Style Council|StyleCouncil]]) to change a [[MusicBrainz]] guideline, practice, or policy.  Follows a [[Request For Comment|RequestForComment]]. </dl>
  
{{Stub}} [[Needs Editing|NeedsEditing]] [[Needs Intertwingling|NeedsIntertwingling]]
+
==Vetos==
  
[[Category:To Be Reviewed]] [[Category:Proposal]]
+
Please try to not cast "preemptive vetos" during the RFC stage, such as "If this goes to RFV, I will veto." Instead, try to work with the proposer to find a compromise on which you both can agree.
 +
 
 +
RFVs should not be vetoed simply because you do not like a change. Before casting a veto, please attempt to describe your concerns about the proposal, preferably during the RFC phase. A veto is not valid without a good argument as to why a proposal should not be accepted.
 +
 
 +
[[Category:Style]] [[Category:Style Council]]

Revision as of 22:29, 10 June 2009

RFV
The last stage in a proposal on the Style mailinglist (see StyleCouncil) to change a MusicBrainz guideline, practice, or policy. Follows a RequestForComment.

Vetos

Please try to not cast "preemptive vetos" during the RFC stage, such as "If this goes to RFV, I will veto." Instead, try to work with the proposer to find a compromise on which you both can agree.

RFVs should not be vetoed simply because you do not like a change. Before casting a veto, please attempt to describe your concerns about the proposal, preferably during the RFC phase. A veto is not valid without a good argument as to why a proposal should not be accepted.