History:Proposals: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(New page: == Process for Idea Champions == # Come up with an idea for something new or something that should be changed. While somewhat out of date, the points raised on [[Checklist_For_Style_Chang...)
 
No edit summary
Line 1: Line 1:
== Process for Idea Champions ==
# Come up with an idea for something new or something that should be changed. While somewhat out of date, the points raised on [[Checklist_For_Style_Changes|this former checklist for style changes]] are still worth consideration as part of your proposal.
# Create a new wikipage for the proposal. This should be located at <nowiki>http://wiki.musicbrainz.org/Proposal:(proposal name)</nowiki>.
#* The proposal template should be at the top of the page:
<dl><dd><dl><dd><dl><dd><pre>
{{Template:proposal
{{Template:proposal
|proposal=
|proposal=284
|discussion=
|discussion=
|champion=
|champion=[[BrianFreud]]
|rfc=
|rfc=
|rfv=
|rfv=
|status=
|status=RFC
|ar=
|ar=
|style=
|style=
|trac=
|trac=
}}
}}</pre></dl></dl></dl>

<ol start="3">
:: '''proposal''': The RFC number from this page
:: '''rfc, rfv, status''': Leave these blank
:: '''discussion''': A link to the initial discussion (IRC, forums, or style list) of an idea.
:: '''champion''': You.
:: '''ar''': If your proposal changes or adds an [[Advanced_Relationship|Advanced Relationship]], then "true", otherwise leave the value blank.
:: '''style''': If your proposal changes or adds a style guideline, then "true", otherwise leave the value blank.
:: '''trac''': The [http://bugs.musicbrainz.org trac] ticket number for your proposal, if there is one.
<li> Send a RFC announcement to the [http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style style list].
:* The RFC should have "RFC:" at the beginning of the subject line.
:* The body of the email should contain:
::# The expected expiration date for the RFC.
::# A brief summary of the proposal.
::# A link to the proposal's wikipage.
::# Links to any previous discussion (IRC, style list, users list, forums, etc) which led to the proposal.
<li> During the period where the RFC is active, discussion of it will occur on the style list.
:* Anyone can change the proposal's wikipage, though it is encouraged that any changes which go beyond minor formatting, spelling, or example changes should be left to the Idea Champion.
::* If you are not the Idea Champion, and you have sufficient disagreement with the proposal that you feel an entirely different proposal needs to be created, a new proposal wikipage should be created, for which you would become that proposal's Idea Champion. '''Do not''' rewrite the original proposal wikipage and attempt to take over the idea from the original Idea Champion!
:* Where there is disagreement, the Idea Champion should work to find consensus.
::* On minor points, the Idea Champion maintains control of the proposal. However, for the Idea Champion, you ignore dissent at the risk of the proposal - disagreement can easily become vetos during the RFV period.
::* If discussion on a RFC is still ongoing, and there is not yet agreement that the proposal is ready to pass, the RFC period may be extended. The RFC period only defines a minimum, not a maximum, time period for debate.
<li> Before a RFC may move into RFV status, another style council member must endorse it with "+1" in an email to the style list, indicating that, in its current state, it has been reviewed and is acceptable to that member. Any changes to RFC text prior to RFV clear that +1 and reset this requirement.
<li> When the RFC's initial period has expired, the Idea Champion (or a Style Leader) will send out a RFV for the proposal.
<li> 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 RFV email should have "RFV:" at the beginning of the subject line.

Revision as of 00:28, 6 April 2010


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



Proposal number: RFC-284
Champion: BrianFreud
Current status: RFC
  • 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

  • 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

  • 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

    • Retrieved from "https://wiki.musicbrainz.org/index.php?title=History:Proposals&oldid=40026"