Relationship Editor: Difference between revisions
((Imported from MoinMoin)) |
(response to Brian's comment + deletion of obsolete parts of my comments (Imported from MoinMoin)) |
||
Line 25: | Line 25: | ||
==Discussion== |
==Discussion== |
||
Perhaps the term [[Relationship Type Editor|RelationshipTypeEditor]] (although there are also relationship ''attributes'') might be better than this one? |
Perhaps the term [[Relationship Type Editor|RelationshipTypeEditor]] (although there are also relationship ''attributes'') might be better than this one? [[User:Dupuy|@alex]] |
||
⚫ | |||
[[User:Dupuy|@alex]] |
|||
⚫ | <ul><li style="list-style-type:none"> |
||
</ul> |
</ul> |
||
"Editor" would tend to imply that the |
"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]] |
|||
</ul> |
|||
[[Category:To Be Reviewed]] [[Category:Terminology]] [[Category:Advanced Relationships]] |
[[Category:To Be Reviewed]] [[Category:Terminology]] [[Category:Advanced Relationships]] |
Revision as of 19:32, 24 August 2007
Relationship Editors
RelationshipEditors are users of MusicBrainz who have the permission to change AdvancedRelationshipType
s and AdvancedRelationshipAttribute
s and to add new ones.
The ideal process to get such a change done is:
- propose the change on the UsersMailingList
- If you get some positive feedback,
- For an existing type add the proposal to the discussion section of the existing relationship type page.
- For a new type write a full proposal on a page named like this SomethingRelationshipType.
- Propose the change to the StyleMailingList. If you get consensus there, the change will be implemented.
Current RelationshipEditors are:
- AlexanderDupuy (dupuy)
- DaveEvans (djce)
- DonRedman (donredman)
- LukasLalinsky (lukz)
- mo (mo)
- RobertKaye (rob)
- WolfSong (wolfsong)
Discussion
Perhaps the term RelationshipTypeEditor (although there are also relationship attributes) might be better than this one? @alex
- Yes you are right, RelationshipTypeEditor would be more correct. If you want to fix this, go ahead. I for myself think that RelationshipEditor is ok enough. --DonRedman
"Editor" would tend to imply that the RelationshipEditors 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
s then eventually become the ones to implement such changes, perhaps "RelationshipEditImplementor" would be more correct? -- BrianSchweitzer 03:58, 17 August 2007 (UTC)
- Well, as these are a subset (or subclass) of Editors, and by analogy with AutoEditor
s (and the more recent TransclusionEditor
s), I now feel the term is fine as it is. @alex