Wikipedia’s constitutional crisis may have come to an end.
The Wikimedia Foundation agreed that the English-language Arbitration Committee would have full power to review the one-year ban against administrator Fram. Three months later ArbCom unbanned Fram and removed his admin status while allowing him to apply for its reinstatement. The RfA failed and Fram withdrew. The details of the Fram case are covered in this month’s Special report. This article explores how we can address the underlying issues of the case moving forward.
At first glance, Wikipedia’s multilevel decision making process has shown that the en:Wiki community can protect its independence from the WMF, can make nuanced decisions about admin incivility and harassment, and protect editors against harassment once they file a complaint.
But on closer inspection, none of that was accomplished. The process was agonizingly slow, confused, and just ugly. The community did not come up with a method to minimize harassment in everyday practice. The difficulty of giving accused harassers enough information to defend themselves while protecting their accusers against potential further harassment was underlined. And any cooperation between the WMF and ArbCom or the community to prevent harassment was trashed as the WMF was routinely derided as the cause of the whole affair.
We believe that three issues must be addressed simultaneously before the constitutional crisis is resolved:
- How to protect editors against harassment? If we can’t protect our editors, we’ll lose our best and brightest. Wikipedia may become the playground of trolls.
- Can we find a reasonable method for accused harassers to defend themselves while still preserving the accuser’s ability to file a complaint without further harassment? and
- Can we cooperate using all the tools of the community, ArbCom, and the WMF to prevent harassment before it happens and deal effectively with it after a complaint is made? If we treat the WMF as the enemy, we’ll be losing many of the tools that can minimize harassment.
— The Signpost
A proposal that ignores one of the issues will ultimately fail on all three counts.
Voices from the community
ArbCom will soon start a request for comment on these and similar issues. The Signpost asked over a dozen well-respected editors how we can move forward rather than dwelling on the wounds of the recent past. Perhaps because the wounds are still fresh only 6 agreed to comment using their usernames. Another allowed their comments to be used without their username. All responses were edited for length.
Our movement has more or less relied on an unwritten division of power between the Foundation, the affiliates, and the communities. Our communities are generally self governing, except in a few clearly defined cases... Individual communities of course can and should be held to account if they are not meeting movement norms by the movement as a whole.
As our movement grows and brings in new people we need to move from an unwritten to a written division of power (ie a movement charter or constitution). Thankfully this has been proposed in our 2030 strategy process.[1]
With respect to the decisions of ArbCom, when the case was handed over I made it clear at the time that I will stand 100% behind whatever decision ArbCom makes and that is still my position.
— Doc James (in his volunteer capacity, not in his position as a WMF trustee)
Levivich wrote, "The project will not succeed if we ignore or outsource maintenance of the pillars. Each of us can see harassment when it happens on-wiki; each of us has an obligation to not tolerate it. If bystanders spoke up more often, victims wouldn’t need to report."
Levivich's proposal appears to be very difficult to implement. He is suggesting a complete change in Wikipedia’s culture. Perhaps this is the only way forward.
Wikipedia needs to improve the sometimes hostile and toxic environment for article creators and editors, both new and old. People who edit WP need to understand that encouragement of good faith new editors is equally as important as quality control …. There are guidelines and policies on WP that need to be respected, but these requirements can be handled with grace and cooperation, not the kneejerk I Don't Like It reactions too often seen.
— MontanaBW
One editor who preferred that his username not be used was skeptical that progress could be made "because one person's harassment is another's defending the encyclopedia." It would be easy to swamp ArbCom, “but if it were possible to filter out … misguided claims of harassment, a complainant might email ArbCom. The remedy might be to separate the people involved along the lines of ‘if the edits need attention, let someone else deal with it’…. There might be volunteer mentors who would act as intermediaries.”
I don't expect easy answers to the harassment and fair process conversations…. our open forms of dispute resolution seem particularly unsuited to addressing long-term poor behaviour that is countered with positive contributions...
Ultimately this is something that the community needs to decide on, and the Foundation needs to respect and support -- not take over.
While I am not happy with how the community interacts with Foundation staff (insults, personal attacks, and the like), this is ultimately a problem of the Foundation's own creation.
— Ajraddatz
Guy felt the WMF was to blame. His suggestions included:
- WMF needs to write a policy for interventions on projects that details the amount of autonomy those projects have and offers office escalation as an option where a project has no ArbCom equivalent...
- WMF needs to enact and document an internal review process, such that we can be confident that a ban is not enacted without fully independent review.
- WMF needs to set up an appeals process for bans, and allow third party appeals from functionaries / ArbComs of projects...
The mechanics for (reporting harassment) do exist, in that people could and should inform the arbitration committee or functionaries mailing list confidentially if they are concerned about their safety. However in practice, I do recall situations where the committee has been slow to respond or act.
Regarding providing a adequate means of defense for the accused, the general principle in the workplace is that the origin of a complaint must be known to a person as a default to allow dispute resolution or management to take place. This should be the case on WP unless a complainant can make a case to the committee that there is a compelling reason otherwise.
— Casliber
What's next
There are some areas of agreement in all these views. Everybody recognizes that there's a problem with harassment or with the WMF's approach to it. Some respondents believe that we have a system in place to deal with harassment, but perhaps it can be improved. Others think that for Wikipedia's approach to harassment to change, our editors' attitudes must change. Nobody praised the WMF's approach to the problem. The RfC to be run by ArbCom will be interesting.
As always, your opinion, politely expressed in the Comments section below, is appreciated.
How far should administrators go to protect Fram, now that he is not an administrator?
Administrator Sitush said, above, "I harass here every day and will continue to do so due to my belief that the content is what counts, not the people. I'm not here to be nice." I left a comment on User talk:Fram shortly before he moved the draft of his RFA from userspace. Sitush left me the warning "I think you should stop pestering Fram."
KillerChihuahua also left me a series of warnings; and I see other administrators are leaving similar warnings for other people.
We should all be civil. We should all not only start with civility, but do our best to remain as civil as possible, even if we think we are dealing with a very difficult person, or with a very clueless person, or a very rude person, or someone who is difficult, rude and clueless.
Would it be okay for an informal cabal of administrators to decide that Fram needs extraordinary protection, to make sure he is treated with kid gloves, until he has a chance to open RFA 3.0?
I suggest this would be a very bad idea.
What if you are an administrator who is a friend of Fram, or even just an administrator who remains angry with the WMF for banning him? Should you take extraordinary steps, independent from a cabal, to see that he is treated with kid gloves?
I don't think that is a good idea.
Fram made comments, when he withdrew his RFA, that implied he was going to try to learn from the opinions of those who opposed restoring his administrator bits. Now that he is not an administrator, I suggest it would be best if Fram enjoyed no more protection against uncivil or unfair comments than anyone else. If he is really going to learn what people were talking about, when they described him as uncivil, it would be best if Fram experienced what is our current normal level of civility, without extraordinary protection.
To return to the comment where Sitush said he or she is "not here to be nice", because "the content is what counts, not the people." Sitush, please remember, just as I am subject to normal human fallibility, and everyone else in this discussion is subject to normal human fallibility, you, Sitush, are similarly subject to normal human fallibility. You will make mistakes. Like everyone here, you will make mistakes.
Here is a thought experiment. Suppose you and I come across an edit to an article, or a comment, that strikes us as so terrible that go after the perpetrator, without restraint - only to realize we had completely misread the situation? I suggest that the attacking people without restraint is very damaging to the project. Every question, every disagreement, is a teachable moment.
So, please abandon the approach you described. I think administrators have an obligation to do their best to set an example of civility and collegiality -- "being nice" to use your term. I think it is essential because less experienced contributors look to administrators for an example of what is acceptable.
In addition, doing one's best to always be civil, and collegial, can turn out to be a huge relief, when one realizes the other guy was right, all along. Geo Swan (talk) 02:36, 6 October 2019 (UTC)
Facebook tracker on this page?
My Facebook container plugin found and warned me about an element on this page. Sure enough when I inspect the element, there is a div containing a CSS class called "fbc-badge" containing other facebook-related div's. What's odd though is Viewing the source doesn't find any of that. Anybody else's facebook container triggering on this page? First time I've seen this on Wikipedia. Jason Quinn (talk) 07:17, 6 October 2019 (UTC)