Uploaded image for project: 'MusicBrainz Style'
  1. MusicBrainz Style
  2. STYLE-2442

Clarify how clear and obvious applications of Style by Auto-Editors are not, or are, "controversial changes" or "abuse" of privileges

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • Guidelines
    • None

      https://musicbrainz.org/doc/Code_of_Conduct

      A lot of users try to make the argument that clear and obvious applications of Style are controversial changes and/or abuse of editing powers.  That doesn't seem right to me, but feel free to clarify otherwise.

      Not really Style, but there doesn't seem to be a more appropriate Jira project for this.

          [STYLE-2442] Clarify how clear and obvious applications of Style by Auto-Editors are not, or are, "controversial changes" or "abuse" of privileges

          Nicolás Tamargo added a comment -

          Obviously, the whole point of having autoeditorship privileges is to be able to speed up edits that follow the guidelines. If anyone puts that in doubt, feel free to point them to this statement.

           

          The only case where this can be in doubt is if someone is already making the change and the autoeditor privileges are used to intentionally enter the same edit in a way that'd make the previous one fail - but I've never seen this happen other than unintentionally. That said, it's always good to make sure there's no pending edits before making an autoedit, and if there are, as long as they're an improvement, they should ideally be approved first, then improved further as an autoedit

          Nicolás Tamargo added a comment - Obviously, the whole point of having autoeditorship privileges is to be able to speed up edits that follow the guidelines. If anyone puts that in doubt, feel free to point them to this statement.   The only case where this can be in doubt is if someone is already making the change and the autoeditor privileges are used to intentionally enter the same edit in a way that'd make the previous one fail - but I've never seen this happen other than unintentionally. That said, it's always good to make sure there's no pending edits before making an autoedit, and if there are, as long as they're an improvement, they should ideally be approved first, then improved further as an autoedit

            reosarevok Nicolás Tamargo
            yindesu yindesu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package