History:Proposals

From MusicBrainz Wiki


Status: This page describes an active proposal and is not official.



Proposal number: RFC-284
Champion: BrianFreud
Current status: RFC



6. When the RFC's initial period has expired, the Idea Champion (or a Style Leader) will send out a RFV for the proposal.

  • The RFV email should have "RFV:" at the beginning of the subject line.
  • The body of the email should contain:
  1. The expected passage date for the RFV.
  2. A brief summary of the proposal, including a summary of any changes which have been made since the RFC.
  3. A link to the proposal's wikipage.

OLD

7. During the RFV period, any member of the style council may veto the RFV. However, vetos must have merit (no vetos simply because "I don't like this proposal"). Vetos must be publicly cast, on the style list, and should detail what problems are believed to remain in the RFV, and what changes could be made such that the veto would be cleared. These suggested changes must be reasonable; if the changes would entail a rewrite, or rethink, of the proposal itself, then a counter-proposal wikipage should be created, and the decision as to which proposal will pass should be left to :* If a RFV receives a veto, the proposal reverts to a RFC. There is no minimum time period at this point, but no new RFV should be attempted until the problems raised in any vetos have been discussed and/or addressed. A proposal may revert to a RFC, or have replacement RFCs sent, as many times as is needed. the style council.

NEW

7. During the RFV period, any member of the style council may veto the RFV. However, vetos must have merit (no vetos simply because "I don't like this proposal").

  • A veto is not cast if:
  • It is implied; see number 3 below,
  • It is hypothetical, e.g., 'I might veto if...',
  • It is conditional, e.g., 'I will veto if you don't...'.
  • To be a valid veto, a veto must:
  1. Be publicly cast, on the style list,
  2. Detail what problems are believed to remain in the RFV, and what changes could be made such that the veto would be cleared. These suggested changes must be reasonable; if the changes would entail a rewrite, or rethink, of the proposal itself, then a counter-proposal wikipage should be created, and the decision as to which proposal will pass should be left to the style council.
  3. Actively state that it is a veto, specifically using the word "veto", e.g., 'I veto because...'.
  • If a RFV receives a veto, the proposal reverts to a RFC. There is no minimum time period at this point, but no new RFV should be attempted until the problems raised in any vetos have been discussed and/or addressed. A proposal may revert to a RFC, or have replacement RFCs sent, as many times as is needed.

END


8. If the end of the RFV period is reached, and no vetos have been cast, then the proposal has passed. The Idea Champion is now responsible for ensuring that the changes described by the proposal are enacted (changing wiki pages, entering edits, creating trac or jira tickets, etc.). This includes remembering to remove the proposal template from the proposal's wikipage!


OLD

NEW

At any time during the proposal process until the proposal passes, the Idea Champion may withdraw or table a proposal, for any reason. Notification of this status change must be sent to the style mailing list.

END


Time Periods


OLD

  • RFC: 7 days
  • RFV: 2 days

NEW

  • RFC: 7 days
  • RFV: 2 days

Note: These time periods define a mimimum time period that a proposal exists in either state. Except for a vetoed RFV reverting to RFC, a proposal does not change its current state ('RFC', 'RFV', 'withdrawn', 'tabled (until date)', or 'passed proposal') until the Idea Champion, a Style Leader, or the Style Elder sends a change of status announcement to the style mailing list. This change of state notification must be received by pipermail to be recognized.

END