Request For Veto: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
Adan Aileron (talk | contribs) m (stub -> {{stub}}) |
(Updating with some basic veto process detail) |
||
Line 1: | Line 1: | ||
<dl><dt>RFV |
|||
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]]. |
<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> |
||
==Vetos== |
|||
{{Stub}} [[Needs Editing|NeedsEditing]] [[Needs Intertwingling|NeedsIntertwingling]] |
|||
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. |
|||
⚫ |
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.