Difference between revisions of "Proposals"

From MusicBrainz Wiki
(Undo revision 40921 by Vsimon213 (Talk))
Line 1,871: Line 1,871:
 
* Any of [[:Category talk:External Website Relationship Class]]
 
* Any of [[:Category talk:External Website Relationship Class]]
 
[[Category:Documentation]]
 
[[Category:Documentation]]
 
==Related Links==
 
[http://hellokittydigitalcamera.net/ '''hello kitty digital camera''']
 

Revision as of 05:40, 6 July 2010

Contents

Proposals

Changes to MusicBrainz are made using this proposal process.

The process is simple. Someone has an idea, either for something new, or for a change to how something existing is done. After discussion of the idea has taken place, one person takes control of the idea. This person is then known as the Idea Champion for that proposal. The Idea Champion has the responsibility for moving the idea from a vague concept to a clear proposal, then working for Style Council passage of the proposal.

Though it is somewhat dated, Turning Your Ideas into Reality is well worth a read.

Definitions

Idea Champion
The person who currently is handling a proposal.
Style Council
Any members of the Style mailing list who wish to take part in discussion of a proposal. There is no formal membership to the style council. If you are an interested contributor to MusicBrainz and reasonably well informed about existing StyleGuidelines, MusicBrainz development, and the general culture of the project, you are welcome to subscribe to the Style mailing list and join the discussions. Also see the history of the Style Council.

Process for Idea Champions

  1. Come up with an idea for something new or something that should be changed. While somewhat out of date, the points raised on this former checklist for style changes are still worth consideration as part of your proposal.
  2. Create a new wikipage for the proposal. This should be located at http://wiki.musicbrainz.org/Proposal:(proposal name).
    • The proposal template should be at the top of the page:
{{Template:proposal
|proposal=
|discussion=
|champion=
|rfc=
|rfv=
|status=
|ar=
|style=
|trac=
}}
    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, 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 trac ticket number for your proposal, if there is one.
  1. Send a RFC announcement to the style list.
    • The RFC should have "RFC:" at the beginning of the subject line.
    • The body of the email should contain:
    1. The expected expiration date for the RFC.
    2. A brief summary of the proposal.
    3. A link to the proposal's wikipage.
    4. Links to any previous discussion (IRC, style list, users list, forums, etc) which led to the proposal.
  2. 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.
  3. 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.
  4. 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.
  5. 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 the style council.
    • 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.
  6. 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!

Time Periods

  • RFC: 7 days
  • RFV: 2 days

Style Leaders

Style Elder

Definitions

RFC (Request for Change)
The initial discussion period for any proposal
RFV (Request for Veto)
The decision period for any proposal
Style Leader
They guide the process and keep it from getting stuck. If the council cannot reach consensus they will make a decision. This position was previously called "secretary".
Style Elder
The benevolent dictator of MusicBrainz style issues. If the process goes off the rails, or if someone disputes the style leaders' decisions, the elder steps in.

Special Procedures

Has Cover Art At, Has Lyrics At, and Has Score At Relationship Types

These relationships each only allow links to whitelisted sites. To add any site to the whitelist for any one of these advanced relationships, the following additional procedure must be followed.

  1. Add the site to the 'in-progress' list on the relevant page for the AR.
  2. Using the normal proposal process, send a RFC requesting the addition of the site.
    • The RFC should be limited to covering only 1 site.
    • The RFC must provide rationale and evidence for why the site can reasonably be believed to have permission to contain the content to which we would be linking.
  3. The Style Council will then make sure that the site itself is legal; that it has a right/license/whatever to store the content (lyrics/scores/cover art) which which the relationships would be link.
    • If any situation arises where "legal" is questionable depending on local laws, MusicBrainz is based in California, so US/California law wins.
  4. Once the RFV has passed, permission must be obtained, in writing (email is fine), from the site which would be added to the whitelist.
    • This permission may be requested prior to the passage of the RFV.

Only when permission has been received and a RFV has passed may the site be added as a whitelisted site for the applicable relationship type(s).

Adding new instrument types

These do not go through the Style Council process. Instead, they use the instrument addition process.

Current Proposals

Next New Proposal Number

Next new proposal number: 288

Proposal numbers 112 - 200 and 206 - 250 have been reserved for RFCs to fill in holes in the guidelines and documentation.

Style Proposals

Categorized as Category:Proposed Style. Passed proposals waiting to be implemented and closed proposals are found on the talk page.

RFC # Title & Wikipage Champion Affects Trac ticket Status RFC RFC Date RFV RFV Date Passage Date

RFC-1: AudioBook Style

RFC-1

Audiobook Style Jormangeud New guideline 2147 In development

RFC-8: Capitalization Standard Swedish

RFC-8

Capitalization Standard Swedish symphonick New guideline In development

RFC-9: Capitalization Standard Turkish

RFC-9

Capitalization Standard Turkish ym New guideline RFV RFC 2010-05-30 2010-06-10 2010-06-12

RFC-19: Game Soundtrack Style

RFC-19

Game Soundtrack Style BrianFreud New guideline 2146 In development

RFC-20: Instrumental Style

RFC-20

Instrumental Style Bogdanb ETI style for instrumental tracks 2142 In development RFC 2006-04-20

RFC-25: Medley Style

RFC-25

Medley Style Jacobbrett New guideline In development

RFC-28: Musical Soundtrack Style

RFC-28

Musical Soundtrack Style BrianFreud New guideline 2146 In development

RFC-42: Release Artist Style

RFC-42

Release Artist Style navap New guideline 2143 In development

RFC-43: Release Country Event Style

RFC-43

Release Country Event Style (additional older page) (RFC-64 Discussion) Jacobbrett Release events 2145 RFC2 RFC, RFC2 2010-03-19, 2010-04-07 in discussion in discussion

RFC-53: Soundtrack Style

RFC-53

Soundtrack Style BrianFreud New guideline 2146 In development

RFC-54: Soundtrack Title Style

RFC-54

Soundtrack Title Style BrianFreud New guideline 2146 In development

RFC-61: Track Title Style

RFC-61

Track Title Style warp Naming of track titles In development

RFC-62: Untitled Release Style

RFC-62

Untitled Release Style Bogdanb New guideline In development

RFC-67: Revised Classical Style Guide (aka CSGv2)

RFC-67

Revised Classical Style Guide (aka CSGv2) BrianFreud Rewrites all of CSG 4426 RFC, On hold pending NGS release RFC 2009-02-15

RFC-202: Part Number Style rewrite

RFC-202

Part Number Style rewrite BrianFreud Part Number Style 5066 On hold pending RFC-61

RFC-109: Release Groups

RFC-109

Release Groups Jacobbrett New guideline None In development

RFC-204: Decommission Don't Make Relationship Clusters

RFC-204

Decomission Don't Make Relationship Clusters BrianFreud Removes a guideline vetoed, awaiting counter-proposal RFC 2010-03-15 RFV 2010-03-29

RFC-275: Clarify order of precidence of guidelines and principles

RFC-275

Clarify order of precidence of guidelines and principles BrianFreud Cleans up & assigns order of precidence for guidelines and principles RFC2 RFC+Second 2010-03-27 RFV 2010-04-04 2010-04-06

RFC-286: Capitalization Standard Transliterations

RFC-286

Capitalization Standard Transliterations rewrite foolip Revised guideline RFC(+1?) RFC 2010-04-07 2010-06-05 2010-?? 2010-??

RFC-288: Capitalization Standard Japanese

RFC-288

Capitalization Standard Japanese foolip New caps standard guideline None RFC+1 RFC 2010-06-05 2010-06-12 2010-06-14

Advanced Relationship Proposals

Categorized as Category:Proposed Relationship Type. Passed proposals waiting to be implemented and closed proposals are found on the talk page.

RFC # Title & Wikipage Champion Affects Trac ticket Status RFC RFC Date RFV RFV Date Passage Date

RFC-4: Redesign of the Vocal Relationship Attribute

RFC-4

Redesign of the Vocal Relationship Attribute BrianFreud AR modification 1140 4437 Pre-RFC Pre-RFC

RFC-26: Miscellaneous Production Relationship Type/Artwork

RFC-26

Miscellaneous Production Relationship Type/Artwork BrianFreud In development

RFC-29: Narrator Relationship Type

RFC-29

Narrator Relationship Type symphonick New vocal role 1368 In development

RFC-35: Part Of Series Relationship Type

RFC-35

Part Of Series Relationship Type voiceinsideyou New release-release, or RG-RG, AR In development

RFC-39: Reader Relationship Type

RFC-39

Reader Relationship Type symphonick New vocal role 1370 In development

RFC-55: Speaker Relationship Type

RFC-55

Speaker Relationship Type symphonick New vocal role 1731 In development

RFC-68: Add Has News Coverage AR

RFC-68

Add Has News Coverage AR Original ruoak; currently BrianFreud New release-URL AR 5636 Tabled until post-NGS RFC, RFC2 2010-02-28, 2010-03-15

RFC-69: Defining instruments and vocals for members of bands

RFC-69

Defining instruments and vocals for members of bands BrianFreud Artist-artist AR enhancement 1141 In development

RFC-83: Add track-url Work-URL Wikipedia AR

RFC-83

Add track-url Work-URL Wikipedia AR BrianFreud New track-URL AR 3852 and 4036 In development

RFC-84: Add 'provides discographic information about' AR

RFC-84

Add 'provides discographic information about' AR BrianFreud New track-URL AR 3734 In development

RFC-87: Add 'is a project of' AR

RFC-87

Add 'is a project of' AR abandoned New artist-artist AR 1739 In development

RFC-89: Add social networking AR

RFC-89

Add Social Networking AR Andrew John Hughes (gnu_andrew) New artist-URL AR
New label-URL AR
5329 RFC RFC 2010-07-05

RFC-111: Writer Relationship Type

RFC-111

Writer Relationship Type abandoned New AR 1423 In development

RFC-260: Extend License attribute

RFC-260

Extend License attribute Murdos Adds new licenses to existing License Relationship Attribute In development

RFC-261: Clean up link phrases

RFC-261

Clean up link phrases BrianFreud Makes AR link phrases consistent and comprehensible RFV RFC 2010-03-23 RFV 2010-04-06 In discussion

RFC-106: Conductor AR Changes

RFC-106

Conductor AR Changes BrianFreud (was luks) Conductor and Chorus Master Relationship Types modification Pre-RFC first mention of problemRFC Pre-RFC 2007-05-03

RFC-264: Choirmaster Position Relationship Type

RFC-264

Choirmaster Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-265: Concertmaster Position Relationship Type

RFC-265

Concertmaster Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-266: Conductor Position Relationship Type

RFC-266

Conductor Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-267: Manager Position Relationship Type

RFC-267

Manager Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-268: Road Crew Position Relationship Type

RFC-268

Road Crew Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-269: Music Director Position Relationship Type

RFC-269

Music Director Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-270: Bandleader Position Relationship Type

RFC-270

Bandleader Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-271: Teacher Position Relationship Type

RFC-271

Teacher Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-272: Vocal Coach Position Relationship Type

RFC-272

Vocal Coach Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-273: Instrument Instructor Position Relationship Type

RFC-273

Instrument Instructor Position Relationship Type BrianFreud New artist-artist AR Pre-RFC Pre-RFC

RFC-274: Supporting Musician Relationship Type enhancement

RFC-274

Supporting Musician Relationship Type enhancement BrianFreud Add attribute to existing artist-artist AR Pre-RFC Pre-RFC

RFC-278: Add label-URL to Discography Relationship Type

RFC-278

Add label-URL to Discography Relationship Type BrianFreud Adds AR RFC+1 RFC 2010-06-03 2010-06-10 2010-06-12

RFC-279: Add label-URL to Mail Order Relationship Type

RFC-279

Add label-URL to Mail Order Relationship Type BrianFreud Adds AR Waiting for RFC

RFC-280: Add label-URL and artist-URL to Review Relationship Type

RFC-280

Add label-URL and artist-URL to Review Relationship Type BrianFreud Adds 2 ARs Waiting for RFC

RFC-281: Add artist-label to Miscellaneous Role Relationship Type

RFC-281

Add artist-label to Miscellaneous Role Relationship Type BrianFreud Adds AR Waiting for RFC

RFC-52a: Document Supporting Release Relationship Type: RG-RG

RFC-52a

Document Supporting Release Relationship Type: RG-RG BrianFreud Document AR In development (Reference RFC-52)

RFC-52: Supporting Release Relationship Type

RFC-52

Supporting Release Relationship Type (NGS version) BrianFreud New release-release AR Passed, RFC4 RFC+second, RFC2, RFC3 2010-03-18, 2010-03-25, 2010-04-05, 2010-06-10 2010-04-01, 2010-06-07 2010-04-04, 2010-06-09

Other Proposals

Categorized as Category:Proposal. Passed proposals waiting to be implemented and closed proposals are found on the talk page.

RFC # Title & Wikipage Champion Affects Trac ticket Status RFC RFC Date RFV RFV Date Passage Date

RFC-3: Advanced Entity

RFC-3

Advanced Entity (Post-NGS) BrianFreud Catchall for various post-NGS entity suggestions post-NGS

RFC-6: Artist Type Project

RFC-6

Artist Type Project abandoned New Artist type In development

RFC-11: Change Default Data Quality Proposal

RFC-11

Change Default Data Quality Proposal (Data) BrianFreud Voting, Quality, and Edit expiration post-NGS pre-RFC RFC 2007-06-19

RFC-24: Location Proposal

RFC-24

Location Proposal BrianFreud New entity discussion, post-NGS

RFC-36: Performance Restructuring Proposal

RFC-36

Performance Restructuring Proposal BrianFreud In development

RFC-37: Performances And Recordings Proposal

RFC-37

Performances And Recordings Proposal BrianFreud New entity discussion, post-NGS

RFC-49: Release Type Restructuring Proposal

RFC-49

Release Type Restructuring Proposal BrianFreud 1372 In development

RFC-78: Add release format: 7" vinyl

RFC-78

Add release format: 7" vinyl Per Øyvind Øygard (Wizzcat) New release format/format+format attribute 3941 In development

RFC-79: Add release format: 10" vinyl

RFC-79

Add release format: 10" vinyl Per Øyvind Øygard (Wizzcat) New release format/format+format attribute 3941 In development

RFC-80: Add release format: 12" vinyl

RFC-80

Add release format: 12" vinyl Per Øyvind Øygard (Wizzcat) New release format/format+format attribute 3941 In development

RFC-49a: Release Status Proposals

RFC-277

Various Release Status Proposals BrianFreud This is a catchall for Release Status proposals formerly part of RFC-49 In development

RFC-49b: Release Format Proposal

RFC-278

Release Format Proposal BrianFreud This is the Release Format proposal, formerly part of RFC-49 In development

RFC-258: How to Identify Release Details

RFC-258

How to Identify Release Details Jacobbrett Will replace How To Identify Labels In development

RFC-287: Modify musical soundtrack style (proposal?)

RFC-287

Modify musical soundtrack style (proposal?)] PBryan RFC 2010-05-30 In discussion 2010-06-06

Pre-Reserved RFCs for cleaning up documentation and guidelines

These are all official entities, relationships, guidelines, or other things which have some minor element which is missing. Most are only a sentence or two, but need an RFC to be made official; this table lists those, and pre-reserves RFC numbers for these future RFCs. As these are intended to be truly short RFCs of only a sentence or two (in almost all cases), most won't actually have proposal pages, only proposal emails.

RFC Number Wikipage Hole to be filled Champion RFC email RFC date RFV date Pass date
RFC-118 (unused at the moment)
RFC-119 (unused at the moment)
RFC-120 Librettist Relationship Type Guideline for use of the additional attribute
RFC-127 Orchestra Relationship Type Guideline for use of the additional attribute
RFC-132 Samples Artist Relationship Type Guideline for use of the additional attribute
RFC-133 (not currently assigned)
RFC-134 Samples Artist Relationship Type Guideline for use of the vocal attribute
RFC-135 Samples Artist Relationship Type Guideline for use of the instrument attribute
RFC-136 Engineer Relationship Type Guideline for use of the executive attribute
RFC-139 (not currently assigned)
RFC-140 (not currently assigned)
RFC-141 (not currently assigned)
RFC-142 Bonus Relationship Attribute Description
RFC-143 Chorus Master Relationship Type start date
RFC-144 Chorus Master Relationship Type end date
RFC-145 Chorus Master Relationship Type additional attribute
RFC-150 Compilation Relationship Type start date
RFC-151 Compilation Relationship Type end date
RFC-157 Co Relationship Attribute Description
RFC-158 Creative Position Relationship Type start date
RFC-159 Creative Position Relationship Type end date
RFC-160 Engineer Position Relationship Type start date
RFC-161 Engineer Position Relationship Type end date
RFC-162 (not currently assigned)
RFC-163 Editor Relationship Type start date
RFC-164 Editor Relationship Type end date
RFC-167 DJ Mix Relationship Type start date
RFC-168 DJ Mix Relationship Type end date
RFC-169 Liner Notes Author Relationship Type start date
RFC-170 Liner Notes Author Relationship Type end date
RFC-171 Liner Notes Author Relationship Type additional
RFC-172 Description Relationship Attribute Description
RFC-173 (unused at the moment)
RFC-174 (unused at the moment)
RFC-175 Mash-up Relationship Type start date
RFC-176 Mash-up Relationship Type end date
RFC-177 (unused at the moment)
RFC-178 (unused at the moment)
RFC-181 Member Of Band Relationship Type additional
RFC-182 Miscellaneous Role Relationship Type start date
RFC-183 Miscellaneous Role Relationship Type end date
RFC-184 (unused at the moment)
RFC-185 (unused at the moment)
RFC-186 Mix-DJ Relationship Type start date
RFC-187 Mix-DJ Relationship Type end date
RFC-188 Orchestra Relationship Type start date
RFC-189 Orchestra Relationship Type end date
RFC-194 Part Of Set Relationship Type start date
RFC-195 Part Of Set Relationship Type end date
RFC-196 Performer Relationship Type start date
RFC-197 Performer Relationship Type end date
RFC-198 Photography Relationship Type additional
RFC-199 Producer Position Relationship Type start date
RFC-200 Producer Position Relationship Type end date
RFC-206 Producer Relationship Type start date
RFC-207 Producer Relationship Type end date
RFC-210 Publisher Relationship Type start date
RFC-211 Publisher Relationship Type end date
RFC-212 (unused at the moment)
RFC-213 (unused at the moment)
RFC-214 Remaster Relationship Type start date
RFC-215 Remaster Relationship Type end date
RFC-218 (unused at the moment)
RFC-219 (unused at the moment)
RFC-222 Tribute Relationship Type start date
RFC-223 Tribute Relationship Type end date
RFC-224 Writer Relationship Type start date
RFC-225 Writer Relationship Type end date
RFC-226 Executive Relationship Attribute Description
RFC-227 Remixer Relationship Type start date
RFC-228 Remixer Relationship Type end date
RFC-229 Remixer Relationship Type additional
RFC-230 Samples Relationship Type start date
RFC-231 Samples Relationship Type end date
RFC-234 Supporting Musician Relationship Type start date
RFC-235 Supporting Musician Relationship Type end date
RFC-236 Supporting Musician Relationship Type additional
RFC-237 Supporting Musician Relationship Type guest
RFC-238 Supporting Musician Relationship Type instrument
RFC-239 Supporting Musician Relationship Type vocal
RFC-240 Transliterated Relationship Attribute Description
RFC-241 (Not used yet)
RFC-242 (Not used yet)
RFC-243 (Not used yet)
RFC-244 (Not used yet)
RFC-245 (Not used yet)
RFC-246 (Not used yet)
RFC-247 (Not used yet)
RFC-248 (Not used yet)
RFC-249 (Not used yet)
RFC-250 (Not used yet)

Fodder for Future Proposals