Difference between revisions of "Relationship Editor"

From MusicBrainz Wiki
((Imported from MoinMoin))
(removed old discussion before transclusion (Imported from MoinMoin))
Line 24: Line 24:
* [[User:WolfSong|WolfSong]] (Editor:wolfsong)  
* [[User:WolfSong|WolfSong]] (Editor:wolfsong)  
* [[User:FrederikSOlesen|FrederikSOlesen]] (Editor:Freso)  
* [[User:FrederikSOlesen|FrederikSOlesen]] (Editor:Freso)  
Perhaps the term [[Relationship Type Editor|RelationshipTypeEditor]] (although there are also relationship ''attributes'') might be better than this one? [[User:Dupuy|@alex]]
<ul><li style="list-style-type:none">Yes you are right, [[Relationship Type Editor|RelationshipTypeEditor]] would be more correct. If you want to fix this, go ahead. I for myself think that RelationshipEditor is ok enough. --[[User:DonRedman|DonRedman]]
"Editor" would tend to imply that the RelationshipEditor<code><nowiki></nowiki></code>s are the proposers of change, in the way we use the term "Editor" elsewhere.  Based on the above description, where the general population proposes changes/additions, and the RelationshipEditor<code><nowiki></nowiki></code>s then eventually become the ones to implement such changes, perhaps "[[Relationship Edit Implementor|RelationshipEditImplementor]]" would be more correct? -- [[Brian Schweitzer|BrianSchweitzer]] 03:58, 17 August 2007 (UTC)
<ul><li style="list-style-type:none">Well, as these are a subset (or subclass) of Editors, and by analogy with [[Auto-Editor|AutoEditor]]<code><nowiki></nowiki></code>s (and the more recent [[Transclusion Editor|TransclusionEditor]]<code><nowiki></nowiki></code>s), I now feel the term is fine as it is.  [[User:Dupuy|@alex]]

Revision as of 14:45, 16 May 2008

Relationship Editors

RelationshipEditors are MusicBrainz editors who have the ability to change or remove AdvancedRelationshipTypes and AdvancedRelationshipAttributes and to add new ones.

In general, such changes are not made unilaterally by these editors, but are implemented only after consensus has been reached on the StyleMailingList to make the change.

Anyone who feels that a change to the AR types is needed should:

  1. propose the change on the UsersMailingList
  2. If you get some positive feedback,
    1. For an existing type add the proposal to the discussion section of the existing relationship type page.
    2. For a new type write a full proposal on a page named like this SomethingRelationshipType.
  1. Propose the change to the StyleMailingList as an RFC (request for comments) -- be sure to include "RFC" in the subject line.
  2. After incorporating suggestions, if there appears to be consensus, send the final proposal to the StyleMailingList as an RFV (request for veto) -- again be sure to include "RFV" in the subject line.
  3. If no vetos are received in two weeks, you have consensus, and should arrange for one of the RelationshipEditors (listed below) to implement the change.

Current RelationshipEditors are: