🇮🇷 Iran Proxy | https://www.wikipedia.org/wiki/Wikipedia:Arbitration/Requests/Case/Kudpung
Jump to content

Wikipedia:Arbitration/Requests/Case/Kudpung

From Wikipedia, the free encyclopedia
Main case page (talk) — Evidence (talk) — Workshop (talk) — Proposed decision (talk)

Case clerks: CodeLyoko (talk) & Miniapolis (talk) Drafting arbitrators: Joe Roe (talk) & Casliber (talk) & SoWhy (talk)

Case opened on 03:43, 14 January 2020 (UTC)

Case closed on 22:47, 29 February 2020 (UTC)

Watchlist all case (and talk) pages: Front, Ev., Wshp., PD.

Case information

Involved parties

Prior dispute resolution

ANI

Preliminary statements

Statement by Guerillero

Kudpung has seemed to be taking a liking to leaving vaguely threatening messages on people's talk pages that he is in a dispute with. There is also this weirdness from 2018. I get that NYB would like to resolve this in some sort of informal way, but actions like this are beyond the pale of conduct that I expect from administrators. There is no amount of informal i-bans that solve the problem that Kudpung is still an administrator.

People have mentioned other conduct on ANI surrounding new page patrolling and other problems. I am not involved enough with Kudpung to be able to speak to any other issues. I hope that other editors are able to fill in more information about.

@Xeno: I have seen the two to three examples on ANI and I don't know of any others. I brought this to you all, because trying to resolve admin conduct issues at ANI is a fools errand. Ed, Sandy, Carrite, and myself all mentioned that this should be brought to arbcom, and I figured that we were a broad swath of opinions on the the project. So, I posted the case. I haven't followed this situation at all and was completely uninvolved until a few hours ago when I posted this. --Guerillero | Parlez Moi 17:21, 8 January 2020 (UTC)[reply]

To further what SandyGeorgia is saying, if this was purely an anti-admin vendetta, then why are there several functionaries and stewards urging this case be accepted? The shoe doesn't fit. --Guerillero | Parlez Moi 16:13, 12 January 2020 (UTC)[reply]

Statement by Kudpung

Apart from the fact that this is ostensibly a vendetta, I trust that for once the Arbitration Committee will do a thorough - and by that I mean thorough - investigation of all the facts, and of the motivations of those who will come here to comment, and not be influenced by negative comments that will come from those who have no axe to grind other than a general antipathy towards adminship as an institution. I also expect that any sitting Arbitrators who have piled on in the past two years will have the decency to recuse themselves. By that, I also mean that the background and behaviour of those who have instigated, or caused this case to be instigated should also be thoroughly examined. I have not been accorded the time to react upon the exchange of email with NewyorkBrad and decide how I would answer to ANI - it is midnight here where I live and I will not be at the beck and call of a pitchfork-wielding mob. That's all I have to say and if the committee votes to take the case, so be it and it can take its course. Kudpung กุดผึ้ง (talk) 16:54, 8 January 2020 (UTC)[reply]

@Cassianto:, at no time did I accuse Eric Corbett of being a troll. It was unfortunate that that account later turned out to be Corbett himself and it . ewas certainly by coincidence and not by design. Let this Committee examine the veracity of your claims. Kudpung กุดผึ้ง (talk) 07:18, 9 January 2020 (UTC)[reply]

@Xxanthippe:, there was nothing ' devastating and demoralizing' about any encounter you had with me. The unsigned post on my talk page by Ritchie333 which you mention: I think it's off-topic for Jbh's RfA, but if somebody dragged Xxanthippe to ANI and proposed a one-way interaction ban with Megalibrarygirl, I would support it... was a sequel to the behavior you displayed on that RfA. If you were to be more forthcoming about the issue, you would have mentioned the long thread two years ago where a great many admins (I believe over 18) and established editors voiced their opinion on your vote on the talk page of Wikipedia's most successful run for adminship, and which turned out to be one of the longest RfA behaviour discussions in history. There is no way you can claim you were not aware of the discussion about it. Let the Committee examine the thread and the veracity of your claims. Kudpung กุดผึ้ง (talk) 07:18, 9 January 2020 (UTC)[reply]

@SandyGeorgia:, you offered the thread, [-https://en.wikipedia.org/w/index.php?title=Wikipedia_talk%3AWikipedia_Signpost%2F2019-12-27%2FFrom_the_editors&type=revision&diff=932787067&oldid=932740609 here it is again}. I expect the Committee will be gracious enough to examine it in its full context before passing judgement. Kudpung กุดผึ้ง (talk) 07:18, 9 January 2020 (UTC)[reply]

@Chris.sherlock:, I understand that you are feeling victimised here, and that others have chosen the issue to escalate some of the comments I have made around Wikipedia out of context and out of all propportion. The fact is, that having been very successful in the past at identifying sockpuppets and undisclosed paid editors (some of whom were carrying out the most distressing blackmail and extortion of families and their children off-Wiki) that I have a naturally inquiring mind - some may say a nasty suspicious one. You won't be aware of the reason why I started the thread at [New Page review talk page],but it should have been clearly evident why I had thought that the account had possibly been compromised (the PRODed creations were so much out of character for such an experienced editor and admin - over 700 articles created), but at the same time not wanting to dance on the grave of that user's previous history. Your intervention came as a surprise especially from an account that had been dormant for literally years.

I therefore quite naturally began to be inquisitive. It was not until it was pointed out to me privately in the last 24 hours or so, that there was a consensus to unblock you, albeit under an account other than the one that it still logged as indeff blocked. I will not go into the full details of the successful unblock request , but the final support vote and comment by Bishonen carries an important councel. We should be grateful for some of the important work you have done in your time for Wikipedia, and history in both your case and that of Missvain has shown that the community can be very forgiving. Any reason for my having examined your accounts and editing history have been resolved and I see no need or reason to engage with you further. Kudpung กุดผึ้ง (talk) 07:18, 9 January 2020 (UTC)[reply]

@Chris.sherlock:, thank you for your response. I largely wrote WP:NPP, created the WP:NPR user right, collaborated on the development of Page Curation 7 years ago and its overhall last year, and finally (with the help of others) got ACTRIAL rolled out and the ACPERM implemented. After a decade of such work, (without self-agrandising), it's clear that I had become somewhat obsessive with it, especially as during the course of that work I had discovered some very unpleasant people, some in fact whom I had met in person and trusted, but who are now firmly blocked and banned.

I therefore decided a year ago to step back from NPP and as soon as it was possible, I encouraged others to take over the initiatitive which they are doing very well. Although NPP still has a huge backlog and we have not even scratched the surface of the number of people abusing the encyclopedia to their own ends, they don't need my help now and I will no longer be taking an interest in New Page Patrol or the quality of new content - it's a thankless task and not worth getting in trouble over. Not being the youngest Wikipedian, (but probably not the oldest) I also have my health to consider. Thank you for your kind comprehension and let's let this be an end to the issue - at least as far as it concerns the two of us. Kudpung กุดผึ้ง (talk) 08:23, 9 January 2020 (UTC)[reply]

Preliminary decision

Clerk notes

This area is used for notes by the clerks (including clerk recusals).

Arbitrators' opinions on hearing this matter (8/2/4)

Vote key: (Accept/decline/recuse)

  • I think since Kudpung and I have worked together closely in the past, albeit in 2011, I should recuse here. WormTT(talk) 16:49, 8 January 2020 (UTC)[reply]
  • Recuse due to my own past conflicts with Kudpung. GorillaWarfare (talk) 16:57, 8 January 2020 (UTC)[reply]
  • Guerillero: You wrote "taking a liking to", are there other examples? As the incidents thread is ongoing, I don't know that we can say the community has been unable to handle it yet. Additionally, Kudpung has not had the opportunity to respond adequately following Newyorkbrad's email. –xenotalk 17:03, 8 January 2020 (UTC)[reply]
    Response to Guerillero who wrote "trying to resolve admin conduct issues at ANI is a fools errand" In my opinion, administrative conduct issues are better raised at WP:AN rather than ANI, where they have a greater chance of being viewed by a wider range of the administrative community. –xenotalk 17:35, 8 January 2020 (UTC) Clarified. –xenotalk 16:53, 9 January 2020 (UTC)[reply]
  • Awaiting statements; in particular from Kudpung, but also any that demonstrate a pattern or that show prior forms of dispute resolution have been (or will be) unable to adequately address these concerns. –xenotalk 19:09, 8 January 2020 (UTC)[reply]
    Kudpung: Do you understand why other editors have taken issue with "vague statements" concerning other editors such as the one that prompted this case request? Are you willing to take these concerns into account and modify your approach to avoid this form of interaction in the future? –xenotalk 14:51, 9 January 2020 (UTC)[reply]
    • I had (perhaps naively) hoped this might be resolvable as a declined case request, one that delivered structured feedback that Kudpung would take on board and self-moderate, but since they have chosen not to engage further at the request stage, I would accept the case. There do not exist community processes to adequately or effectively address the concerns raised. –xenotalk 12:15, 12 January 2020 (UTC)[reply]
  • Kudpung, an admin, is subject to minimum standards of conduct and it is this committee's job to review users possibly not meeting those standards. Kudpung has earned a degree of faith and trust, having edited for a long time, that their aggregate effect on Wikipedia is beneficial. But I am convinced here that we should be looking in more detail at the effect he has had in certain situations. Accept. AGK ■ 14:18, 10 January 2020 (UTC)[reply]
Please tell me if I missed some but from that I can't see that previous steps of dispute resolution were actually exhausted or even tried. Yes, ArbCom is the only instance that can desysop someone but desysop is not the only possible sanction and the community can impose other sanctions. But for that, they need to actually discuss them. Except the current ANI thread, I see no evidence that this was attempted. Unfortunately, with the case request, the ANI discussion stalled and probably should instead continue. Furthermore, Kudpung has since elaborated on their comment and apologized to Chris and Chris has himself indicated that he is willing to work with Kudpung going forward. So as long as there is no evidence of the community actually attempting and failing to resolve the alleged user misconduct issues, this request seems premature. Decline at this point with no prejudice against refiling if and when the circumstances change. Regards SoWhy 08:38, 9 January 2020 (UTC)[reply]
@Rschen7754: I don't think the comparison to Fram is valid. Multiple case requests were filed because the community has proven incapable of handling it. Was it wrong to decline the case requests until T&S did what they did? Maybe. But in this case there is no real evidence so far that the community has even attempted to handle it. If ArbCom is the final step of dispute resolution, previous steps should at least have been tried, shouldn't they? Regards SoWhy 19:18, 9 January 2020 (UTC)[reply]
@Black Kite: The only reason why many editors (grudgingly) accept that a body such as ArbCom has to exist is that they understand that sometimes the community is unable to fix a problem. As I noted above, my decline at this point of time stems from the fact that there seems to be no attempt to solve such problems by the community beforehand. If someone can demonstrate that the community has tried and failed to solve those issues, I'm happy to reconsider. But so far I was unable to find any such community-wide discussion. Regards SoWhy 10:43, 10 January 2020 (UTC)[reply]
  • The impetus for this case request is the dispute between Kudpung and Chris.sherlock, which appears to have been resolved amiably. However, there are several comments here suggesting that this is a pattern of behaviour that is indicative of a recurrent problem. If that is the case it would broaden the scope of this request from a dispute resolution case to an administrator misconduct case, which cannot be satisfactorily resolved at other venues. I'm still mulling over the merits of this request, but the bottom line for me is this: If one of our administrators is habitually making good-faith contributors feel uncomfortable or threatened, we have a duty to take those allegations seriously. – bradv🍁 15:20, 9 January 2020 (UTC)[reply]
    Accept. I've taken another read through the comments here, and there are a lot of concerns that can not be appropriately addressed by dismissing this request. Many of them focus not on the most recent issue, but on an ongoing pattern of behaviour that falls short of the conduct we expect from our administrators. We have a duty to perform a thorough examination of all the facts, as even Kudpung has requested, and not to bury this or kick it back to AN. It's quite possible that nothing will come of this, but we do ourselves a disservice if we don't take complaints of administrator misconduct seriously. – bradv🍁 04:14, 10 January 2020 (UTC)[reply]
    I wouldn't say that all administrator misconduct cases cannot be satisfactorily resolved at other venues, but it may be so in the present case. Carrite wrote above that "only Arbcom has the authority to sanction administrators in a meaningful way", however there are administrators presently under community restriction, and administrators can be warned and blocked (even indefinitely), just as any other user. As above, I agree ANI is not a good venue for this: AN is a better venue to raise serious concerns about administrator behaviour, and if that venue cannot adequately address the concern, it should then be brought to case requests. I am sympathetic to the fact that following RFC/U being marked historical that case requests are the only formal and structured way, but that does not mean that lesser forms of dispute resolution may be short-circuited without good reason. I do understand that warning or blocking fellow administrators is not a pleasant or easy task, but neither is warning and blocking fellow editors, and administrators are tasked with this also. Perhaps we require more administrators willing to add themselves to Category:Wikipedia administrators willing to make difficult blocks. All that being said: there are only 19 administrators presently in that category, with some of them likely to have past interactions with Kudpung; even looking at the present request: out of 9 arbitrators reporting, almost half have recused. So it is possible that there are no administrators available that are sufficiently uninvolved, sufficiently experienced, or sufficiently motivated, to actually attempt to moderate this situation via direct administrative involvement and if that is the case, the committee is required to intervene. –xenotalk 16:06, 9 January 2020 (UTC)[reply]
  • Accept as issue of admin conduct has been raised - which is separate to the dispute, which has now been resolved. Cas Liber (talk · contribs) 04:25, 10 January 2020 (UTC)[reply]
  • Accept, albeit somewhat reluctantly, to examine Kudpung's conduct. The nature and quantity of the concerns is such that I feel that punting the issue back to AN(I) would be worse than accepting a case. Maxim(talk) 15:31, 10 January 2020 (UTC)[reply]
  • I believe a sufficient number of concerns from a wide range of editors have been brought forward that a case should be accepted to investigate the matter further. Mkdw talk 03:33, 11 January 2020 (UTC)[reply]
  • Accept, following my rule of thumb that the committee should take any admin misconduct case that isn't totally spurious. On the prior dispute resolution point: we all know that AN(I) is a terrible place to bring concerns about long-term conduct, especially with admins or other popular editors, so counting threads there doesn't give an accurate picture of the how close to the end of the community's tether someone is. The number of people asking us to accept this case does, and I think obligates ArbCom to examine the facts of the matter. – Joe (talk) 14:45, 11 January 2020 (UTC)[reply]

Temporary injunction (none)

Final decision

All tallies are based the votes at /Proposed decision, where comments and discussion from the voting phase is also available.

Principles

Administrator conduct

1) Administrators are trusted members of the community, who are expected to follow Wikipedia policies and are held to a high standard of conduct. They are expected to perform administrative tasks to the best of their abilities. Occasional mistakes are entirely compatible with this; administrators are not expected to be perfect. However, repeated or egregiously poor judgment may result in the removal of administrator status.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Leading by example

2) Administrators are expected to lead by example and to behave in a respectful, civil manner in their interactions with others. While such an ideal applies to interactions with all editors, it is particularly relevant to interactions with newer and inexperienced users, as in those cases, administrators provide a public face to both the broader administrative corps and to Wikipedia as a whole.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Administrator accountability

3) Administrators are expected to objectively consider criticism and questions relating to their decisions including those raised by anonymous editors. For an administrator to not promptly and appropriately deal with concerns, without good cause, may constitute misconduct.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Decorum

4) Wikipedia users are expected to behave reasonably, calmly, and courteously in their interactions with other users. Unseemly conduct, such as personal attacks, incivility, assumptions of bad faith, harassment, disruptive point-making, and gaming the system, is prohibited.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Anyone can edit

5) Wikipedia was founded on the principle that "anyone can edit" and that by the collaboration of editors of all backgrounds, the best possible encyclopedia can be created. Hostility towards any editor is prohibited by Wikipedia's conduct policies and, if directed towards a particular group, can be especially damaging to the inclusivity of the project.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Treatment of new editors

6) Wikipedia articles are improved through the hard work of both regular editors and newcomers; every new editor is a potential long-term contributor. All editors should therefore assume good faith when dealing with new editors and, if it is necessary to comment on problematic actions, do so in a clear and polite manner. Treating newcomers with hostility can alienate a potential contributor and is therefore detrimental to the project as a whole.

Passed 8 to 1 with 1 abstention at 22:44, 29 February 2020 (UTC)

Proposed deletion

7) Proposed deletion (PROD) is a streamlined process for nominating an article for deletion. It should only be used for obvious and uncontroversial deletions where no opposition is expected. Proposed deletions are subject to the deletion policy, which requires that alternatives to deletion are considered before nomination. A prior search for more sources to establish notability is not required but considered good practice when the main concern is lack of notability or sources.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Findings of fact

Kudpung

1) Kudpung (talk · contribs) has been a user since 2006 and an administrator since 2011. He has made over 100,000 edits and performed more than 14,000 admin actions. He has been particularly active in coordinating and driving improvements to the new page patrol process over many years.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Kudpung's conduct

2) Kudpung has occasionally made remarks towards other editors that could be interpreted as personal attacks.[14][15][16] In disputes with other editors, he has also made nonspecific threats of retaliating against or "investigating" the other party.[17][18][19][20][21]

Passed 9 to 0 at 22:44, 29 February 2020 (UTC)

Kudpung's accountability as an administrator

3) Kudpung frequently reacts to feedback on his conduct unobjectively and without assuming good faith. On multiple occasions, he has interpreted criticism as a vendetta against himself [22][23][24] or admins in general, making numerous references to an "anti-admin brigade".[25] He often reacts to criticism by dismissing it as "trolling" or similar [26] or by requesting that users not edit his talk page (at least six times, by Kudpung's own count).[27][28]

Passed 9 to 1 at 22:44, 29 February 2020 (UTC)

Previous attempts at resolution

4) Multiple users have individually counseled Kudpung about his behavior in messages on his talk page or in the context of other discussions including in 2018 (1), 2018 (2), 2018 (3), 2020. Kudpung has also been the subject of incident reports on the administrators' noticeboard including in 2015, 2017, 2018, (which each resulted in consensus that no action was necessary), and the 2020 report that was closed after the reporting user indicated that the issue was resolved. At this time, this Case request had already been opened.

Passed 8 to 2 at 22:44, 29 February 2020 (UTC)

Kudpung and Chris.sherlock

5) Kudpung made two comments to Chris.sherlock (talk · contribs) that Chris.sherlock interpreted as threats [29] [30]. This incident was discussed on the administrator's noticeboard and was considered to be resolved after Kudpung wrote privately to Chris.sherlock clarifying his intention.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Kudpung and Missvain

6) Kudpung nominated four articles created by Missvain (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) for deletion using the proposed deletion process [31][32][33][34]. Two of these nominations were made after he was made aware that Missvain would object [35][36] and therefore could not be considered "uncontroversial", as all proposed deletions are required to be. Kudpung also started a discussion of Missvain's autopatrolled right, although without mentioning her username or notifying her of the discussion.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Kudpung and GorillaWarfare

7) In August 2018, GorillaWarfare (talk · contribs) asked Kudpung to refer to her by her username "when discussed among men".[37] Kudpung reacted to negatively to this in comments referencing "men haters",[38][39][40] publicly withdraw his support from the Women in Red WikiProject,[41][42] and temporarily resigned as an administrator.[43] Later the same month, Kudpung wrote an article in the Signpost critical of WMF director Katherine Maher. GorillaWarfare commented on the piece, describing it as continued "misogyny" on Kudpung's part.[44] This comment led to an edit war and block of GorillaWarfare by uninvolved administrator Fram, which was subsequently overturned.[45][46][47] [48][49]

Kudpung and GorillaWarfare did not interact again until the ArbCom elections in November 2019. In response to a question about his boycott of Women in Red, Kudpung made reference to proud women [who] accuse such men [as Kudpung] of being misogynists.[50] GorillaWarfare interpreted this as referring to her, and challenged Kudpung on why he emphasised that she is queer.[51] Kudpung denied that he was referring to GorillaWarfare or any particular editor.[52]

Passed 9 to 0 with 1 abstention at 22:44, 29 February 2020 (UTC)

Kudpung's participation in this case

8) Kudpung has not submitted any evidence in this case. Kudpung made a statement during the workshop phase indicating he is willing to take on board objective criticism and generally try to learn from the feedback given, but he did not make any specific concessions to the criticism brought forth.

Passed 10 to 0 at 22:44, 29 February 2020 (UTC)

Remedies

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.

Kudpung desysopped

1) For his failure to meet the conduct standards expected of an administrator, Kudpung's administrative user rights are removed. He may regain them at any time via a successful request for adminship.

Passed 7 to 2 at 22:44, 29 February 2020 (UTC)

Kudpung admonished

2) Kudpung is admonished for failing to meet the conduct standards expected of an administrator. In future, he is urged to ensure that he remains civil in his interactions with both new and regular editors, and responds to feedback on his conduct objectively and with an assumption of good faith.

Passed 8 to 1 at 22:44, 29 February 2020 (UTC)

General reminder

3) Arbitration is supposed to be the final step in the dispute resolution process. The community is reminded that attempting to have a community-wide discussion of problematic behavior early on can prevent unnecessary escalations.

Passed 7 to 2 at 22:44, 29 February 2020 (UTC)

Proposed enforcement

Enforcement of restrictions

0) Should any user subject to a restriction in this case violate that restriction, that user may be blocked, initially for up to one month, and then with blocks increasing in duration to a maximum of one year.

In accordance with the procedure for the standard enforcement provision adopted 3 May 2014, this provision did not require a vote.

Appeals and modifications

In accordance with the procedure for the standard appeals and modifications provision adopted 3 May 2014, this provision did not require a vote.

Enforcement log

Any block, restriction, ban, or sanction performed under the authorisation of a remedy for this case must be logged at Wikipedia:Arbitration enforcement log, not here.