After considering
/Evidence and discussing proposals with other Arbitrators, parties and others at
/Workshop, Arbitrators may place proposals which are ready for voting here. Arbitrators should vote for or against each point or abstain. Only items that receive a majority "support" vote will be passed. Conditional votes for or against and abstentions should be explained by the Arbitrator before or after his/her time-stamped signature. For example, an Arbitrator can state that she/he would only favor a particular remedy based on whether or not another remedy/remedies were passed. Only Arbitrators or Clerks should edit this page; non-Arbitrators may comment on the talk page.
For this case there are 13 active arbitrators, not counting 1 recused. 7 support or oppose votes are a majority.
If observing editors notice any discrepancies between the arbitrators' tallies and the final decision or the
#Implementation notes, you should
post to the
Clerk talk page. Similarly, arbitrators may request clerk assistance via the same method.
Proposed motions
Arbitrators may place proposed motions affecting the case in this section for voting. Typical motions might be to close or dismiss a case without a full decision (a reason should normally be given), or to add an additional party (although this can also be done without a formal motion as long as the new party is on notice of the case). Suggestions by the parties or other non-arbitrators for motions or other requests should be placed on the
/Workshop page for consideration and discussion. Motions have the same majority for passage as the final decision.
Template
1)
{text of proposed motion}
Support:
Oppose:
Abstain:
Proposed temporary injunctions
A temporary injunction is a directive from the Arbitration Committee that parties to the case, or other editors notified of the injunction, do or refrain from doing something while the case is pending.
Four net "support" votes needed to pass (each "oppose" vote subtracts a "support")
24 hours from the first vote is normally the fastest an injunction will be imposed.
Template
1)
{text of proposed orders}
Support:
Oppose:
Abstain:
Proposed final decision Information
Proposed principles
Decorum
1) [Old 2] Wikipedia users are expected to behave reasonably, calmly, and courteously in their interactions with other users; to approach even difficult situations in a dignified fashion and with a constructive and collaborative outlook; and to avoid acting in a manner that brings the project into disrepute. Unseemly conduct, such as
personal attacks,
incivility,
assumptions of bad faith,
trolling,
harassment,
disruptive point-making, and
gaming the system, is prohibited.
Per Coren and PhilKnight. Perhaps the missing piece to tie the principle to this case would be an added sentence at the end along the lines of "Administrators have the responsibility for enforcing these requirements, and are expected to do in a reasonable, thoughtful, and proportionate fashion" or some such.
Newyorkbrad (
talk)
11:16, 15 April 2011 (UTC)reply
2.1) [Old 8] Administrators who address Arbitration Enforcement requests handle one of the project's most sensitive and stressful administrator tasks; among other things, they must frequently assess and resolve complex issues arising from bitter long-term editing disputes and involving intractable and strongly opinionated editors. The Arbitration Committee appreciates the work performed by these administrators, without whom long-term remedies imposed in our decisions would be meaningless. To share the workload, the Committee encourages more administrators, particularly experienced ones, to become involved in this task. More administrators are also urgently needed to handle other tasks at the front lines of addressing user-conduct issues, such as review of unblock requests on-wiki and on the unblock-l mailing list.
2.2) [Old 1]Wikipedia administrators are trusted members of the community and are expected to follow all of
Wikipedia's policies and guidelines to the best of their abilities. Occasional mistakes are entirely compatible with this–administrators are not expected to be perfect–but consistently poor judgment may result in reapplication for adminship via the
requests for adminship procedure or suspension or revocation of adminship. If revoked, the user may have a temporary or permanent limitation placed on reapplying.
I will support, but this could use some copyediting; for example, "may result in reapplication for adminship via RfA" is unnecessary, as any required new RfA would follow a revocation (or perhaps a long-term suspension, but we don't do that much) of adminship. The last sentence, while true, also sets an unnecessarily harsh tone for the introduction to this case and I would omit it here.
Newyorkbrad (
talk) 11:14, 15 April 2011 (UTC) Second choice.
Newyorkbrad (
talk)
20:54, 17 April 2011 (UTC)reply
2.2.1) [Old 1.2]Administrators are trusted members of the community and are expected to follow Wikipedia policies and to perform their duties to the best of their abilities. Administrators should exercise care and judgment when using their tools and when
imposing sanctions delegated by the arbitration committee. Occasional mistakes by administrators are understandable, but consistently or egregiously poor judgment may result in the removal of administrator status. Administrators are expected to learn from experience and from justified criticisms of their actions.
2.3) [Old 10] An administrator's actions taken for purposes of Arbitration enforcement may be overturned following a clear, substantial, and active consensus of uninvolved editors, on the Arbitration Enforcement noticeboard or another appropriate venue, or in rare instances, by the Arbitration Committee on appeal. When this occurs, the administrator whose action was overturned should assess why others disagreed with the action, and take this into account in future decision-making. However, the administrator should not take the overturning as a personal rebuke; over time, every active administrator working anywhere on the project will have some of his or her administrator actions disagreed with or overturned, just as every arbitrator sometimes finds himself or herself in the minority on an issue voted on by the Committee.
This principle should be extended to other administrator-review functions--it just came up the other day at
WP:DRV. The focus is on getting the outcome right, and doesn't shift onto the administrator taking a reversed action until a pattern of repeated or egregious differences between actions taken and community expectations.
Jclemens (
talk)
14:32, 15 April 2011 (UTC)reply
What this is about is an individual administrator learning from mistakes. Could this be reflected in the heading? "Reacting positively to reversals" or similar as that provides a bit more context for the principle?
Roger Daviestalk05:31, 30 April 2011 (UTC)reply
Deliberate and careful use of discretionary sanctions
3.1) [Old 4.0] Because of the increased risk of disruption around enforcement of
discretionary sanctions,
Wikipedia administrators are expected to be especially deliberate and careful in applying their discretion and to seek consensus
in a suitable venue over unilateral action when there is no pressing need for immediate action.
Support:
There is no reason, for instance, where an administrator that notices problematic behavior from an editor that has already been warned cannot open a new enforcement request of their own impetus to discuss the matter with their peers before making most enforcement decisions. —
Coren(talk)14:59, 14 April 2011 (UTC)reply
No. Everything so far from the Arbitration Committee in regard to discretionary sanctions has been based around 'any uninvolved admin', if we are changing this towards a consensus model that should be a remedy, not a principle.
PhilKnight (
talk)
16:10, 14 April 2011 (UTC)reply
This is ok, but I would like something stronger—that decisions must be supported by independent uninvolved admins users at AE unless there is a pressing need for action. I would also prefer to leave out the word "consensus" because the sanctioned party rarely agrees, and partisans on his or her "side" frequently also oppose sanction. If we want to use the c-word, let's at least say "consensus of uninvolved users."
Cool HandLuke15:36, 14 April 2011 (UTC)reply
I don't mind a rewording in that direction; my problem is with unilateral action without discussion when there is no pressing need to do so. Tweaked accordingly. —
Coren(talk)16:33, 14 April 2011 (UTC)reply
Deliberate and careful use of discretionary sanctions (alt 1)
3.1.1) [Old 4.1] Because of the increased risk of disruption around enforcement of
discretionary sanctions,
Wikipedia administrators are expected to be especially deliberate and careful in applying their discretion and to first prefer seeking support of uninvolved editors
in a suitable venue over unilateral action when there is no pressing need for immediate action.
Support:
I recognize this is a departure, but this case was taken so that we would slightly modify AE; it's been far too cowboy. I think this proposal strikes a good balance by keeping the process unyoked from the heavy burden of CONSENSUS, but by requiring some third-party support when the situation is not urgent.
Cool HandLuke02:40, 15 April 2011 (UTC)reply
With great power comes great responsibility--responsibility which, had it been appropriately exercised in the first place, would have avoided this fiasco entirely.
Jclemens (
talk)
03:15, 15 April 2011 (UTC)reply
Except it HAD been appropriately exercised, you noticed that the finding was that while the remedy wasn't the greatest from Sandstein, there was no consensus to remove it? Seems to me that in lawyer speak, I'd be saying "Objection, assumes facts not in evidence".
SirFozzie (
talk)
04:16, 15 April 2011 (UTC)reply
My evaluation of the appropriateness of such exercise is informed, but not bound, by the community's or the committee's findings. It's been obvious from our first discussions of the case that the committee is of multiple minds on this.
Jclemens (
talk)
05:49, 15 April 2011 (UTC)reply
Same as 3.1 4.0. We have a situation where there are enough "uninvolved" editors who "just happen to show up" with normal issues, and AE is hyper focused on things that can have significant amount of push back from the sanctioned editor's colleagues only makes it worse. I prefer the current situation, as MastCell says, AE in GENERAL is not a significant source of harm to the project.
SirFozzie (
talk)
21:50, 14 April 2011 (UTC)reply
Did you mean to say there are not enough uninvolved editors? Honestly, I'm not sure what incentive an uninvolved editor would have to participate with restraint when any other admin can shoot from the hip without any realistic chance of being reversed. If this is not the root of the problem (which I think it is, and Coren apparently does as well), what part of AE in PARTICULAR is harmful to the project?
Cool HandLuke03:51, 15 April 2011 (UTC)reply
No, I'm saying there's "uninvolved" editors, and by that, I mean "Really involved/partisan but will say they're not so they can prevent fellow partisans from being sanctioned." I'm saying AE in general is NOT harmful, period, as MastCell does on the talk page. Are there problematic actions taken? Obviously, but not enough I think to change AE, and this is speaking as someone who's worked there. The admins working there need our support, not having their hands tied further.
SirFozzie (
talk)
04:14, 15 April 2011 (UTC)reply
Deliberate and careful use of discretionary sanctions
3.1.2) [Old 4.2] Because of the priority given to enforcement of
discretionary sanctions, administrators must be deliberate and careful in applying their discretion to impose sanctions. In general, sanctions should be imposed in situations where there has been a serious violation or a pattern of violations of a remedy contained in an Arbitration Committee decision, and a prior warning or warnings have not resolved the problem. When it is not entirely clear whether a sanction is appropriate, or when an administrator knows that there is a division of opinion regarding whether a sanction is warranted, and there is no pressing need for immediate action, it may be best for an administrator to raise the issue
in the discussion venue for Arbitration Enforcement and seek a consensus, rather than to act unilaterally.
This is not written as a remedy. Is your position that modifications to policies should be listed as remedies because they're new? I don't think that's the correct distinction: our principles often fill in gaps between policies with common sense. In this case, the underlying policy is our own construction, and if we were to formally modify it we would not call such amendment a "remedy."
Cool HandLuke23:51, 15 April 2011 (UTC)reply
3.2) [Old 7] In imposing a sanction or giving a warning based on an Arbitration Committee decision, an administrator should clearly specify the basis of the action and the reasons it is being taken. The scope of any sanction imposed should also be specified as clearly as possible. A sanctioned editor may respond by asking the sanctioning administrator, in a civil fashion, to explain or to reconsider the imposition or scope of the sanction. The administrator should respond to appropriate questions raised by the sanctioned editor, and when appropriate should also advise the editor that he or she may request a review of the sanctions by a request to the Arbitration Enforcement noticeboard.
Support:
I'm adding three principles now, and perhaps one or two more later on. This one sets forth some expectations and recommendations, for clarity and emphasis. This is not meant to suggest that these procedures were not followed in this case.
Newyorkbrad (
talk)
11:52, 15 April 2011 (UTC)reply
Yes. Particularly in this case, there's a school of thought that says that had the warning in this case been clearer and explicitly advised what was expected (ie redaction), the subsequent block would not have been placed and therefore there would have been nothing to overturn.
Roger Daviestalk05:22, 30 April 2011 (UTC)reply
Like Roger says, clear warnings can stop a problem in its tracks; there are some reasonable differences of opinion here about whether a different warning might have had a different outcome.
Shellbabelfish11:50, 4 May 2011 (UTC)reply
Oppose:
Abstain:
Arbitration case sanctions
3.3) [Old 3] The scope of sanctions imposed as remedies in arbitration cases should be clearly defined so as to avoid later misunderstandings and disagreements. A sanction remedy should also clearly specify the duration of the sanction and the procedure, if any, available to the sanctioned user to seek lifting or modification of the sanction in due course.
Opposing until this is clarified ... Is this principle saying that the scope of discretionary sanctions for any particular topic should be defined in the case remedy on a case by case basis? Don't we already do that in the area of conflict stuff? Or it is saying that the type of available sanction needs to specified in the case remedy? I agree that santioned editors need to be informed about appeal options but I'm slightly unclear about "the procedure, if any". Aren't there numerous appeal options already available?
Roger Daviestalk05:13, 30 April 2011 (UTC)reply
This principle was taken from the
Henri Coanda case, where you supported it. However, if you feel that it can be improved, then I suggest you go ahead and create an alternative.
PhilKnight (
talk)
13:33, 30 April 2011 (UTC)reply
Sure but context is everything ... and in Henry Coanda it was about specific case remedies rather than discretionary sanctions. As, in the context of this case, it can easily be misunderstood/misconstrued, I'm not sure that it, or an alternative, really helps much :)
Roger Daviestalk13:44, 30 April 2011 (UTC)reply
3.4) [Old 6] Arbitration remedies are a powerful but blunt instrument to protect areas of the project that have already proven difficult. They should not be invoked where normal policy and practice would suffice to resolve a problem, or where a lesser remedy would be adequate.
Support:
A pithy way of restating this might be "Thou shall not take
AE's name in vain". Because enforcement actions are more powerful, they should be used as little as possible. —
Coren(talk)14:59, 14 April 2011 (UTC)reply
First, this strikes me was very gameable: this argument is always available ("your AE request was invalid because you provided no evidence ANI wouldn't work!"). Second, discretionary sanctions only exist because the "community" failed to resolve a dispute. Within those topics, I think AE is the presumptively correct venue. AE admins should understand that a range of lesser remedies will be appropriate in many cases. AE has
every tool at its disposal, from blocks up to one year (or much shorter), topic bans, page bans, and "any other measures which the imposing administrator believes are reasonably necessary." If AE is failing to properly give out the lesser remedies when appropriate, we should reform AE rather than insist that small stuff be handled by "normal policy and practice." (If AE is abnormal, it ought not to be.)
Cool HandLuke15:47, 14 April 2011 (UTC)reply
Before becoming an arbitrator, I was an admin who handled requests at
WP:AE, and my approach was that, in general, sanctions that resulted from reports to the
WP:AE noticeboard should be logged as enforcement sanctions. While we could stipulate this approach is wrong, that should be a remedy, instead of a principle.
PhilKnight (
talk)
16:13, 14 April 2011 (UTC)reply
I stated in the workshop something similar, that AE is not a hammer, and not every editor under those sanctions is a nail.. but we put discretionary sanctions in to give administrators more options, this and other findings would restrict them more then I feel comfortable with.
SirFozzie (
talk)
16:34, 14 April 2011 (UTC)reply
I would prefer a revised version that takes the opposers' comments into account. (Some of this may now be covered by my new 3.1.2 4.2, if adopted.)
Newyorkbrad (
talk)
11:30, 15 April 2011 (UTC)reply
4.1) [Old 5] Arbitration enforcement should not be reversed unilaterally: it is not appropriate for an administrator to simply substitute their judgment for another's. Even if the disagreeing administrator believes that the enforcement action was erroneous or mistaken and discussion with the enforcing administrator has not led to a solution, substantial community consensus or Committee permission must be sought before overturning an act explicitly stated to be pursuant to an arbitration remedy.
Support:
Specifically, an administrator preparing to overturn such a decision needs to realize that they are exactly as likely, in the end, to be in error about the validity of the enforcement action than the original admin might have been. —
Coren(talk)14:59, 14 April 2011 (UTC)reply
I also agree with JClemens, but would add that as a new principle. Once an explained AE decision is made, it should not be overturned easily.
Cool HandLuke21:05, 16 April 2011 (UTC)reply
Although I can imagine an exception for blatant or obvious errors, which we might want to write in. With regard to Jclemens' point below, I might support a principle in line with his comment, but think it raises a separate (albeit related) issue to this one.
Newyorkbrad (
talk)
11:29, 15 April 2011 (UTC)reply
I think it would add an appropriate level of responsibility (see above) to require detailed and specific justification for AE sanctions. Part of the problem in this case was that the blocking admin referred to a block as an AE block without appropriate explanation, such that other editors not participating in the discussion were not able to see how the block was, in fact, an AE block. Blocks are not AE blocks because the blocking administrator calls them AE blocks, they are AE blocks because they are applied pursuant to the specific constraints of a previously enacted remedy. The presumption that a mere "this is an AE block!" statement makes a block a valid AE block until proven otherwise by widespread consensus is inappropriate.
Jclemens (
talk)
03:23, 15 April 2011 (UTC)reply
Comes at "Trusilver" from a slightly different angle. For clarity, I'd rather have just one principle on this, using the Trusilver text verbatim, which is elsewhere here.
Roger Daviestalk05:18, 30 April 2011 (UTC)reply
My point is, the Trusilver text applies of this principle by setting out a specific procedure. It's the "remedy" to this principle. —
Coren(talk)15:04, 30 April 2011 (UTC)reply
4.2) [Old 9] In March 2010, the Committee by
motion specified the procedure for overturning discretionary sanctions. The applicable section reads:
Administrators are prohibited from reversing or overturning (explicitly or in substance) any action taken by another administrator pursuant to the terms of an active arbitration remedy, and explicitly noted as being taken to enforce said remedy, except:
(a) with the written authorization of the Committee, or
(b) following a clear, substantial, and active consensus of uninvolved editors at a community discussion noticeboard (such as
WP:AN or
WP:ANI). If consensus in such discussions is hard to judge or unclear, the parties should submit a request for clarification on the
proper page.
Any administrator that overturns an enforcement action outside of these circumstances shall be subject to appropriate sanctions, up to and including desysopping, at the discretion of the Committee.Administrators who consistently make questionable enforcement administrative actions, or whose actions are consistently overturned by community or Arbitration Committee discussions may be asked to cease performing such activities or be formally restricted from taking such activities.
The description of good practice is a principle; that it was adopted in a prior decision is a fact; if we instruct people to abide by it going forward it's a remedy. Given the need to finish this case and to focus on the substance of our decision at this stage rather than matters of form, I don't think we should debate at length which section or sections of the decision this paragraph belongs in.
Newyorkbrad (
talk)
02:24, 1 May 2011 (UTC)reply
Although I think we took the case to review wider issues relating to the Arbitration enforcement process, not primarily this single block and unblock.
Newyorkbrad (
talk)
11:58, 15 April 2011 (UTC)reply
Concur, as far as it goes. The root cause was an editing dispute on
Talk:Pseudoscience which led Ludwigs2 to initiate a thread at
the administrator noticeboard. It should be noted that the initial dispute was not addressed by the community, whose attention was diverted by the block of Ludwigs2. However, the reason for accepting the case surrounds the actions described in this finding.
Risker (
talk)
19:47, 1 May 2011 (UTC)reply
2) In accepting this case, several arbitrators
expressly did so as an opportunity to examine the general background to
arbitration enforcement and to consider the underlying principles involved.
I had concerns, both specific and general with regards to AE. So far, after reviewing the notes, my concerns have GENERALLY been ameliorated, not to say I think everything out of AE is perfect, mind you.
SirFozzie (
talk)
10:26, 18 April 2011 (UTC)reply
As a pure matter of drafting style, I prefer to work this into the locus finding rather than treat it in a separate paragraph. However, I strongly suspect that no one else cares.
Newyorkbrad (
talk)
21:54, 18 April 2011 (UTC)reply
3) This dispute was triggered by a
posting made by Ludwigs2 on 8 March 2011 at the Administrators' Noticeboard. The last paragraph of Ludwigs2's posting contained inappropriate remarks, which included: "if you don't do something to get him to fly right you'll leave me with no choice except to shout him down and shut him up" and " if I have to go that route things will get progressively more ugly".
This wouldn't have warranted an arbitration case in and of itself, but it's relevant as background, and I can't say that Lugwigs2 was so innocent in the situation that it's inherently unfair to mention him.
Newyorkbrad (
talk)
02:27, 1 May 2011 (UTC)reply
I will note that Ludwigs2's use of intemperate language had the effect of distracting reviewing administrators and community members from the issue that he sought to draw attention to, and as such was pretty much an own goal; I have noticed similar but less colourful posts during this case as well. Ludwigs2 should seriously consider moderating the tone of future posts so that hyperbolic language does not overshadow the subject of his commentary or, in some situations, consider whether or not his comments are more likely to assist other readers or distract them from the subject.
Risker (
talk)
20:02, 1 May 2011 (UTC)reply
4) Ludwigs2 had been previously notified about the Pseudoscience discretionary sanctions, in respect of
another case in
September 2008.
Among other things, the notification stated "These editing restrictions may be applied to any editor for cause, provided the editor has been previously informed of the case. This message is to so inform you. This message does not necessarily mean that your current editing has been deemed a problem; this is a template message crafted to make it easier to notify any user who has edited the topic of the existence of these sanctions."
The notification also states: "Prior to any sanctions being imposed, the editor in question shall be given a warning with a link to this decision; and, where appropriate, should be counseled on specific steps that he or she can take to improve his or her editing in accordance with relevant policies and guidelines."
Background; but note the recent discussion, in an unrelated request for clarification, in which we discussed whether these general "notice to all editors on the articles" notices constitute the type of "warnings" that should precede the imposition of discretionary sanctions.
Newyorkbrad (
talk)
22:03, 24 April 2011 (UTC)reply
5) On 8 March 2011, Ludwigs2 was warned by Sandstein both in the
AN thread and on
Ludwigs2's talk page that a block was contemplated. The AN message stated that Ludwigs2 "had previously been warned" and linked to the
September 2008 message.
6) Sandstein's warning message to Ludwigs2 requested the latter to "show cause why [he] should not be sanctioned" within two hours of his next edit. Ludwigs2 requested that Sandstein clarify his warning at both his own talk page
[2] and the noticeboard thread
[3]. Sandstein did not respond further to Ludwigs2, but proceeded to block him less than two hours after his initial warning.
[4]
I can support this although a copyedit per SirFozzie would be welcome. I note that "show cause" as Sandstein used the term in his notification is a "legalism" (see
order to show cause). Although not as opaque to laypersons as some legalisms, the terminology might not have been fully understood.
Newyorkbrad (
talk) 22:08, 24 April 2011 (UTC) (adding for clarity) ... although, per PhilKnight below, the import of the message as a whole should have been.
Newyorkbrad (
talk)
20:32, 26 April 2011 (UTC)reply
Accurate finding of fact. I concur with PhilKnight that Sandstein's post on
WP:AN was more explanatory than the one on Ludwigs2's talk page; however, both posts invited discussion rather than action, and it was a reasonable interpretation that Sandstein was initiating a (two-way) discussion rather than planning to block if he did not find Ludwigs2's first comment to meet his expectations to "show cause".
Risker (
talk)
20:14, 1 May 2011 (UTC)reply
The show cause was to remove it or explain why he should not be sanctioned. This is an abstain rather than oppose because I understand that I was familiar with the term used, but others may not be.
SirFozzie (
talk)
02:33, 24 April 2011 (UTC)reply
"Show cause" barely has that meaning even among lawyers; a reasonable (perhaps even more reasonable) interpretation is "explain why you should not be sanctioned for the remarks you have already made."
Cool HandLuke14:00, 3 May 2011 (UTC)reply
Sandstein said "But I am concerned about the following statement by Ludwigs2 above: "I'm dropping this in your lap now, because if you don't do something to get him to fly right you'll leave me with no choice except to shout him down and shut him up. I'm very capable of doing that (as some of you should be aware), but if I have to go that route things will get progressively more ugly." That sounds like a threat to me. Threats are not an acceptable mode of dispute resolution. Ludwigs2 has previously been warned that they may be subject to discretionary sanctions if they violate community norms in the pseudoscience topic area. I therefore invite Ludwigs2 to show cause why they should not be sanctioned for making threats against others." In this context, for Ludwigs2 to say 'what are you talking about' is inadequate. Ok, he may not have understood the phrase 'show cause', but he must have understood the rest of the comment. Consequently, he should have retracted his threats.
PhilKnight (
talk)
19:03, 25 April 2011 (UTC)reply
8) A little over three hours later,
Dreadstar(
talk·contribs·blocks·protections·deletions·page moves·rights·RfA) unblocked the editor while clearly aware that the block was done pursuant to an arbitration remedy
[8][9]. While the applicability and propriety of the block was disputed and under discussion
[10], there was no consensus to overturn the enforcement action at that time (nor, indeed, did Dreadstar claim there was or that he was acting accordingly).
Support:
Dreadstar clearly believed that the block was erroneous (or at least erroneously claimed to be arbitration enforcement); but "I'm right and you're wrong" is not sufficient rationale to
ignore process — if only because everyone acts under a presumption that they are correct, including the blocking admin. —
Coren(talk)16:29, 14 April 2011 (UTC)reply
I will support, but I'm not sure we've captured all aspects of Dreadstar's thinking here. Although Dreadstar did not claim there was a "consensus to overturn the administrator action," he did reference several editors' support for an unblock at the time he unblocked. Most important, I find Dreadstar's evidence that he did not understand at the time the procedures required to overturn an AE block, and his assurance that he will not do so without consensus in the future (or at all with regard to this particular editors), to be credible.
Newyorkbrad (
talk)
11:58, 15 April 2011 (UTC)reply
You're opposing a finding of fact. Since the first sentence appears pretty straightforward, would you care to propose alternative wording that ameliorates your problems with the second?
Jclemens (
talk)
05:14, 24 April 2011 (UTC)reply
The unblock without discussion or consensus of an AE block (and despite claims otherwise, there has been no evidence that would lead me to believe it wasn't one) taints this action.
SirFozzie (
talk)
15:27, 25 April 2011 (UTC)reply
I'm not going to support this finding, or its alternatives, because — while strictly accurate — they create an impression that is contrary to plainly observable facts: Dreadstar did not try to apply arbitration enforcement differently, he believed arbitration enforcement did not apply at all in the first place. If he had clearly believed this was an arbitration enforcement matter at the time of the unblock, this would be an aggravating finding and certainly not a mitigating one. —
Coren(talk)15:01, 30 April 2011 (UTC)reply
This is about Dreadstar and Ludwigs2, Sandstein's finding that the statements were threats of disruption was already addressed.
Risker (
talk)
03:19, 2 May 2011 (UTC)reply
I'm explaining why, at the time I am voting, I oppose this finding. I've no objection to the idea that this finding of fact was proposed.
Risker (
talk)
04:18, 2 May 2011 (UTC)reply
This covers additional ground that 9 does not address, so it's hard to pick a "first choice" among them. Might a third version be appropriate? Alternatively, a separate FoF on Ludwigs2's statements might work. Regardless, I don't oppose this, I'm just not sure it's scoped right.
Jclemens (
talk)
01:12, 27 April 2011 (UTC)reply
9.2) Sandstein interpreted remarks in the last paragraph of
Ludwigs2's initial AN post as threats to disrupt. After unblocking Ludwigs2, Dreadstar
instructed Ludwigs2 to strike the contentious remarks. Ludwigs2 duly
redacted them.
Support. I don't get the problem with sticking to the facts here, contra SirFozzie below. We're taking each of the two administrators at their word here, largely because their conduct was internally consistent and each has acknowledged deficiencies. I don't see this wording rewarding anyone.
Jclemens (
talk)
21:30, 29 April 2011 (UTC)reply
Ugh. Half support, half oppose (again, it doesn't excuse what he did before hand, and it seems like we're praising him for it, which rubs me the wrong way). Going to think about it, but Abstain for now.
SirFozzie (
talk)
20:49, 29 April 2011 (UTC)reply
10) While it was generally agreed during the ensuing discussion that an arbitration enforcement block was probably not the best solution in this case, there was no clear consensus that the block should have been overturned
[12].
I view the ideas of "was an appropriate AE block" and "should have been overturned as it transpired" as separate issues. I think it's clear that the manner in which the unblock was done was itself suboptimal and drama-producing, even if the block was not a valid AE block.
Jclemens (
talk)
14:35, 15 April 2011 (UTC)reply
This FoF isnt wrong per se, however it will result in the wrong decision if this passes in absence of a determination on whether the block was a valid AE block. "suboptimal" and "drama-producing" are par for the Wikipedia course, especially for contentious blocks & unblocks are discussed at the administrative noticeboards. John Vandenberg(
chat)20:48, 20 April 2011 (UTC)reply
I'm not sure I see what you mean, John. It was clearly stated to be an AE block, and it invoked a specific discretionary sanction. Whether or not it was a good AE block is not material to whether it was one — though I think that the lack of consensus to overturn it shows that it was, at least, a defensible interpretation of the remedy. —
Coren(talk)16:05, 17 April 2011 (UTC)reply
My oppose is not regarding whether or not it was a good or bad AE block; there are many AE blocks which are undeniably AE blocks and whether they are "good" or "bad" is often very subjective and depending on the POV&alliances of the person making that assessment. OTOH, this block made it to ArbCom because saying it is an AE block doesnt make it one. This is 2011, and both the community and arbcom have expectations about what can be appropriately called an AE block. They haven't been codified until now, and that is an important component of this case. John Vandenberg(
chat)20:41, 20 April 2011 (UTC)reply
11) In
Dreadstar's evidence, Dreadstar acknowledges that he made an error of judgment, has apologised for unblocking Ludwigs2, and has promised that he will not act similarly in respect of discretionary sanction in the future.
The reason a desysop is unnecessary has nothing to do with Dreadstar's apology. While an appropriate gesture, the problems with the block itself place the desysoping of Dreadstar out of consideration.
Jclemens (
talk)
05:16, 24 April 2011 (UTC)reply
I agree with this for exactly the opposite reasons Jclemens does: whether the block had problems or not, it's the assurance that such an unilateral unblock with not happen again that makes it unnecessary to desysop. —
Coren(talk)15:09, 30 April 2011 (UTC)reply
12) In
Sandstein's evidence, Sandstein has expressed regret for shortcomings in communications with Ludwigs2 and has promised to take more care to avoid miscommunication in the future.
Poor communication in the initial warning was certainly a significant factor in the escalation of the situation.
Risker (
talk)
03:29, 2 May 2011 (UTC)reply
As previously stated, does not, in my opinion, rise to the level of needing a finding.
SirFozzie (
talk) 02:33, 24 April 2011 (UTC) convinced by actions related to but not part of this case to switch to support.
SirFozzie (
talk)
07:50, 1 May 2011 (UTC)reply
Not sure that an arbitration finding is needed here; perhaps this could be briefly folded into the Sandstein-related paragraph above.
Newyorkbrad (
talk)
23:37, 24 April 2011 (UTC)reply
Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.
I don't think there is any doubt that this unilateral unblock was the wrong thing to do, but given Dreadstar's apparent motivation and their clear statement that they will not repeat the mistake, there is no reason to sanction them further. —
Coren(talk)12:47, 17 April 2011 (UTC)reply
(first Choice). Per Coren. I put strongly admonished in my workshop but that's because if there was a similar incident down the road, we all know what the likely result will be.
SirFozzie (
talk)
02:40, 18 April 2011 (UTC)reply
I'm not certain this is essential, as it appears more than clear that Dreadstar has gotten the message by now, but I will support it to bring the issue to a result.
Newyorkbrad (
talk)
17:27, 2 May 2011 (UTC)reply
I would support "reminded", but I think "admonished" is too strong a remedy unless there's a finding that Dreadstar's action was premeditated and/or partisan. While this has been alleged in evidence, no proposed finding has yet been put forth on this.
Jclemens (
talk)
20:55, 17 April 2011 (UTC)reply
This case involves an intricate choreography of missteps by three individuals. I am reluctant to point accusing fingers in any one direction. Per Jclemens, I'd support reminded,
Roger Daviestalk03:59, 1 May 2011 (UTC)reply
Holding off on voting until I see the balance of the remedies to put this in context, as well as whether any additional findings are proposed per Jclemens' comment. My initial inclination at this time is to oppose per Jclemens and my comments on finding 36 above. (Weirdly, this section heading is showing up in the page history and I noticed it on my watchlist as "Dreadstar severely admonished", although the actual title doesn't include "severely". Can anyone kindly tell me why this is happening?)
Newyorkbrad (
talk) 21:29, 17 April 2011 (UTC) Moved to support.
Newyorkbrad (
talk)
17:27, 2 May 2011 (UTC)reply
Right. What else is there, Coren? I would not support this by itself. I would not even support taking the case if I believed this was the only problem.
Cool HandLuke04:20, 18 April 2011 (UTC)reply
I would support a "reminded" for Sandstein, just like I would for Dreadstar. More importantly, this advice does not take into account the deficiencies of fact with the block, which are separate from the deficiencies in communication.
Jclemens (
talk)
05:19, 24 April 2011 (UTC)reply
Procedurally. At this time, the decision would end up with this minor sanction towards Sandstein passing while the more important admonishment of Dreadstar fails — a result I see as entirely nonsensical and undesirable. —
Coren(talk)15:35, 2 May 2011 (UTC)reply
Wavering between supporting per Casliber and abstaining per Coren (assuming that Coren's comment is missing a "not").
Newyorkbrad (
talk) 02:30, 1 May 2011 (UTC) Sticking with abstain, given Sandstein's statement that he does not anticipate participating in AE again for awhile.
Newyorkbrad (
talk)
17:28, 2 May 2011 (UTC)reply
Does not, in my opinion, meet the level to require a finding/remedy.
SirFozzie (
talk) 02:34, 24 April 2011 (UTC)convinced by actions related to but not part of this case to switch to support.
SirFozzie (
talk)
07:50, 1 May 2011 (UTC)reply
Equal preference (which is kind of a moot point when I'm abstaining). The abstention rather than support is based on Sandstein's comment that he does not anticipate participating in any AE actions for the foreseeable future in any event. I do not, incidentally, agree that our decision not to desysop Dreadstar in this case is a sensible basis for concluding that Sandstein's work at AE is not appreciated; I do, though, think it makes sense, in light of his expressed feelings, to take a break from this activity.
Newyorkbrad (
talk)
04:44, 3 May 2011 (UTC)reply
First choice. Ludwigs2, you were blocked because of your rhetoric and hyperbole, which distracted from the issue you wished to have addressed.
Risker (
talk)
02:01, 4 May 2011 (UTC)reply
Support, but specifically not as remedies. The principles expound on caution and due diligence, but do not give procedure (nor, indeed, should they). I would support a restatement of Trusilver as an independent remedy, however. —
Coren(talk)15:17, 30 April 2011 (UTC)reply
Re principles vs. findings vs. remedies, see my comment on principle 9. Perhaps it would be helpful to reword by changing "reflect on" to "abide by", which effectively would incorporate all the AE-related principles into the remedies?
Newyorkbrad (
talk)
02:33, 1 May 2011 (UTC)reply
Yes, indeed, done. If anyone vehemenently objects, it can be reposted as an alternative. Incidentally, as discussed elsewhere, the principles probably now need rearranging into a more logical order.
Roger Daviestalk19:12, 2 May 2011 (UTC)reply
Disagree. That puts way too much weight on 4 & 8, which need the context of the other stuff (like the restatement of Trusilver) for context. I would support however a bullet point remedy, referring back to specified principles, along the lines of
that suggested in the /Workshop.
Roger Daviestalk03:58, 30 April 2011 (UTC)reply
i) Discretionary sanctions are a fast-track procedure to tackle misconduct within defined topic areas and/or to prevent disputes from within the defined topic area overflowing freely into other areas of the encyclopedia (cf.
P2.1,
P2.2.1);
ii) Discretionary sanctions may be imposed by any uninvolved administrator after giving due warning (cf.
P3.2,
P3.1.2);
iii) Best practice includes seeking additional input prior to applying a novel sanction or when a reasonable, uninvolved editor may question whether the sanction is within the scope of the relevant case (cf.
P3.1.2);
iv) Warnings should be clear and unambiguous, link to the decision authorising the sanctions, identify misconduct and advise how the editor may mend their ways (cf.
P3.2);
v) Notices of imposed sanctions should specify the misconduct for which they have been imposed as well as the appeal process (cf.
P3.2);
vi) Discretionary sanctions have an established and clearly defined appeal process, which must be adhered to (cf.
P4.1,
P4.2,
P2.3);
vii) Overturning arbitration enforcement actions out of process is strictly prohibited per longstanding principle (cf.
P4.1,
P4.2);
viii) Discretionary sanctions should be used with caution where the community is already dealing with the specific issue through dispute resolution processes (cf.
P3.1.2).
Support:
This was floated in the workshop and copy-edited to accommodate comments there. It probably needs cross-referencing to principles, once they're stabilised.
Roger Daviestalk04:49, 30 April 2011 (UTC)reply
This is okay, as set out, though I think (v) might well deserve a more detailed remedy on its own. I'll see if I can craft something up without unduly delaying the decision. —
Coren(talk)15:19, 30 April 2011 (UTC)reply
Support, but I would propose two copyedits: (1) change "instructed" to "reminded" or "advised" (I prefer to use "instructed" when we are speaking to someone who has done something wrong, not to hundreds or thousands of users); and (2) although we might refer to the "Trusilver principle" in internal shorthand, I don't think it's either dignified or fair to him to call it by that name in a formal decision. (Or maybe I'm just unduly sensitive because I dissented from the desysopping in that case.)
Newyorkbrad (
talk)
02:36, 1 May 2011 (UTC)reply
Clerks and Arbitrators should use this section to clarify their understanding of the final decision--at a minimum, a list of items that have passed. Additionally, a list of which remedies are conditional on others (for instance a ban that should only be implemented if a mentorship should fail), and so on. Arbitrators should not pass the motion until they are satisfied with the implementation notes.
Important: Please ask the case clerk to author
the implementation notes before initiating a motion to close, so that the final decision is clear.
Four net "support" votes needed to close case (each "oppose" vote subtracts a "support"). 24 hours from the first motion is normally the fastest a case will close. The
Clerks will close the case either immediately, or 24 hours after the fourth net support vote has been cast, depending on whether the arbitrators have voted unanimously on the entirety of the case's proposed decision or not.
There's a little more tweaking to be done but the substance is now established. I observe the comments on the talkpage that there are issues we have not addressed, but this case will not be our last opportunity to address these issues.
Newyorkbrad (
talk)
04:18, 3 May 2011 (UTC)reply
The tweakings are all done. I've put up symmetry "reminder" findings for the three named individuals above: if they fly, they fly; if they don't, they don't. My view is close this now in 48 hours, come what may.Roger Daviestalk06:00, 3 May 2011 (UTC)reply
Given the fundamental disagreement within the committee about the core substantive matter, this current decision is the best possible result. —
Coren(talk)23:30, 3 May 2011 (UTC)reply
# Procedural oppose, there's still things above that need one or two more votes to pass.
SirFozzie (
talk) 04:31, 3 May 2011 (UTC) striking now that most everything has enough votes to go one way or the other.
SirFozzie (
talk)
23:58, 3 May 2011 (UTC)reply
After considering
/Evidence and discussing proposals with other Arbitrators, parties and others at
/Workshop, Arbitrators may place proposals which are ready for voting here. Arbitrators should vote for or against each point or abstain. Only items that receive a majority "support" vote will be passed. Conditional votes for or against and abstentions should be explained by the Arbitrator before or after his/her time-stamped signature. For example, an Arbitrator can state that she/he would only favor a particular remedy based on whether or not another remedy/remedies were passed. Only Arbitrators or Clerks should edit this page; non-Arbitrators may comment on the talk page.
For this case there are 13 active arbitrators, not counting 1 recused. 7 support or oppose votes are a majority.
If observing editors notice any discrepancies between the arbitrators' tallies and the final decision or the
#Implementation notes, you should
post to the
Clerk talk page. Similarly, arbitrators may request clerk assistance via the same method.
Proposed motions
Arbitrators may place proposed motions affecting the case in this section for voting. Typical motions might be to close or dismiss a case without a full decision (a reason should normally be given), or to add an additional party (although this can also be done without a formal motion as long as the new party is on notice of the case). Suggestions by the parties or other non-arbitrators for motions or other requests should be placed on the
/Workshop page for consideration and discussion. Motions have the same majority for passage as the final decision.
Template
1)
{text of proposed motion}
Support:
Oppose:
Abstain:
Proposed temporary injunctions
A temporary injunction is a directive from the Arbitration Committee that parties to the case, or other editors notified of the injunction, do or refrain from doing something while the case is pending.
Four net "support" votes needed to pass (each "oppose" vote subtracts a "support")
24 hours from the first vote is normally the fastest an injunction will be imposed.
Template
1)
{text of proposed orders}
Support:
Oppose:
Abstain:
Proposed final decision Information
Proposed principles
Decorum
1) [Old 2] Wikipedia users are expected to behave reasonably, calmly, and courteously in their interactions with other users; to approach even difficult situations in a dignified fashion and with a constructive and collaborative outlook; and to avoid acting in a manner that brings the project into disrepute. Unseemly conduct, such as
personal attacks,
incivility,
assumptions of bad faith,
trolling,
harassment,
disruptive point-making, and
gaming the system, is prohibited.
Per Coren and PhilKnight. Perhaps the missing piece to tie the principle to this case would be an added sentence at the end along the lines of "Administrators have the responsibility for enforcing these requirements, and are expected to do in a reasonable, thoughtful, and proportionate fashion" or some such.
Newyorkbrad (
talk)
11:16, 15 April 2011 (UTC)reply
2.1) [Old 8] Administrators who address Arbitration Enforcement requests handle one of the project's most sensitive and stressful administrator tasks; among other things, they must frequently assess and resolve complex issues arising from bitter long-term editing disputes and involving intractable and strongly opinionated editors. The Arbitration Committee appreciates the work performed by these administrators, without whom long-term remedies imposed in our decisions would be meaningless. To share the workload, the Committee encourages more administrators, particularly experienced ones, to become involved in this task. More administrators are also urgently needed to handle other tasks at the front lines of addressing user-conduct issues, such as review of unblock requests on-wiki and on the unblock-l mailing list.
2.2) [Old 1]Wikipedia administrators are trusted members of the community and are expected to follow all of
Wikipedia's policies and guidelines to the best of their abilities. Occasional mistakes are entirely compatible with this–administrators are not expected to be perfect–but consistently poor judgment may result in reapplication for adminship via the
requests for adminship procedure or suspension or revocation of adminship. If revoked, the user may have a temporary or permanent limitation placed on reapplying.
I will support, but this could use some copyediting; for example, "may result in reapplication for adminship via RfA" is unnecessary, as any required new RfA would follow a revocation (or perhaps a long-term suspension, but we don't do that much) of adminship. The last sentence, while true, also sets an unnecessarily harsh tone for the introduction to this case and I would omit it here.
Newyorkbrad (
talk) 11:14, 15 April 2011 (UTC) Second choice.
Newyorkbrad (
talk)
20:54, 17 April 2011 (UTC)reply
2.2.1) [Old 1.2]Administrators are trusted members of the community and are expected to follow Wikipedia policies and to perform their duties to the best of their abilities. Administrators should exercise care and judgment when using their tools and when
imposing sanctions delegated by the arbitration committee. Occasional mistakes by administrators are understandable, but consistently or egregiously poor judgment may result in the removal of administrator status. Administrators are expected to learn from experience and from justified criticisms of their actions.
2.3) [Old 10] An administrator's actions taken for purposes of Arbitration enforcement may be overturned following a clear, substantial, and active consensus of uninvolved editors, on the Arbitration Enforcement noticeboard or another appropriate venue, or in rare instances, by the Arbitration Committee on appeal. When this occurs, the administrator whose action was overturned should assess why others disagreed with the action, and take this into account in future decision-making. However, the administrator should not take the overturning as a personal rebuke; over time, every active administrator working anywhere on the project will have some of his or her administrator actions disagreed with or overturned, just as every arbitrator sometimes finds himself or herself in the minority on an issue voted on by the Committee.
This principle should be extended to other administrator-review functions--it just came up the other day at
WP:DRV. The focus is on getting the outcome right, and doesn't shift onto the administrator taking a reversed action until a pattern of repeated or egregious differences between actions taken and community expectations.
Jclemens (
talk)
14:32, 15 April 2011 (UTC)reply
What this is about is an individual administrator learning from mistakes. Could this be reflected in the heading? "Reacting positively to reversals" or similar as that provides a bit more context for the principle?
Roger Daviestalk05:31, 30 April 2011 (UTC)reply
Deliberate and careful use of discretionary sanctions
3.1) [Old 4.0] Because of the increased risk of disruption around enforcement of
discretionary sanctions,
Wikipedia administrators are expected to be especially deliberate and careful in applying their discretion and to seek consensus
in a suitable venue over unilateral action when there is no pressing need for immediate action.
Support:
There is no reason, for instance, where an administrator that notices problematic behavior from an editor that has already been warned cannot open a new enforcement request of their own impetus to discuss the matter with their peers before making most enforcement decisions. —
Coren(talk)14:59, 14 April 2011 (UTC)reply
No. Everything so far from the Arbitration Committee in regard to discretionary sanctions has been based around 'any uninvolved admin', if we are changing this towards a consensus model that should be a remedy, not a principle.
PhilKnight (
talk)
16:10, 14 April 2011 (UTC)reply
This is ok, but I would like something stronger—that decisions must be supported by independent uninvolved admins users at AE unless there is a pressing need for action. I would also prefer to leave out the word "consensus" because the sanctioned party rarely agrees, and partisans on his or her "side" frequently also oppose sanction. If we want to use the c-word, let's at least say "consensus of uninvolved users."
Cool HandLuke15:36, 14 April 2011 (UTC)reply
I don't mind a rewording in that direction; my problem is with unilateral action without discussion when there is no pressing need to do so. Tweaked accordingly. —
Coren(talk)16:33, 14 April 2011 (UTC)reply
Deliberate and careful use of discretionary sanctions (alt 1)
3.1.1) [Old 4.1] Because of the increased risk of disruption around enforcement of
discretionary sanctions,
Wikipedia administrators are expected to be especially deliberate and careful in applying their discretion and to first prefer seeking support of uninvolved editors
in a suitable venue over unilateral action when there is no pressing need for immediate action.
Support:
I recognize this is a departure, but this case was taken so that we would slightly modify AE; it's been far too cowboy. I think this proposal strikes a good balance by keeping the process unyoked from the heavy burden of CONSENSUS, but by requiring some third-party support when the situation is not urgent.
Cool HandLuke02:40, 15 April 2011 (UTC)reply
With great power comes great responsibility--responsibility which, had it been appropriately exercised in the first place, would have avoided this fiasco entirely.
Jclemens (
talk)
03:15, 15 April 2011 (UTC)reply
Except it HAD been appropriately exercised, you noticed that the finding was that while the remedy wasn't the greatest from Sandstein, there was no consensus to remove it? Seems to me that in lawyer speak, I'd be saying "Objection, assumes facts not in evidence".
SirFozzie (
talk)
04:16, 15 April 2011 (UTC)reply
My evaluation of the appropriateness of such exercise is informed, but not bound, by the community's or the committee's findings. It's been obvious from our first discussions of the case that the committee is of multiple minds on this.
Jclemens (
talk)
05:49, 15 April 2011 (UTC)reply
Same as 3.1 4.0. We have a situation where there are enough "uninvolved" editors who "just happen to show up" with normal issues, and AE is hyper focused on things that can have significant amount of push back from the sanctioned editor's colleagues only makes it worse. I prefer the current situation, as MastCell says, AE in GENERAL is not a significant source of harm to the project.
SirFozzie (
talk)
21:50, 14 April 2011 (UTC)reply
Did you mean to say there are not enough uninvolved editors? Honestly, I'm not sure what incentive an uninvolved editor would have to participate with restraint when any other admin can shoot from the hip without any realistic chance of being reversed. If this is not the root of the problem (which I think it is, and Coren apparently does as well), what part of AE in PARTICULAR is harmful to the project?
Cool HandLuke03:51, 15 April 2011 (UTC)reply
No, I'm saying there's "uninvolved" editors, and by that, I mean "Really involved/partisan but will say they're not so they can prevent fellow partisans from being sanctioned." I'm saying AE in general is NOT harmful, period, as MastCell does on the talk page. Are there problematic actions taken? Obviously, but not enough I think to change AE, and this is speaking as someone who's worked there. The admins working there need our support, not having their hands tied further.
SirFozzie (
talk)
04:14, 15 April 2011 (UTC)reply
Deliberate and careful use of discretionary sanctions
3.1.2) [Old 4.2] Because of the priority given to enforcement of
discretionary sanctions, administrators must be deliberate and careful in applying their discretion to impose sanctions. In general, sanctions should be imposed in situations where there has been a serious violation or a pattern of violations of a remedy contained in an Arbitration Committee decision, and a prior warning or warnings have not resolved the problem. When it is not entirely clear whether a sanction is appropriate, or when an administrator knows that there is a division of opinion regarding whether a sanction is warranted, and there is no pressing need for immediate action, it may be best for an administrator to raise the issue
in the discussion venue for Arbitration Enforcement and seek a consensus, rather than to act unilaterally.
This is not written as a remedy. Is your position that modifications to policies should be listed as remedies because they're new? I don't think that's the correct distinction: our principles often fill in gaps between policies with common sense. In this case, the underlying policy is our own construction, and if we were to formally modify it we would not call such amendment a "remedy."
Cool HandLuke23:51, 15 April 2011 (UTC)reply
3.2) [Old 7] In imposing a sanction or giving a warning based on an Arbitration Committee decision, an administrator should clearly specify the basis of the action and the reasons it is being taken. The scope of any sanction imposed should also be specified as clearly as possible. A sanctioned editor may respond by asking the sanctioning administrator, in a civil fashion, to explain or to reconsider the imposition or scope of the sanction. The administrator should respond to appropriate questions raised by the sanctioned editor, and when appropriate should also advise the editor that he or she may request a review of the sanctions by a request to the Arbitration Enforcement noticeboard.
Support:
I'm adding three principles now, and perhaps one or two more later on. This one sets forth some expectations and recommendations, for clarity and emphasis. This is not meant to suggest that these procedures were not followed in this case.
Newyorkbrad (
talk)
11:52, 15 April 2011 (UTC)reply
Yes. Particularly in this case, there's a school of thought that says that had the warning in this case been clearer and explicitly advised what was expected (ie redaction), the subsequent block would not have been placed and therefore there would have been nothing to overturn.
Roger Daviestalk05:22, 30 April 2011 (UTC)reply
Like Roger says, clear warnings can stop a problem in its tracks; there are some reasonable differences of opinion here about whether a different warning might have had a different outcome.
Shellbabelfish11:50, 4 May 2011 (UTC)reply
Oppose:
Abstain:
Arbitration case sanctions
3.3) [Old 3] The scope of sanctions imposed as remedies in arbitration cases should be clearly defined so as to avoid later misunderstandings and disagreements. A sanction remedy should also clearly specify the duration of the sanction and the procedure, if any, available to the sanctioned user to seek lifting or modification of the sanction in due course.
Opposing until this is clarified ... Is this principle saying that the scope of discretionary sanctions for any particular topic should be defined in the case remedy on a case by case basis? Don't we already do that in the area of conflict stuff? Or it is saying that the type of available sanction needs to specified in the case remedy? I agree that santioned editors need to be informed about appeal options but I'm slightly unclear about "the procedure, if any". Aren't there numerous appeal options already available?
Roger Daviestalk05:13, 30 April 2011 (UTC)reply
This principle was taken from the
Henri Coanda case, where you supported it. However, if you feel that it can be improved, then I suggest you go ahead and create an alternative.
PhilKnight (
talk)
13:33, 30 April 2011 (UTC)reply
Sure but context is everything ... and in Henry Coanda it was about specific case remedies rather than discretionary sanctions. As, in the context of this case, it can easily be misunderstood/misconstrued, I'm not sure that it, or an alternative, really helps much :)
Roger Daviestalk13:44, 30 April 2011 (UTC)reply
3.4) [Old 6] Arbitration remedies are a powerful but blunt instrument to protect areas of the project that have already proven difficult. They should not be invoked where normal policy and practice would suffice to resolve a problem, or where a lesser remedy would be adequate.
Support:
A pithy way of restating this might be "Thou shall not take
AE's name in vain". Because enforcement actions are more powerful, they should be used as little as possible. —
Coren(talk)14:59, 14 April 2011 (UTC)reply
First, this strikes me was very gameable: this argument is always available ("your AE request was invalid because you provided no evidence ANI wouldn't work!"). Second, discretionary sanctions only exist because the "community" failed to resolve a dispute. Within those topics, I think AE is the presumptively correct venue. AE admins should understand that a range of lesser remedies will be appropriate in many cases. AE has
every tool at its disposal, from blocks up to one year (or much shorter), topic bans, page bans, and "any other measures which the imposing administrator believes are reasonably necessary." If AE is failing to properly give out the lesser remedies when appropriate, we should reform AE rather than insist that small stuff be handled by "normal policy and practice." (If AE is abnormal, it ought not to be.)
Cool HandLuke15:47, 14 April 2011 (UTC)reply
Before becoming an arbitrator, I was an admin who handled requests at
WP:AE, and my approach was that, in general, sanctions that resulted from reports to the
WP:AE noticeboard should be logged as enforcement sanctions. While we could stipulate this approach is wrong, that should be a remedy, instead of a principle.
PhilKnight (
talk)
16:13, 14 April 2011 (UTC)reply
I stated in the workshop something similar, that AE is not a hammer, and not every editor under those sanctions is a nail.. but we put discretionary sanctions in to give administrators more options, this and other findings would restrict them more then I feel comfortable with.
SirFozzie (
talk)
16:34, 14 April 2011 (UTC)reply
I would prefer a revised version that takes the opposers' comments into account. (Some of this may now be covered by my new 3.1.2 4.2, if adopted.)
Newyorkbrad (
talk)
11:30, 15 April 2011 (UTC)reply
4.1) [Old 5] Arbitration enforcement should not be reversed unilaterally: it is not appropriate for an administrator to simply substitute their judgment for another's. Even if the disagreeing administrator believes that the enforcement action was erroneous or mistaken and discussion with the enforcing administrator has not led to a solution, substantial community consensus or Committee permission must be sought before overturning an act explicitly stated to be pursuant to an arbitration remedy.
Support:
Specifically, an administrator preparing to overturn such a decision needs to realize that they are exactly as likely, in the end, to be in error about the validity of the enforcement action than the original admin might have been. —
Coren(talk)14:59, 14 April 2011 (UTC)reply
I also agree with JClemens, but would add that as a new principle. Once an explained AE decision is made, it should not be overturned easily.
Cool HandLuke21:05, 16 April 2011 (UTC)reply
Although I can imagine an exception for blatant or obvious errors, which we might want to write in. With regard to Jclemens' point below, I might support a principle in line with his comment, but think it raises a separate (albeit related) issue to this one.
Newyorkbrad (
talk)
11:29, 15 April 2011 (UTC)reply
I think it would add an appropriate level of responsibility (see above) to require detailed and specific justification for AE sanctions. Part of the problem in this case was that the blocking admin referred to a block as an AE block without appropriate explanation, such that other editors not participating in the discussion were not able to see how the block was, in fact, an AE block. Blocks are not AE blocks because the blocking administrator calls them AE blocks, they are AE blocks because they are applied pursuant to the specific constraints of a previously enacted remedy. The presumption that a mere "this is an AE block!" statement makes a block a valid AE block until proven otherwise by widespread consensus is inappropriate.
Jclemens (
talk)
03:23, 15 April 2011 (UTC)reply
Comes at "Trusilver" from a slightly different angle. For clarity, I'd rather have just one principle on this, using the Trusilver text verbatim, which is elsewhere here.
Roger Daviestalk05:18, 30 April 2011 (UTC)reply
My point is, the Trusilver text applies of this principle by setting out a specific procedure. It's the "remedy" to this principle. —
Coren(talk)15:04, 30 April 2011 (UTC)reply
4.2) [Old 9] In March 2010, the Committee by
motion specified the procedure for overturning discretionary sanctions. The applicable section reads:
Administrators are prohibited from reversing or overturning (explicitly or in substance) any action taken by another administrator pursuant to the terms of an active arbitration remedy, and explicitly noted as being taken to enforce said remedy, except:
(a) with the written authorization of the Committee, or
(b) following a clear, substantial, and active consensus of uninvolved editors at a community discussion noticeboard (such as
WP:AN or
WP:ANI). If consensus in such discussions is hard to judge or unclear, the parties should submit a request for clarification on the
proper page.
Any administrator that overturns an enforcement action outside of these circumstances shall be subject to appropriate sanctions, up to and including desysopping, at the discretion of the Committee.Administrators who consistently make questionable enforcement administrative actions, or whose actions are consistently overturned by community or Arbitration Committee discussions may be asked to cease performing such activities or be formally restricted from taking such activities.
The description of good practice is a principle; that it was adopted in a prior decision is a fact; if we instruct people to abide by it going forward it's a remedy. Given the need to finish this case and to focus on the substance of our decision at this stage rather than matters of form, I don't think we should debate at length which section or sections of the decision this paragraph belongs in.
Newyorkbrad (
talk)
02:24, 1 May 2011 (UTC)reply
Although I think we took the case to review wider issues relating to the Arbitration enforcement process, not primarily this single block and unblock.
Newyorkbrad (
talk)
11:58, 15 April 2011 (UTC)reply
Concur, as far as it goes. The root cause was an editing dispute on
Talk:Pseudoscience which led Ludwigs2 to initiate a thread at
the administrator noticeboard. It should be noted that the initial dispute was not addressed by the community, whose attention was diverted by the block of Ludwigs2. However, the reason for accepting the case surrounds the actions described in this finding.
Risker (
talk)
19:47, 1 May 2011 (UTC)reply
2) In accepting this case, several arbitrators
expressly did so as an opportunity to examine the general background to
arbitration enforcement and to consider the underlying principles involved.
I had concerns, both specific and general with regards to AE. So far, after reviewing the notes, my concerns have GENERALLY been ameliorated, not to say I think everything out of AE is perfect, mind you.
SirFozzie (
talk)
10:26, 18 April 2011 (UTC)reply
As a pure matter of drafting style, I prefer to work this into the locus finding rather than treat it in a separate paragraph. However, I strongly suspect that no one else cares.
Newyorkbrad (
talk)
21:54, 18 April 2011 (UTC)reply
3) This dispute was triggered by a
posting made by Ludwigs2 on 8 March 2011 at the Administrators' Noticeboard. The last paragraph of Ludwigs2's posting contained inappropriate remarks, which included: "if you don't do something to get him to fly right you'll leave me with no choice except to shout him down and shut him up" and " if I have to go that route things will get progressively more ugly".
This wouldn't have warranted an arbitration case in and of itself, but it's relevant as background, and I can't say that Lugwigs2 was so innocent in the situation that it's inherently unfair to mention him.
Newyorkbrad (
talk)
02:27, 1 May 2011 (UTC)reply
I will note that Ludwigs2's use of intemperate language had the effect of distracting reviewing administrators and community members from the issue that he sought to draw attention to, and as such was pretty much an own goal; I have noticed similar but less colourful posts during this case as well. Ludwigs2 should seriously consider moderating the tone of future posts so that hyperbolic language does not overshadow the subject of his commentary or, in some situations, consider whether or not his comments are more likely to assist other readers or distract them from the subject.
Risker (
talk)
20:02, 1 May 2011 (UTC)reply
4) Ludwigs2 had been previously notified about the Pseudoscience discretionary sanctions, in respect of
another case in
September 2008.
Among other things, the notification stated "These editing restrictions may be applied to any editor for cause, provided the editor has been previously informed of the case. This message is to so inform you. This message does not necessarily mean that your current editing has been deemed a problem; this is a template message crafted to make it easier to notify any user who has edited the topic of the existence of these sanctions."
The notification also states: "Prior to any sanctions being imposed, the editor in question shall be given a warning with a link to this decision; and, where appropriate, should be counseled on specific steps that he or she can take to improve his or her editing in accordance with relevant policies and guidelines."
Background; but note the recent discussion, in an unrelated request for clarification, in which we discussed whether these general "notice to all editors on the articles" notices constitute the type of "warnings" that should precede the imposition of discretionary sanctions.
Newyorkbrad (
talk)
22:03, 24 April 2011 (UTC)reply
5) On 8 March 2011, Ludwigs2 was warned by Sandstein both in the
AN thread and on
Ludwigs2's talk page that a block was contemplated. The AN message stated that Ludwigs2 "had previously been warned" and linked to the
September 2008 message.
6) Sandstein's warning message to Ludwigs2 requested the latter to "show cause why [he] should not be sanctioned" within two hours of his next edit. Ludwigs2 requested that Sandstein clarify his warning at both his own talk page
[2] and the noticeboard thread
[3]. Sandstein did not respond further to Ludwigs2, but proceeded to block him less than two hours after his initial warning.
[4]
I can support this although a copyedit per SirFozzie would be welcome. I note that "show cause" as Sandstein used the term in his notification is a "legalism" (see
order to show cause). Although not as opaque to laypersons as some legalisms, the terminology might not have been fully understood.
Newyorkbrad (
talk) 22:08, 24 April 2011 (UTC) (adding for clarity) ... although, per PhilKnight below, the import of the message as a whole should have been.
Newyorkbrad (
talk)
20:32, 26 April 2011 (UTC)reply
Accurate finding of fact. I concur with PhilKnight that Sandstein's post on
WP:AN was more explanatory than the one on Ludwigs2's talk page; however, both posts invited discussion rather than action, and it was a reasonable interpretation that Sandstein was initiating a (two-way) discussion rather than planning to block if he did not find Ludwigs2's first comment to meet his expectations to "show cause".
Risker (
talk)
20:14, 1 May 2011 (UTC)reply
The show cause was to remove it or explain why he should not be sanctioned. This is an abstain rather than oppose because I understand that I was familiar with the term used, but others may not be.
SirFozzie (
talk)
02:33, 24 April 2011 (UTC)reply
"Show cause" barely has that meaning even among lawyers; a reasonable (perhaps even more reasonable) interpretation is "explain why you should not be sanctioned for the remarks you have already made."
Cool HandLuke14:00, 3 May 2011 (UTC)reply
Sandstein said "But I am concerned about the following statement by Ludwigs2 above: "I'm dropping this in your lap now, because if you don't do something to get him to fly right you'll leave me with no choice except to shout him down and shut him up. I'm very capable of doing that (as some of you should be aware), but if I have to go that route things will get progressively more ugly." That sounds like a threat to me. Threats are not an acceptable mode of dispute resolution. Ludwigs2 has previously been warned that they may be subject to discretionary sanctions if they violate community norms in the pseudoscience topic area. I therefore invite Ludwigs2 to show cause why they should not be sanctioned for making threats against others." In this context, for Ludwigs2 to say 'what are you talking about' is inadequate. Ok, he may not have understood the phrase 'show cause', but he must have understood the rest of the comment. Consequently, he should have retracted his threats.
PhilKnight (
talk)
19:03, 25 April 2011 (UTC)reply
8) A little over three hours later,
Dreadstar(
talk·contribs·blocks·protections·deletions·page moves·rights·RfA) unblocked the editor while clearly aware that the block was done pursuant to an arbitration remedy
[8][9]. While the applicability and propriety of the block was disputed and under discussion
[10], there was no consensus to overturn the enforcement action at that time (nor, indeed, did Dreadstar claim there was or that he was acting accordingly).
Support:
Dreadstar clearly believed that the block was erroneous (or at least erroneously claimed to be arbitration enforcement); but "I'm right and you're wrong" is not sufficient rationale to
ignore process — if only because everyone acts under a presumption that they are correct, including the blocking admin. —
Coren(talk)16:29, 14 April 2011 (UTC)reply
I will support, but I'm not sure we've captured all aspects of Dreadstar's thinking here. Although Dreadstar did not claim there was a "consensus to overturn the administrator action," he did reference several editors' support for an unblock at the time he unblocked. Most important, I find Dreadstar's evidence that he did not understand at the time the procedures required to overturn an AE block, and his assurance that he will not do so without consensus in the future (or at all with regard to this particular editors), to be credible.
Newyorkbrad (
talk)
11:58, 15 April 2011 (UTC)reply
You're opposing a finding of fact. Since the first sentence appears pretty straightforward, would you care to propose alternative wording that ameliorates your problems with the second?
Jclemens (
talk)
05:14, 24 April 2011 (UTC)reply
The unblock without discussion or consensus of an AE block (and despite claims otherwise, there has been no evidence that would lead me to believe it wasn't one) taints this action.
SirFozzie (
talk)
15:27, 25 April 2011 (UTC)reply
I'm not going to support this finding, or its alternatives, because — while strictly accurate — they create an impression that is contrary to plainly observable facts: Dreadstar did not try to apply arbitration enforcement differently, he believed arbitration enforcement did not apply at all in the first place. If he had clearly believed this was an arbitration enforcement matter at the time of the unblock, this would be an aggravating finding and certainly not a mitigating one. —
Coren(talk)15:01, 30 April 2011 (UTC)reply
This is about Dreadstar and Ludwigs2, Sandstein's finding that the statements were threats of disruption was already addressed.
Risker (
talk)
03:19, 2 May 2011 (UTC)reply
I'm explaining why, at the time I am voting, I oppose this finding. I've no objection to the idea that this finding of fact was proposed.
Risker (
talk)
04:18, 2 May 2011 (UTC)reply
This covers additional ground that 9 does not address, so it's hard to pick a "first choice" among them. Might a third version be appropriate? Alternatively, a separate FoF on Ludwigs2's statements might work. Regardless, I don't oppose this, I'm just not sure it's scoped right.
Jclemens (
talk)
01:12, 27 April 2011 (UTC)reply
9.2) Sandstein interpreted remarks in the last paragraph of
Ludwigs2's initial AN post as threats to disrupt. After unblocking Ludwigs2, Dreadstar
instructed Ludwigs2 to strike the contentious remarks. Ludwigs2 duly
redacted them.
Support. I don't get the problem with sticking to the facts here, contra SirFozzie below. We're taking each of the two administrators at their word here, largely because their conduct was internally consistent and each has acknowledged deficiencies. I don't see this wording rewarding anyone.
Jclemens (
talk)
21:30, 29 April 2011 (UTC)reply
Ugh. Half support, half oppose (again, it doesn't excuse what he did before hand, and it seems like we're praising him for it, which rubs me the wrong way). Going to think about it, but Abstain for now.
SirFozzie (
talk)
20:49, 29 April 2011 (UTC)reply
10) While it was generally agreed during the ensuing discussion that an arbitration enforcement block was probably not the best solution in this case, there was no clear consensus that the block should have been overturned
[12].
I view the ideas of "was an appropriate AE block" and "should have been overturned as it transpired" as separate issues. I think it's clear that the manner in which the unblock was done was itself suboptimal and drama-producing, even if the block was not a valid AE block.
Jclemens (
talk)
14:35, 15 April 2011 (UTC)reply
This FoF isnt wrong per se, however it will result in the wrong decision if this passes in absence of a determination on whether the block was a valid AE block. "suboptimal" and "drama-producing" are par for the Wikipedia course, especially for contentious blocks & unblocks are discussed at the administrative noticeboards. John Vandenberg(
chat)20:48, 20 April 2011 (UTC)reply
I'm not sure I see what you mean, John. It was clearly stated to be an AE block, and it invoked a specific discretionary sanction. Whether or not it was a good AE block is not material to whether it was one — though I think that the lack of consensus to overturn it shows that it was, at least, a defensible interpretation of the remedy. —
Coren(talk)16:05, 17 April 2011 (UTC)reply
My oppose is not regarding whether or not it was a good or bad AE block; there are many AE blocks which are undeniably AE blocks and whether they are "good" or "bad" is often very subjective and depending on the POV&alliances of the person making that assessment. OTOH, this block made it to ArbCom because saying it is an AE block doesnt make it one. This is 2011, and both the community and arbcom have expectations about what can be appropriately called an AE block. They haven't been codified until now, and that is an important component of this case. John Vandenberg(
chat)20:41, 20 April 2011 (UTC)reply
11) In
Dreadstar's evidence, Dreadstar acknowledges that he made an error of judgment, has apologised for unblocking Ludwigs2, and has promised that he will not act similarly in respect of discretionary sanction in the future.
The reason a desysop is unnecessary has nothing to do with Dreadstar's apology. While an appropriate gesture, the problems with the block itself place the desysoping of Dreadstar out of consideration.
Jclemens (
talk)
05:16, 24 April 2011 (UTC)reply
I agree with this for exactly the opposite reasons Jclemens does: whether the block had problems or not, it's the assurance that such an unilateral unblock with not happen again that makes it unnecessary to desysop. —
Coren(talk)15:09, 30 April 2011 (UTC)reply
12) In
Sandstein's evidence, Sandstein has expressed regret for shortcomings in communications with Ludwigs2 and has promised to take more care to avoid miscommunication in the future.
Poor communication in the initial warning was certainly a significant factor in the escalation of the situation.
Risker (
talk)
03:29, 2 May 2011 (UTC)reply
As previously stated, does not, in my opinion, rise to the level of needing a finding.
SirFozzie (
talk) 02:33, 24 April 2011 (UTC) convinced by actions related to but not part of this case to switch to support.
SirFozzie (
talk)
07:50, 1 May 2011 (UTC)reply
Not sure that an arbitration finding is needed here; perhaps this could be briefly folded into the Sandstein-related paragraph above.
Newyorkbrad (
talk)
23:37, 24 April 2011 (UTC)reply
Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.
I don't think there is any doubt that this unilateral unblock was the wrong thing to do, but given Dreadstar's apparent motivation and their clear statement that they will not repeat the mistake, there is no reason to sanction them further. —
Coren(talk)12:47, 17 April 2011 (UTC)reply
(first Choice). Per Coren. I put strongly admonished in my workshop but that's because if there was a similar incident down the road, we all know what the likely result will be.
SirFozzie (
talk)
02:40, 18 April 2011 (UTC)reply
I'm not certain this is essential, as it appears more than clear that Dreadstar has gotten the message by now, but I will support it to bring the issue to a result.
Newyorkbrad (
talk)
17:27, 2 May 2011 (UTC)reply
I would support "reminded", but I think "admonished" is too strong a remedy unless there's a finding that Dreadstar's action was premeditated and/or partisan. While this has been alleged in evidence, no proposed finding has yet been put forth on this.
Jclemens (
talk)
20:55, 17 April 2011 (UTC)reply
This case involves an intricate choreography of missteps by three individuals. I am reluctant to point accusing fingers in any one direction. Per Jclemens, I'd support reminded,
Roger Daviestalk03:59, 1 May 2011 (UTC)reply
Holding off on voting until I see the balance of the remedies to put this in context, as well as whether any additional findings are proposed per Jclemens' comment. My initial inclination at this time is to oppose per Jclemens and my comments on finding 36 above. (Weirdly, this section heading is showing up in the page history and I noticed it on my watchlist as "Dreadstar severely admonished", although the actual title doesn't include "severely". Can anyone kindly tell me why this is happening?)
Newyorkbrad (
talk) 21:29, 17 April 2011 (UTC) Moved to support.
Newyorkbrad (
talk)
17:27, 2 May 2011 (UTC)reply
Right. What else is there, Coren? I would not support this by itself. I would not even support taking the case if I believed this was the only problem.
Cool HandLuke04:20, 18 April 2011 (UTC)reply
I would support a "reminded" for Sandstein, just like I would for Dreadstar. More importantly, this advice does not take into account the deficiencies of fact with the block, which are separate from the deficiencies in communication.
Jclemens (
talk)
05:19, 24 April 2011 (UTC)reply
Procedurally. At this time, the decision would end up with this minor sanction towards Sandstein passing while the more important admonishment of Dreadstar fails — a result I see as entirely nonsensical and undesirable. —
Coren(talk)15:35, 2 May 2011 (UTC)reply
Wavering between supporting per Casliber and abstaining per Coren (assuming that Coren's comment is missing a "not").
Newyorkbrad (
talk) 02:30, 1 May 2011 (UTC) Sticking with abstain, given Sandstein's statement that he does not anticipate participating in AE again for awhile.
Newyorkbrad (
talk)
17:28, 2 May 2011 (UTC)reply
Does not, in my opinion, meet the level to require a finding/remedy.
SirFozzie (
talk) 02:34, 24 April 2011 (UTC)convinced by actions related to but not part of this case to switch to support.
SirFozzie (
talk)
07:50, 1 May 2011 (UTC)reply
Equal preference (which is kind of a moot point when I'm abstaining). The abstention rather than support is based on Sandstein's comment that he does not anticipate participating in any AE actions for the foreseeable future in any event. I do not, incidentally, agree that our decision not to desysop Dreadstar in this case is a sensible basis for concluding that Sandstein's work at AE is not appreciated; I do, though, think it makes sense, in light of his expressed feelings, to take a break from this activity.
Newyorkbrad (
talk)
04:44, 3 May 2011 (UTC)reply
First choice. Ludwigs2, you were blocked because of your rhetoric and hyperbole, which distracted from the issue you wished to have addressed.
Risker (
talk)
02:01, 4 May 2011 (UTC)reply
Support, but specifically not as remedies. The principles expound on caution and due diligence, but do not give procedure (nor, indeed, should they). I would support a restatement of Trusilver as an independent remedy, however. —
Coren(talk)15:17, 30 April 2011 (UTC)reply
Re principles vs. findings vs. remedies, see my comment on principle 9. Perhaps it would be helpful to reword by changing "reflect on" to "abide by", which effectively would incorporate all the AE-related principles into the remedies?
Newyorkbrad (
talk)
02:33, 1 May 2011 (UTC)reply
Yes, indeed, done. If anyone vehemenently objects, it can be reposted as an alternative. Incidentally, as discussed elsewhere, the principles probably now need rearranging into a more logical order.
Roger Daviestalk19:12, 2 May 2011 (UTC)reply
Disagree. That puts way too much weight on 4 & 8, which need the context of the other stuff (like the restatement of Trusilver) for context. I would support however a bullet point remedy, referring back to specified principles, along the lines of
that suggested in the /Workshop.
Roger Daviestalk03:58, 30 April 2011 (UTC)reply
i) Discretionary sanctions are a fast-track procedure to tackle misconduct within defined topic areas and/or to prevent disputes from within the defined topic area overflowing freely into other areas of the encyclopedia (cf.
P2.1,
P2.2.1);
ii) Discretionary sanctions may be imposed by any uninvolved administrator after giving due warning (cf.
P3.2,
P3.1.2);
iii) Best practice includes seeking additional input prior to applying a novel sanction or when a reasonable, uninvolved editor may question whether the sanction is within the scope of the relevant case (cf.
P3.1.2);
iv) Warnings should be clear and unambiguous, link to the decision authorising the sanctions, identify misconduct and advise how the editor may mend their ways (cf.
P3.2);
v) Notices of imposed sanctions should specify the misconduct for which they have been imposed as well as the appeal process (cf.
P3.2);
vi) Discretionary sanctions have an established and clearly defined appeal process, which must be adhered to (cf.
P4.1,
P4.2,
P2.3);
vii) Overturning arbitration enforcement actions out of process is strictly prohibited per longstanding principle (cf.
P4.1,
P4.2);
viii) Discretionary sanctions should be used with caution where the community is already dealing with the specific issue through dispute resolution processes (cf.
P3.1.2).
Support:
This was floated in the workshop and copy-edited to accommodate comments there. It probably needs cross-referencing to principles, once they're stabilised.
Roger Daviestalk04:49, 30 April 2011 (UTC)reply
This is okay, as set out, though I think (v) might well deserve a more detailed remedy on its own. I'll see if I can craft something up without unduly delaying the decision. —
Coren(talk)15:19, 30 April 2011 (UTC)reply
Support, but I would propose two copyedits: (1) change "instructed" to "reminded" or "advised" (I prefer to use "instructed" when we are speaking to someone who has done something wrong, not to hundreds or thousands of users); and (2) although we might refer to the "Trusilver principle" in internal shorthand, I don't think it's either dignified or fair to him to call it by that name in a formal decision. (Or maybe I'm just unduly sensitive because I dissented from the desysopping in that case.)
Newyorkbrad (
talk)
02:36, 1 May 2011 (UTC)reply
Clerks and Arbitrators should use this section to clarify their understanding of the final decision--at a minimum, a list of items that have passed. Additionally, a list of which remedies are conditional on others (for instance a ban that should only be implemented if a mentorship should fail), and so on. Arbitrators should not pass the motion until they are satisfied with the implementation notes.
Important: Please ask the case clerk to author
the implementation notes before initiating a motion to close, so that the final decision is clear.
Four net "support" votes needed to close case (each "oppose" vote subtracts a "support"). 24 hours from the first motion is normally the fastest a case will close. The
Clerks will close the case either immediately, or 24 hours after the fourth net support vote has been cast, depending on whether the arbitrators have voted unanimously on the entirety of the case's proposed decision or not.
There's a little more tweaking to be done but the substance is now established. I observe the comments on the talkpage that there are issues we have not addressed, but this case will not be our last opportunity to address these issues.
Newyorkbrad (
talk)
04:18, 3 May 2011 (UTC)reply
The tweakings are all done. I've put up symmetry "reminder" findings for the three named individuals above: if they fly, they fly; if they don't, they don't. My view is close this now in 48 hours, come what may.Roger Daviestalk06:00, 3 May 2011 (UTC)reply
Given the fundamental disagreement within the committee about the core substantive matter, this current decision is the best possible result. —
Coren(talk)23:30, 3 May 2011 (UTC)reply
# Procedural oppose, there's still things above that need one or two more votes to pass.
SirFozzie (
talk) 04:31, 3 May 2011 (UTC) striking now that most everything has enough votes to go one way or the other.
SirFozzie (
talk)
23:58, 3 May 2011 (UTC)reply