Misplaced Pages

:Arbitration/Requests/Enforcement - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Arbitration | Requests

This is an old revision of this page, as edited by Sandstein (talk | contribs) at 23:01, 27 January 2013 (→Result concerning Noetica: cmt). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 23:01, 27 January 2013 by Sandstein (talk | contribs) (→Result concerning Noetica: cmt)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff) "WP:AE" redirects here. For the automated editing program, see Misplaced Pages:AutoEd.
Noticeboards
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
General
Articles and content
Page handling
User conduct
Other
Category:Misplaced Pages noticeboards
    Shortcuts

    Click here to add a new enforcement request
    For appeals: create a new section and use the template {{Arbitration enforcement appeal}}
    See also: Logged AE sanctions

    Important informationShortcuts

    Please use this page only to:

    • request administrative action against editors violating a remedy (not merely a principle) or an injunction in an Arbitration Committee decision, or a contentious topic restriction imposed by an administrator,
    • request contentious topic restrictions against previously alerted editors who engage in misconduct in a topic area designated as a contentious topic,
    • request page restrictions (e.g. revert restrictions) on pages that are being disrupted in topic areas designated as contentious topics, or
    • appeal arbitration enforcement actions (including contentious topic restrictions) to uninvolved administrators.

    For all other problems, including content disagreements or the enforcement of community-imposed sanctions, please use the other fora described in the dispute resolution process. To appeal Arbitration Committee decisions, please use the clarification and amendment noticeboard.

    Only autoconfirmed users may file enforcement requests here; requests filed by IPs or accounts less than four days old or with less than 10 edits will be removed. All users are welcome to comment on requests except where doing so would violate an active restriction (such as an extended-confirmed restriction). If you make an enforcement request or comment on a request, your own conduct may be examined as well, and you may be sanctioned for it. Enforcement requests and statements in response to them may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. (Word Count Tool) Statements must be made in separate sections. Non-compliant contributions may be removed or shortened by administrators. Disruptive contributions such as personal attacks, or groundless or vexatious complaints, may result in blocks or other sanctions.

    To make an enforcement request, click on the link above this box and supply all required information. Incomplete requests may be ignored. Requests reporting diffs older than one week may be declined as stale. To appeal a contentious topic restriction or other enforcement decision, please create a new section and use the template {{Arbitration enforcement appeal}}.

    Appeals and administrator modifications of contentious topics restrictions

    The Arbitration Committee procedures relating to modifications of contentious topic restrictions state the following:

    All contentious topic restrictions (and logged warnings) may be appealed. Only the restricted editor may appeal an editor restriction. Any editor may appeal a page restriction.

    The appeal process has three possible stages. An editor appealing a restriction may:

    1. ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision;
    2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and
    3. submit a request for amendment ("ARCA"). If the editor is blocked, the appeal may be made by email.

    Appeals submitted at AE or AN must be submitted using the applicable template.

    A rough consensus of administrators at AE or editors at AN may specify a period of up to one year during which no appeals (other than an appeal to ARCA) may be submitted.

    Changing or revoking a contentious topic restriction

    An administrator may only modify or revoke a contentious topic restriction if a formal appeal is successful or if one of the following exceptions applies:

    • The administrator who originally imposed the contentious topic restriction (the "enforcing administrator") affirmatively consents to the change, or is no longer an administrator; or
    • The contentious topic restriction was imposed (or last renewed) more than a year ago and:
      • the restriction was imposed by a single administrator, or
      • the restriction was an indefinite block.

    A formal appeal is successful only if one of the following agrees with revoking or changing the contentious topic restriction:

    • a clear consensus of uninvolved administrators at AE,
    • a clear consensus of uninvolved editors at AN,
    • a majority of the Arbitration Committee, acting through a motion at ARCA.

    Any administrator who revokes or changes a contentious topic restriction out of process (i.e. without the above conditions being met) may, at the discretion of the Arbitration Committee, be desysopped.

    Standard of review
    On community review

    Uninvolved administrators at the arbitration enforcement noticeboard ("AE") and uninvolved editors at the administrators' noticeboard ("AN") should revoke or modify a contentious topic restriction on appeal if:

    1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
    2. the action was not reasonably necessary to prevent damage or disruption when first imposed, or
    3. the action is no longer reasonably necessary to prevent damage or disruption.
    On Arbitration Committee review

    Arbitrators hearing an appeal at a request for amendment ("ARCA") will generally overturn a contentious topic restriction only if:

    1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
    2. the action represents an unreasonable exercise of administrative enforcement discretion, or
    3. compelling circumstances warrant the full Committee's action.
    1. The administrator may indicate consent at any time before, during, or after imposition of the restriction.
    2. This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator.
    Appeals and administrator modifications of non-contentious topics sanctions

    The Arbitration Committee procedures relating to modifications and appeals state:

    Appeals by sanctioned editors

    Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may:

    1. ask the enforcing administrator to reconsider their original decision;
    2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and
    3. submit a request for amendment at the amendment requests page ("ARCA"). If the editor is blocked, the appeal may be made by email through Special:EmailUser/Arbitration Committee (or, if email access is revoked, to arbcom-en@wikimedia.org).
    Modifications by administrators

    No administrator may modify or remove a sanction placed by another administrator without:

    1. the explicit prior affirmative consent of the enforcing administrator; or
    2. prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below).

    Administrators modifying sanctions out of process may at the discretion of the committee be desysopped.

    Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied.

    Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions.

    Important notes:

    1. For a request to succeed, either
    (i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or
    (ii) a passing motion of arbitrators at ARCA
    is required. If consensus at AE or AN is unclear, the status quo prevails.
    2. While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify.
    3. These provisions apply only to contentious topic restrictions placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorized by the committee, and enacted either by arbitrators or by arbitration clerks, or to special functionary blocks of whatever nature.
    4. All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue.
    Information for administrators processing requests

    Thank you for participating in this area. AE works best if there are a variety of admins bringing their expertise to each case. There is no expectation to comment on every case, and the Arbitration Committee (ArbCom) thanks all admins for whatever time they can give.

    A couple of reminders:

    • Before commenting, please familiarise yourself with the referenced ArbCom case. Please also read all the evidence (including diffs) presented in the AE request.
    • When a request widens to include editors beyond the initial request, these editors must be notified and the notifications recorded in the same way as for the initial editor against whom sanctions were requested. Where some part of the outcome is clear, a partial close may be implemented and noted as "Result concerning X".
    • Enforcement measures in arbitration cases should be construed liberally to protect Misplaced Pages and keep it running efficiently. Some of the behaviour described in an enforcement request might not be restricted by ArbCom. However, it may violate other Misplaced Pages policies and guidelines; you may use administrative discretion to resolve it.
    • More than one side in a dispute may have ArbCom conduct rulings applicable to them. Please ensure these are investigated.

    Closing a thread:

    • Once an issue is resolved, enclose it between {{hat}} and {{hab}} tags. A bot should archive it in 7 days.
    • Please consider referring the case to ARCA if the outcome is a recommendation to do so or the issue regards administrator conduct.
    • You can use the templates {{uw-aeblock}} (for blocks) or {{AE sanction}} (for other contentious topic restrictions) to give notice of sanctions on user talk pages.
    • Please log sanctions in the Arbitration enforcement log.

    Thanks again for helping. If you have any questions, please post on the talk page.

    Arbitration enforcement archives
    1234567891011121314151617181920
    2122232425262728293031323334353637383940
    4142434445464748495051525354555657585960
    6162636465666768697071727374757677787980
    81828384858687888990919293949596979899100
    101102103104105106107108109110111112113114115116117118119120
    121122123124125126127128129130131132133134135136137138139140
    141142143144145146147148149150151152153154155156157158159160
    161162163164165166167168169170171172173174175176177178179180
    181182183184185186187188189190191192193194195196197198199200
    201202203204205206207208209210211212213214215216217218219220
    221222223224225226227228229230231232233234235236237238239240
    241242243244245246247248249250251252253254255256257258259260
    261262263264265266267268269270271272273274275276277278279280
    281282283284285286287288289290291292293294295296297298299300
    301302303304305306307308309310311312313314315316317318319320
    321322323324325326327328329330331332333334335336337338339340
    341342343344345346

    Apteva

    Apteva is warned about possible discretionary sanctions under Misplaced Pages:Arbitration/Requests/Case/Article titles and capitalisation. The restriction concerning Misplaced Pages:Article titles imposed by SarekOfVulcan and logged at Misplaced Pages:Arbitration/Requests/Case/Article titles and capitalisation#Log of blocks, bans, and restrictions is rescinded by consensus among uninvolved administrators at this noticeboard.  Sandstein  20:52, 27 January 2013 (UTC)
    The following discussion has been closed. Please do not modify it.

    Request concerning Apteva

    User who is submitting this request for enforcement
    SarekOfVulcan (talk) 11:48, 22 January 2013 (UTC)
    User against whom enforcement is requested
    Apteva (talk · contribs · deleted contribs · logs · filter log · block user · block log)
    Sanction or remedy to be enforced
    Misplaced Pages:Arbitration/Requests/Case/Article titles and capitalisation#Log of blocks, bans, and restrictions (Article titles)
    Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
    1. 21 January 2013 (See explanation below)
    Diffs of notifications or of prior warnings against the conduct objected to (if required)
    1. Warned on 3 January 2013 by SarekOfVulcan (talk · contribs)
    Additional comments by editor filing complaint

    During a related edit war, Apteva started a discussion on 2 January, seen at Misplaced Pages talk:Article titles/Archive 39#Common names, regarding the excessive number of examples at WP:AT#Common names. The last edit to that particular thread was on 6 January, with Apteva asking Are any other examples needed, or are three plenty?. Having no other input, he implemented the results of the discussion in the diff above, citing "per talk", but not linking directly to the archived discussion. (Blueboar, not seeing the discussion on the active talkpage, reverted.) Noetica posted on my talkpage requesting that I sanction Apteva, per the discretionary sanctions I imposed above to end the edit war on a policy page.

    However, since the last line of the logged sanction explicitly said Should a consensus discussion determine that there don't need to be 21 examples, ... that of course will not call for a block I'm not sure that there's a violation here. Therefore, I've brought the request here for independent review. Did Apteva have sufficient consensus for his edit? If so, is Noetica's request for a block tendentious, and does it call for a block itself? Thanks.

    @Sandstein -- honestly, I don't think that edit was a violation of the sanctions, as it took place after an attempt at consensus discussion. However, Noetica argued on my talkpage that it was, and I didn't feel comfortable making the call in either direction myself, so I brought it here. There's currently another discussion dealing with reducing the number of examples -- once that determines what the appropriate examples are (how many and which ones), the need for this sanction will go away. As far as the warning goes, everyone who needed to see it clearly did, as shown in the lack of edit warring on the policy page since then.--SarekOfVulcan (talk) 23:40, 22 January 2013 (UTC)
    Notification of the user against whom enforcement is requested

    Notified here

    Discussion concerning Apteva

    Statement by Apteva

    That was a consensus edit made per the discussion at Misplaced Pages talk:Article titles/Archive 39#Common names. Since it was reverted, it will be re-opened for further discussion. But per that discussion, a clear request was made are there any more examples that needed to be added, and since none were added, the draft was dropped in as required. "Are any other examples needed, or are three plenty?" To do anything less would have been irresponsible. Apteva (talk) 01:31, 23 January 2013 (UTC)

    As others have pointed out although the warning could be literally construed to mean that forever that specific example must always be at WP:AT until someone goes to Arb to get it lifted, few interpreted it that narrowly and instead construed it to mean that if anyone changed that and only that example as a bold edit and not as a consensus process they would be blocked for continuing an edit war. The edit war was completely unacceptable, and was not stopped until that warning was given, even though there was ongoing discussion about the list of examples. Normally no one expects to not be blocked who participates in an edit war instead of participating in an ongoing discussion and waiting until that discussion concludes before taking action. WP:AT is watched by approximately 600 editors, and it does not seem unreasonable to expect that if anyone had any objection to the three examples in the draft they would have said something during the two weeks between the final are three plenty question and when the page was archived. From 20:40, 2 January 2013 (UTC) when the talk page discussion started, the page was changed and finally with the "supervote" . These follow the three edits that occurred before 20:40, so in all the edit war consisted of eight edits. Seven minutes later we were warned not to restore that example which had been removed. I would have to construe it a "tag team" edit war, which I had no intention of starting, although I would stipulate that the initial edit (of the eight) was made for the purpose of disrupting Misplaced Pages to make a point. Apteva (talk) 22:09, 23 January 2013 (UTC)

    Per WP:BRD, if anyone is warned, it should be those who made the six edits after mine. While it is optional to do a BDR cycle instead of a BRD cycle, there really is nothing wrong with doing BRD, and a lot wrong with doing BRR... and no discussion. Apteva (talk) 22:15, 23 January 2013 (UTC)

    For the record, I prefer to be referred to in gender neutral terms, no matter how strange that seems to anyone who has not made the transition from calling everyone he and she, and using he for both. He/she, his/her, they, xe, even "it" works, but not he, and not she. Thanks. Apteva (talk) 19:14, 24 January 2013 (UTC)

    Comment. 1RR is not necessary on WP:AT. There is very little edit warring there and the edit war that did exist was a tag team edit war involving eight different editors and eight different edits. On the other hand reinstating the 1RR at MOS is warranted as the constant edit warring there is still continuing. Apteva (talk) 05:16, 26 January 2013 (UTC)

    Just as a comment, per WP:ARBATC#The Manual of Style the intent of a style guide is not to provide hard rules. For example, titles are often names of items, and it really should not be a part of the MOS to specify how titles are chosen. Up until October 2007, there was nothing in the MOS about choosing titles, but with this edit, someone who perhaps did not even know that we already had guidelines on how titles are chosen, but did know that we had a MOS, insisted that there needed to be a section in the MOS about how titles are chosen. I think that it has been way too contentious to refer to the MOS in choosing titles, and that all of that material should be moved back to WP:AT. In this edit the bold statement which was not discussed at WP:AT, was made that effectively WP:AT has no bearing on choosing titles, but only WP:MOS chooses titles. Since then much of the discussion at MOS has been about titles, all of which in my opinion is inappropriate, as only WP:AT and WP:RM decides titles, and the idea of "styling" an article title is farcical (styling only applies to choosing a font or font size, and that is done by the browser, not WP). Apteva (talk) 17:36, 26 January 2013 (UTC)

    • I would strongly recommend that that warning be given to the five editors who actually were edit warring, not myself, and to the editor who actually was being disruptive, not myself, for making the bold edit that led to that edit war. Apteva (talk) 14:45, 27 January 2013 (UTC)

    Comments by others about the request concerning Apteva

    @Cailil: Agreed. I noticed after adding the comment above that he was still participating at WT:AT. Mathsci (talk) 16:45, 22 January 2013 (UTC)

    Comments by NE Ent

    Making an edit and then declaring anyone who changes it will be AE blocked per Discretionary Sanctions is bogus. First of all, it's textbook involved -- being an admin doesn't give SoV a supervote on the content dispute. Secondly, Discretionary sanctions specifically require "the editor in question be given a warning", and the procedures for administrators specifically state:
    "4. Warnings should be clear and unambiguous, link to the decision authorising the sanctions, identify misconduct and advise how the editor may mend their ways;
    5. Notices of imposed sanctions should specify the misconduct for which they have been imposed as well as the appeal process;"
    In simpler terms -- if an admin is going to DS an editor they should be posting a notice on the editor's talk page.

    The log of the incorrect sanction should be deleted and this case closed. NE Ent 13:36, 22 January 2013 (UTC)

    Comments by Dicklyon

    Apteva has a habit of making himself very hard to ignore. His proposal to trim to 3 examples got zero support and got archived, yet he claims it would have been irresponsible for him to not go ahead and implement it, just because nobody extended his list. Very bogus. But is there an enforceable ban against such bullshit? I don't think so. Even his violations of his badly worded topic ban slide by. Teflon? Dicklyon (talk) 23:45, 23 January 2013 (UTC)

    Comments by Rschen7754

    MBisanz already gave Apteva a final warning. --Rschen7754 19:17, 24 January 2013 (UTC)

    Comments by GoodDay

    I'm assuming that whatever the arbitrators decide, that decision will also apply to Delphi234, which Apteva's an alternate account of. GoodDay (talk) 18:17, 26 January 2013 (UTC)

    Result concerning Apteva

    This section is to be edited only by uninvolved administrators. Comments by others will be moved to the section above.
    • Very early response. Awaiting Apteva's statement. Before going any further I do think Noetica should be named above and asked to make a statement as in fairness to them SoV is bringing up potential sanctions against them.
      From a prima facia review Apteva probably didn't have consensus for the change (especially given the warning s/he had from SoV) and as Blueboar's revert noted the talk thread wasn't linked to and even in that thread the issue isn't actually discussed. As far as I can see there was no discussion in relation to Apteva's questions "is three plenty?" (see the end of the first subsection of this thread) - in that context that edit does look tendentious to me, but I'd like to see other sysop's views--Cailil 12:41, 22 January 2013 (UTC)
    • @Mathsci: Apteva's community sanction is seperate. SoV has logged a specific page probation at Misplaced Pages:Article titles WRT this particular revert war, under the terms of the linked RFAR. It's this page probation that is being discussed and whether Apteva broke that, rather than his community sanction--Cailil 16:39, 22 January 2013 (UTC)
    • I don't see how this edit is in violation of any AE-enforceable restriction. From what I can tell, SarekOfVulcan's argument is that Apteva's edit was in violation of SarekOfVulcan's very informally worded talk page comment, which was apparently meant to be read as an order to other editors not to change "Halley" to "Halley-Bopp" or "Halley–Bopp", on pain of a block under the discretionary sanctions authority. However, even if one assumes arguendo that this order was a valid exercise of the discretionary sanctions authority, discretionary sanctions can only be imposed, per WP:AC/DS, after "the editor in question given a warning with a link to the decision authorizing sanctions". There's no diff in evidence indicating that a warning meeting these requirements was given to Apteva, especially in relation with the abovementioned order. Accordingly, I recommend closing this as not actionable. Furthermore, I doubt that SarekOfVulcan's order, as written, is a valid exercise of the discretionary sanctions authority. I don't think AE authority may be used to freeze a page in one's preferred state, if only because after editing the page one has become editorially involved and may no longer act in one's administrative capacity. I therefore strongly recommend that SarekOfVulcan rescind said order and remove it from Misplaced Pages:Arbitration/Requests/Case/Article titles and capitalisation#Log of blocks, bans, and restrictions, where it is logged in a confusing and lengthy manner.  Sandstein  23:27, 22 January 2013 (UTC)
    • I see that NE Ent above has made a very similar point, and I agree with them that SarekOfVulcan's "warning", such as it was, fell far short of the formal requirements for AE warnings that NE Ent cites.  Sandstein  23:31, 22 January 2013 (UTC)
    • I'd agree that Apteva was not directly warned. However the page in question has a very clear notification of AC/DS - I'd consider that sufficient constructive warning for all involved (especially in light of the numerous discussions they were having there). However I'd agree that SoV's approach was in the least novel, by making an edit himself. This was discussed on his talk page and the advice given was that he shouldn't implement any blocks - that's what he's doing in bringing it here. That said I think Sandstein and NE Ent have a point - even if SoV didn't intend (and in my view he didn't) to "freeze the page in a preferred state" it looks like he did. That makes the whole issue sufficiently ambiguous to create as much or more trouble than it is seeking to prevent.
      But there again we have Apteva continuing an edit war nearly a month after it was resolved with a claim of consensus that is not borne out on the talk page. In my view we CAN investigate Apteva's conduct vis-a-vis the RFAR even if we rescind SoV's warning. Such an investigation may result (and in my view it might be enough) with a final warning for Apteva but I don't think we should ignore this--Cailil 13:01, 23 January 2013 (UTC)
    In view of my above comment I haven't reviewed the context of Apteva's edit, but I've no objection to any appropriate warning.  Sandstein  21:00, 23 January 2013 (UTC)
    • I recommend lifting the specific restriction imposed by SarekOfVulcan on Misplaced Pages:Article titles, a sanction which can be undone by a consensus here. If Sarek had originally proposed this restriction at WP:AE instead of enacting it himself, it seems to me it would be unlikely to be approved. It is too adventurous and is open to many challenges. EdJohnston (talk) 17:50, 23 January 2013 (UTC)
    Agreed.  Sandstein  21:00, 23 January 2013 (UTC)
    Specifically looking at the sanction and enforcement request and not the surrounding issues of the edit having consensus or not, the sanction was very loosely worded and it appears, whether intentional or not, that the page was put in a locked state to enforce the right version with a sanction over top of it to stop anyone who did want to change it. Either way, the sanction was very loosely worded and I agree with Sandstien that we can't enforce it. With the wording at this level, and how it appears, I also agree that the sanction needs to be rescinded until overturned by the community as Ed worded it above. -- DQ (ʞlɐʇ) 22:18, 23 January 2013 (UTC)
    • Agree with rescinding SoV's sanction but I think we are missing the point significantly if we ignore Apteva's behaviour, which was clearly incompatible with the RFAR. (However in light of the lack of a direct warning re: this RFAR I would suggest issuing a final warning to Apteva & no harsher sanction at this time)--Cailil 17:14, 24 January 2013 (UTC)
    • I don't think we are ignoring Apteva's behavior; but if you feel it necessary, I have no objection to adding an official AE warning to those which they have already received. KillerChihuahua 19:19, 24 January 2013 (UTC)
    • I agree that we should give a DS warning to Apteva. Though I'm not sure implementing 1RR is going to do anything of benefit here. It appears already that the reverts have been mostly within that restriction already. -- DQ (ʞlɐʇ) 14:37, 26 January 2013 (UTC)
    • I don't particularly object to 1RR, but the need for applying such restrictions is not evident to me from the evidence submitted here, nor from the recent page histories.  Sandstein  14:49, 26 January 2013 (UTC)
    • The boilerplate will do, I think, because it's not very clear what Apteva is supposed to have done wrong except making an edit that allegedly did not reflect consensus. So closing.  Sandstein  20:48, 27 January 2013 (UTC)

    Noetica

    Attention: This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.

    Request concerning Noetica

    User who is submitting this request for enforcement
    Apteva (talk) 13:58, 27 January 2013 (UTC)
    User against whom enforcement is requested
    Noetica (talk · contribs · deleted contribs · logs · filter log · block user · block log)
    Sanction or remedy to be enforced
    Misplaced Pages:Arbitration/Requests/Case/Article titles and capitalisation#All parties reminded

    Here is someone you can warn about WP:ARBATC

    Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
    1. 27 January 2013 ARBCOM does not resolve content disputes, their role was just to stop everyone from arguing
    2. 27 January 2013 Such vitriolic serves no purpose and has nothing to do with improving this policy
    3. 27 January 2013 After two further edits to fix grammar
    Diffs of notifications or of prior warnings against the conduct objected to (if required)
    1. Warned on 3 January 2013 by Apteva (talk · contribs)
    2. Warned on 11 January 2013 by Born2cycle (talk · contribs)
    Additional comments by editor filing complaint

    Focusing on the editor is endemic at Misplaced Pages talk:MOS.

    Notification of the user against whom enforcement is requested

    Discussion concerning Noetica

    Statement by Noetica

    I thank Guerillero, Sandstein, and The Devil's Advocate for remarks made so far, either here or in the recently closed section regarding Apteva.

    I agree with The Devil's Advocate: this is terribly POINTy. Apteva has been causing widespread disruption to editors' work for months. At WP:MOS, WP:TITLE, many RMs (reopening old disputes that had been long settled), users' talkpages, the village pump, ArbCom itself (starting an action that was given short shrift), and so on. See Misplaced Pages:Requests for comment/Apteva and its talkpage, and lengthy discussions at WP:AN that followed. They resulted in a topic ban whose boundaries Apteva relentlessly tests. See the latest discussions of that provocation, initiated at WP:AN with this edit. Because I am centrally involved in the development of WP:MOS, but not an admin, I am vulnerable when I work toward order and harmony in its relations with WP:TITLE. I have had to play a part in actions against Apteva's anti-consensus campaign, and this AE application is just one episode in that campaign.

    Admin SarekOfVulcan became involved in a dispute at WP:TITLE over moves to include an example that was common to both WP:TITLE and WP:MOS, showing their harmony and natural accord. I have consistently claimed that this was settled by wide community consultation under ArbCom direction in 2011. Sarek is with Apteva in rejecting that accord, and in editing to reduce evidence of that accord. Sandstein has now rescinded the provision that Sarek added under the DS arrangements (see section concerning Apteva, above on this page). I objected at Sarek's talkpage to his acting as an admin while involved, as did some of his fellow admins. I am glad that Sandstein has sorted things out. In evidence, Apteva provides only diffs from WT:TITLE, in which I pointed out Sarek's compromised status as an admin attending to pages in which he pushes an agenda. I am glad that I will no longer have to do that, because as I say I am without the protection that some admins assume as their right.

    If I have time (always a problem), I will continue to insist on due process in development of core policy and guideline pages on Misplaced Pages. I expect to do so without impediments from abuse of power, or from ingeniously conducted campaigns to game the system. Apteva plays an interesting hand, with more than one RFA in recent times and even an RFB . No one has the resources to track all of those capers; but perhaps something more systematic might eventually be done about them.

    I request that this application be speedily dismissed, as purely vexatious.

    Noetica 22:11, 27 January 2013 (UTC)

    Comments by others about the request concerning Noetica

    Comment by The Devil's Advocate

    This seems like a terribly POINTy AE request given the above discussion regarding Apteva.--The Devil's Advocate tlk. cntrb. 18:47, 27 January 2013 (UTC)

    Comment by Guerillero

    I don't see any misconduct here --Guerillero | My Talk 20:59, 27 January 2013 (UTC)

    Result concerning Noetica

    This section is to be edited only by uninvolved administrators. Comments by others will be moved to the section above.
    • Awaiting Noetica's statement before examining the evidence. But I'm inclined to close this as nonactionable because the "All parties reminded" remedy is not accompanied by a corresponding enforcement provision. The enforcement provision of the decision refers to "user subject to an editing restriction", which the "All parties reminded" remedy does not provide for. Applying discretionary sanctions requires a warning that meets the requirements of WP:AC/DS#Sanctions, and no diff of such a warning is in evidence.  Sandstein  21:21, 27 January 2013 (UTC)
    • After considering the submitted evidence and Noetica's statement, I recommend closing this request either without action or with a discretionary sanctions warning to Noetica, similar to the one issued to Apteva in the preceding request. The grounds for the possible warning is that all other editors must abide by the requirement of WP:NPA to "comment on content, not on the contributor". In particular, they may not make broad allegations of bad faith or misconduct on the part of others. Such allegations are admissible only in the context of the resolution of conduct disputes and when they are supported by specific evidence in the form of diffs. In all other circumstances (e.g., in a policy talk page discussion) they must be avoided. The Arbitration Committee has recognized this in a decision, which I don't currently have at hand, that forbids "casting aspersions" on others by making broad, unsubstantiated allegations of misconduct. In the instant case, I tend to believe that while Noetica has alleged misconduct by others, they have done so with a sufficiently close focus on the dispute at issue (i.e., an administrator's disputed involvement) and/or citing evidence such as a now-concluded RfC. As such, a warning may not be required. But other administrators may view the matter differently.  Sandstein  23:01, 27 January 2013 (UTC)