The Signpost

Arbitration report

Board member likely to receive editing restriction

Contribute   —  
Share this
By Bri


Cases by lifecycle phase (since last report)
Requested Accepted Remained open Closed Amendments
none none Medicine Jytdog AP2
Declined
Carmaker1

Declined cases

Carmaker1 case was requested 17 April 2020; declined on 2 May.

Ongoing cases

Medicine

Medicine case

Last month, The Signpost stated "many of the workshop proposals appear to favor letting the editors solve the content dispute on their own." An unprecedented "topic moratorium" was proposed by active Arbcom member David Fuchs.

One quarter of the twelve active arbitrators recused themselves: Casliber, DGG, and Newyorkbrad. Recusal is usually done when an arbitrator considers him- or herself unable to make an impartial decision, often due to closeness to the subject in either a positive or negative way, but there is no requirement to give a reason for recusal. The Signpost notes without comment that one of the involved parties, Doc James, was appointed as a community-selected Wikimedia Foundation trustee in August 2017.[1]

Remedies proposed as of publication deadline include (reminders/admonishments have been omitted; a checkY means the remedy has passed as of publication deadline):

Closed cases

Jytdog

Jytdog case

Jytdog is indefinitely banned from the English Wikipedia. 11 yea, 0 nay (DGG recused). Issues identified in the findings include Jytdog's history of oversight blocks, Jytdog's other sanctions (two voluntary interaction restrictions/bans with another, and an indefinite topic ban), a history of edit warring and incivility, and uninvited off-wiki contact with another editor.

Amendment requests

Due to the inclusion of the Op-Ed "Where Is Political Bias Taking Us?" by Atsme, we are taking the unusual step of reviewing an amendment request from several months ago. American politics 2 (AP2) discretionary sanctions were taken up by Arbitration Committee in a December 2019 amendment request. It was the twelfth request for amendment or clarification and perhaps is of special importance during this U.S. election year. In the December request, Atsme objected to unilateral actions based on [a specific administrator's] customized DS which has lead to POV creep and specific DS for specific editors as he sees fit. He is micromanaging AP2 and controlling the narrative.

Atsme said this month (May) to the administrator who had applied the discretionary sanctions to her under the aegis of AP2 (which were lifted in March), your response is why I have made it my mission to draw attention to the problems you and a few other admins have created with DS and AE, specifically unilateral actions, and the POV creep associated with sole discretion. Your response solidifies my position, and I will use it in my arguments until the community is aware of why this is an extremely important issue to the future of the project as it relates to maintaining NPOV, and the ability for editors to engage in discussions where the exchange of free thought and ideas is paramount. Other respondents at the December amendment request made observations about the expansion of DS to become "boutique" or "tailored" sanctions at the unreviewed discretion of a single administrator. Comments by two arbitrators either noted their own concerns or the concerns of others: DGG said Delegating [DS] to whatever one of the several hundred individual admins may choose to exercise their imagination is another matter entirely ... no one admin should repeatedly engage in arb enforcement on the same individual or take a disproportionate share for any large area, and GorillaWarfare said [T]his does not seem to be a great place to also address whether admins should be creating their own sets of custom sanctions for use in areas where discretionary sanctions have been authorized. However it does seem like it would be worth visiting that issue somewhere, since there seem to be many people who share concerns about them.

Extended detail

Terminlogy used in American politics 2 December 2019 amendment request

"boutique", "specialized", "customized", or "custom" discretionary sanctions

Quotes used in the amendment request:

Arbs

  • Delegating [DS] to whatever one of the several hundred individual admins may choose to exercise their imagination is another matter entirely ... no one admin should repeatedly engage in arb enforcement on the same individual or take a disproportionate share for any large area - DGG
  • [T]his does not seem to be a great place to also address whether admins should be creating their own sets of custom sanctions for use in areas where discretionary sanctions have been authorized. However it does seem like it would be worth visiting that issue somewhere, since there seem to be many people who share concerns about them. - GorillaWarfare

Others

  • If the committee wants to consider [respondent]'s specialized DS, that should probably be a separate clarification request- Floqenbeam
  • [Complainant] may wish to consider posting another, separate, ARCA request about the special sanctions - Bishonen
  • ArbCom should look into how DS are being used - SashiRolls

Correction: The original headline made it appear that the Medicine case decision was closed. Currently the votes for an editing restriction on Doc James stand at 7-0, with 5 votes needed to pass, and the votes for closing the case at 2-0, with a net +4 needed to close. We regret the error.

Notes

  1. ^ "Press Release Wikimedia Foundation, August 2017". Archived from the original on November 7, 2017. Retrieved October 30, 2017.
S
In this issue
+ Add a comment

Discuss this story

These comments are automatically transcluded from this article's talk page. To follow comments, add the page to your watchlist. If your comment has not appeared here, you can try purging the cache.
Yes the case is still open but this sanction has been voted on 7-0, and For this case there are 9 active arbitrators, not counting 2 who are inactive and 3 who have abstained or recused, so 5 support or oppose votes are a majority. Therefore, unless someone three or more arbs reverse their vote, that's that. @Smallbones: do you want to change anything here? ☆ Bri (talk) 19:44, 31 May 2020 (UTC)[reply]
I've been thinking about this. Technically @Natureium: is correct, but how do we correct it now? Put a new headline of "Board member to receive editing restriction" up for 2 or 3 days? If an arb or @Doc James: wants a retraction or apology, please contact me by email. Smallbones(smalltalk) 20:06, 31 May 2020 (UTC)[reply]
You could do the honourable thing and correct the title to something that reflects the current situation, then correct it when it changes. You don’t have a crystal ball, and your comments in this magazine should reflect reality, not what you predict it to be. - SchroCat (talk) 22:07, 31 May 2020 (UTC)[reply]
I agree that the title should read "to receive", but the potential for real-life harm caused by this inaccuracy seems limited, in particular since the main text appears to state the situation correctly.
As for the idea to update it again in a few days: I'm a big fan of {{when}} in the mainspace, but Signpost articles carry a publication date; they do not need to be constantly updated to reflect future developments. Regard, HaeB (talk) 23:56, 31 May 2020 (UTC)[reply]
Perhaps the only change needed would be to change "receives" to "receiving" or "likely to receive" in the header. (Note: I'm recused in the case and have not looked at the merits of the decision; just offering a semantic suggestion.) Newyorkbrad (talk) 03:21, 1 June 2020 (UTC)[reply]
ditto, as NYB suggests. just think of it as fixing a grammar error. DGG ( talk ) 05:40, 1 June 2020 (UTC)[reply]

Signpost words all of the arbcom decisions wrongly.

I think it important that Signpost correct these mistakes so that its readers understand the correct extent of any sanctions or bans, and can adjust their editing or report violations appropriately. -- Colin°Talk 07:43, 1 June 2020 (UTC)[reply]

I have corrected the headline to read "Board member likely to receive editing restriction"

and posted the correction The original headline made it appear that the Medicine case decision was closed. Currently the votes for an editing restriction on Doc James stand at 7-0, with 5 votes needed to pass, and the votes for closing the case at 2-0, with a net +4 needed to close. We regret the error.

Thanks to everybody who commented here for their input. Smallbones(smalltalk) 11:59, 1 June 2020 (UTC)[reply]

Arbcom debates are not intended as public entertainment, and are certainly not accessible as such. It can be hard for an ordinary editor to figure out what the debate is about, let alone what the arguments on each side are. So it is the duty of those who report on Arbcom decisions to comment on the decision process, and to state the justification given (whether or not they accept it) for the verdict. That has not happened here. No justification for the rather surprising outcome "we should suppress this information" is mentioned in this Signpost article. Maproom (talk) 22:31, 3 June 2020 (UTC)[reply]



       

The Signpost · written by many · served by Sinepost V0.9 · 🄯 CC-BY-SA 4.0