The Report this week is dominated by the Academy Awards, taking the top 4 spots and 13 of the Top 25 (if you count another big jump in views for Stephen Hawking at #4). In the aggregate this is not too much different than the past two years, where the top American movie award show took 12 slots in 2014 and 14 in 2013. The 87th Academy Awards article led at #1 with an impressive 6.2 million views, though a rather low mobile view count of 12.17% suggests those numbers might be somewhat inflated; Best Picture Birdman had 2.2 million views with 50% mobile views.
Also of note this week was the death of actor Leonard Nimoy (#5). Nimoy's article was also one of the most edited recently, and is currently topping the automated Top 20 most edited articles report as of March 1, showing that 193 editors have hit "edit" 524 times. As a recent creation, you probably didn't know this report existed—you should take a look.
For the full top 25 list, see WP:TOP25. See this section for an explanation of any exclusions.
For the week of February 22 to 28, 2015, the ten most popular articles on Wikipedia, as determined from the report of the most viewed pages, were:
Just as this year's awards held on February 22 were a bit predictable (Really? Birdman won? I'd never have guessed!), it was just as predictable that this entry would top the chart this week.
The death of this beloved actor on February 27, best known for playing the role of Mr. Spock in the Star Trek franchise, led to widespread tributes. Spock's Vulcan salute bade us to "live long and prosper," as Nimoy did himself.
America loves a good, old fashioned culture war, and while Clint Eastwood's American Sniper may not have wowed critics nor drawn great overseas crowds, it has played spectacularly well in America's conservative heartland. After dropping to #8 and 850,000 views last week, news that Eddie Ray Routh was found guilty of the deaths of Kyle and Chad Littlefield on February 25, after three hours of jury deliberations, raised the profile of this article once again.
A new entry to this chart, Whiplash won the Oscars for Best Film Editing, Best Sound Mixing, and Best Supporting Actor for J. K. Simmons (pictured). It had also been nominated for Best Picture. Whiplash was written and directed by Damien Chazelle based on his experiences in the Princeton High School Studio Band, and stars Miles Teller as a student jazz drummer who seeks the respect of an abusive teacher played by Simmons. Though critically acclaimed, you may not have been aware of the film, which had only grossed about $12 million worldwide (on a $3.3 million budget) prior to its Academy Award wins.
The release of the film adaptation (#11) of this onetime Twilightfanfic continues to draw fans, though it is very unlikely to be drawing Oscars this time next year.
The daughter of Melanie Griffith and Don Johnson plays the lead role in Fifty Shades of Grey (film) (see #11). Griffith and her daughter were at the Oscars (of course), where some inane kerfuffle on the red carpet occurred over the fact that Griffith hadn't chosen to watch her daughter's film. We know our parents and children have sex (God willing), but we don't need to watch it.
So why don't you kill me?: Numerous news outlets are reporting that the domain loser.com now redirects to the Wikipedia article for rapper Kanye West. Page views on West's Wikipedia article skyrocketed to almost 250,000 views on March 2, up from less than 19 thousand the previous day. At the 57th Annual Grammy Awards on February 8, West leaped on stage to interrupt Album of the Year winner Beck, but a moment later left the stage without saying anything. Beck first achieved fame with the 1993 single "Loser"; the song's chorus is referenced in our headline. CBC Newsreports (March 2) that a Twitter user claims responsibility and said that she has owned the domain for 20 years. G
I'll be there for Kim Jong-un: Wired published a long article (March 1) about activists who smuggle cultural products, including Western films and television shows like Friends, into North Korea on USB flash drives in an effort to destabilize the totalitarian military regime. It reports that one of the activist groups, the North Korea Strategy Center, "is working with the Wikimedia Foundation to put a North Korean-dialect version of Wikipedia on every flash drive it smuggles over." G
Hong Kong government slammed for citing Wikipedia: The South China Morning Postreports (March 1) that Hong Kong's government "has been accused of using standards of sourcing that would shame an undergraduate student after citing information from Wikipedia in Legislative Council papers." A.K.
Editors-for-hire on Wikipedia: The print edition of the Financial Times (February 27) featured an article on paid editing, with comments by the WMF's Katherine Maher, Michael Wood of Legalmorning, Dariusz Jemielniak and others. (The online version of the article is only available to FT subscribers.) A.K.
Arrested for Wikipedia edit: The Toronto Sunreports (February 26) that a member of the Canadian Armed Forces has been arrested for an inappropriate edit to the article Suicide of Rehtaeh Parsons and other online comments related to the case, according to Parsons' father. The case is also covered by Vice (February 26) and CBC News (February 27), which reports that "No charges have been laid, the man was released on several conditions and the investigation continues". A.K.
Online threats: The Irish Timesreports (February 25) that an Irish former medical student was given a three-year suspended sentence for sending threatening letters to instructors at the Royal College of Surgeons in Ireland after he was refused readmission. The letters threatened to reveal confidential medical information about 1,300 patients by posting it on Wikipedia. G
Wikipedia as sculpture: In an interview (February 25) with the Charleston City Paper, comedian Kyle Kinane was asked about the accuracy of some information about his family that appeared in his Wikipedia article. He said "Hey, man, what do you want to do, pull the curtain back on Wikipedia? I will say that Wikipedia, I never put that page up there, and I don't know how you access Wikipedia pages, but as long as it's nothing offensive or cruel to me or my family, I look at it like a living art project. I look at it like a literary sculpture that the public can access and augment at any time. So yeah, maybe my dad did sell beer at those events...When people are like, 'So, your grandfather was Lon Chaney Jr.'s stunt man?' I just go, 'Sure was, guy. Sure was.'" G
How Wikipedia reminds me: In an interview (February 25) with Music Times, Nickelback guitarist Ryan Peake expressed surprise that he had no Wikipedia article. Peake said " The less I'm on the internet, the better! I truly do appreciate any kind of privacy I can get living in the spotlight. It doesn't bother me. It's kind of nice that nobody's paying attention. I don't feel slighted whatsoever." A Wikipedia article on Peake was created in December 2002 but it was edited to redirect to his band in April 2011. Attempts to re-create the article in December 2013 and May 2014 were reverted. On the day of the interview's publication, another editor turned the redirect into an article. G
Editor's note: the Signpost has arranged to mirror Tech news from Meta-Wiki to supplement the long-form tech coverage in our infrequent Technology report..
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent software changes
A Lua function to use Wikidata has changed. You need to update the pages that use it. [1]
You can use the Content Translation tool on Wikipedia in Uzbek and Minangkabau. You need to enable it in your Beta options.
You can now hide banners if you don't have an account. [2][3]
Software changes this week
The new version of MediaWiki has been on test wikis and MediaWiki.org since February 25. It will be on non-Wikipedia wikis from March 3. It will be on all Wikipedias from March 4 (calendar).
You can use the Content Translation tool on Wikipedia in Punjabi and Kyrgyz. You can ask for the tool in other languages.
Editing the fake blank line in VisualEditor is now simpler. This change also fixed a few bugs. [4][5][6][7]
The TemplateData editor now warns you if a related page already has TemplateData. [8]
The TemplateData table now tells you if a template doesn't take any parameters. [9]
A new feature allowing one to more easily link to sections within an article was deployed this week as a default setting. [10]
Meetings
You can read the notes from the last meeting with the VisualEditor team.
You can join the next weekly meeting with the VisualEditor team. During the meetings you can tell developers which bugs are the most important. The meeting will be on March 4 at 16:00 (UTC). See how to join.
You can join technical meetings in France and Mexico this year. You will be able to ask for help if you can't pay yourself. [11]
Future changes
You will be able to get a direct link for a section of a page. [12]
Wikimedia Foundation quarterly report published, community consultation organized
The Wikimedia Foundation released its Quarterly Report last week covering the three months from October to December of 2014. The Foundation has been releasing and making publicly available internal operational reports—originally presented directly to the Board of Trustees—since January 2008. What makes the publication of this particular report notable from an organizational perspective is that it is the first report published since the Foundation's decision to move to a quarterly instead of monthly structure late last fall. A key reason for the decision was to better align reporting with the Foundation's generally quarterly planning and goal-setting processes. Due to the larger time spans, the new quarterly reports attempt to highlight key priorities more so than to present detailed quarterly activities documentation. Highlights from Foundation goings-on continue to be posted as blog-aggregated Wikimedia Highlights; more detailed information is presented in team-separated WMF quarterly reviews.
Making good on the new format, the Foundation has presented a much more visually oriented and succinct report than it has in the past this reporting round. Readers interested in the Foundation's initiatives may find it a good resource to review. Some highlights:
Mobile readership is ascendant: while global pageviews are flat (and concurrently, desktop traffic is in decline), mobile pageviews are on the rise, and the Foundation succeeded in raising the mobile fundraising share in the end-of-year campaign from 1.7% in 2013 to 16.1% in 2014. The Foundation-funded mobile web-viewing and editing applications have seen significant improvements as well.
The deployment of the HHVM interpreter tool late last year has reduced average edit save-time by almost half.
After impact analysis, Foundation grant disbursement has increased its focus on smaller projects, finding more and smaller projects to have more impact than fewer, larger ones. However, the total amount disbursed in 2014 actually decreased by 14% year on year, in part because the Foundation sees that project organizations "want non-monetary support ... [and are] focusing on institutional partnerships".
The Foundation reached its annual (as always, very conservative) US$58 million funding goal six months ahead of schedule in 2014. Funds raised from non-English-speaking countries increased by 42%, but still compose a small fraction of overall funding.
In related news, last week the Foundation kicked off strategic planning consultation with the Wikimedia community. This will be the second of the Foundation's five-year plans: the first such plan, begun in 2009 and published in 2011 (Signpost coverage here, here, and elsewhere), proved at best flat-footed. It contained wildly optimistic editor growth projections—a particularly notable projection failure, as editor numbers have actually decreased since the report's publication. The Foundation released a supplement, "Narrowing Focus", in 2012, and is now proceeding with a 2015 iteration of the report in changed organizational format:
“
Rather than trying to draft a five-year document for the entire movement, we are kicking-off what will become a discipline of ongoing strategic inquiry, assessment, and alignment. This more agile, adaptable process will directly inform and update our priorities and goals and help us maintain a strategic direction that is consistent with the Wikimedia vision, supports the Wikimedia projects, and is sensitive to the changing global environment.
The "Strategic Visioning" Community Consultation is the first step in our new strategic process. It is an opportunity for us to explore together what the future holds for the Wikimedia Movement and projects. We will learn from your ideas and use them to inform and refine our strategic thinking. From that, we will define the WMF Strategic Direction, which we will share with you in 2015. This Strategic Direction will guide us in our community support, engineering, grant-making, and fundraising and will be updated annually.
”
To participate in the consultation, follow the instructions; at the time of writing, the consultation had already drawn more than 200 responses.
Wikimedia OTRS team publishes annual report
The Wikimedia OTRS team has released its annual report for the year 2014. The OTRS team handles the Wikimedia movement's instance of the Open-source Ticket Request System, and is generally responsible for all queries, complaints, and comments from the public directed at the movement via email since September 2004. The report, both visually striking and very informative, presents a detailed report on the activities and actions of the OTRS team over the past year. Some highlights:
The OTRS team fielded 72,714 tickets in 2014, of which more than half were information requests, and another fifth were requests from copyright holders. The other third of the tickets were split among queries about chapter, photos, and various miscellaneous queues.
The number of requests fielded has declined somewhat from a peak of 84,571 tickets in 2010.
The OTRS team consists of 660 open accounts on OTRS and 850 inactive (closed) ones, as of the end of 2014.
In many cases the workload for individual ticket queues was predominantly distributed among one or two editors, and even among busy queues—such as en-info, which fielded almost four times as many requests as the next busiest info queue, de-info—a handful of editors tend to handle over half of requests, per the long tail.
The English-language team responded to 77% of its tickets within 24 hours; for other sizable teams the percentage ranged from 33% (info-es) to 80% (info-pol).
Tickets remain overwhelmingly directed at the Wikipedia projects. The cumulative 2014 total for sister projects came to just 782 tickets.
There were 12,857 photo-permission verification tickets, from editors checking about the copyright status of particular images, and 616 photo-submission tickets, from photographers releasing their work for use on Wikimedia projects.
To better reflect the status of the project's backlogs, the OTRS team will be moving to a monthly instead of quarterly report structure this year. The OTRS team is currently exploring applying for grants from the Foundation to hire external developers to improve the movement's OTRS software, and efforts are underway to expand project documentation. Editors are invited to post their responses to the report on the report talk page.
Train the trainer program held in India
This week saw the 2015 iteration of the Centre for Internet and Society's Access to Knowledge program's train the trainer community workshop (in shorthand, the CIS-ATK TTT). The event, first held in 2013, is a four-day intensive training workshop and program for a select group of Indic-language editors. As the title of the workshop implies, the event attempts to expose its attendees to and give them experience with the tools and skills they need to communicate with and encourage participation from prospective Wikimedian editors in their respective languages. After the event, participants are expected to begin implementing the "plans of action" they develop at the workshop, with support from the CIS-A2K team. Travel expenses to and from the event are covered by organizational stipends. There were 30 attendees overall this year, up from 17 in 2013.
The Centre for Internet and Society (CIS) is a Bangalore-based Indian NGO concerned with technological advocacy and multidisciplinary research in Internet and society. It is integrally involved in the Wikimedia India movement via the Access to Knowledge (A2K) program, a long-standing project ongoing since 2011 organized and funded in collaboration with the Wikimedia Foundation (coincidentally, the quarterly report this week). This event, one of the most visible results of these efforts, included seminars on public presentation, copyright law, Internet research techniques, digitization techniques, media strategies, and community-building, as well as multiple panel and group discussions, a GLAM activity session at Janapada Loka, and capstone individual outreach planning presentations.
This article was retitled after publication to reflect that the OTRS report was annual, not quarterly.
Indiegogo campaign for prolific Wikipedian photographer underway
An Indiegogo campaign to fund a macro lens and other equipment purchases for Wikipedian Jeevan Jose launched last week. Jee's wildlife photographs illustrate over 500 Wikipedia articles, including nearly 300 on English Wikipedia alone. The campaign, coordinated on Commons, launched on 22 February; the modest initial target—funding the purchase of a new macro lens—has already been exceeded. Fund-raising for additional small-wildlife photography equipment—such as a macro flash, camera bag, a travel tripod, and improved digital darkroom (computer & software)—continues. The campaign runs until 24 March.
Brief notes
Death of a Wikimedian: The Malayalam Wikipedia lost one of its most prolific contributors on 4 March. G. Balachandran, also known as Babug, joined the site in 2008. By the time he made his final edit, he had single-handedly created almost 1% of the site's total articles, despite being partially paralyzed from a debilitating stroke and suffering from several subsequent health problems. He was 76 years old. ViswaPrabha, who notified the Wikimedia community through the Wikimedia-l mailing list, wrote:
“
He always attributed his renewed energy and life's aspirations to the Wikimedia mission, for having returned to a meaningful life after a 20-year long and frustrating solitude while constrained to an immobile chair. Ever since 2008, he stood up and started walking and moving around. His was an extreme example for us in Malayalam [Wikipedia] to showcase how Wikipedia can change lives. ... For us in [the] Malayalam Wikipedia, today is a black day, for having lost a great beacon on our voyage to ultimate openness and freedom in knowledge and wisdom. Yet we feel [that] BabuG has made his life stamped immortal for ever and has shown us the pathway we should follow in continuing our humble contributions to the ultimate cause of mankind.
”
Wikidata for research forges ahead: Wikidata volunteers this week officially submitted their EU grant proposal for review. The proposal, developed for the Horizon 2020 European research initiative, aims to construct a virtual research environment connecting open-source databases across disciplines and languages worldwide through the Wikidata framework. With €1.5m of funding on the line, this is by far the largest competitive external grant that a Wikimedia project has ever applied for, involving coordination between the community, the Museum für Naturkunde, and more than ten other associated institutions throughout Europe. This week also saw additional follow-up meetings in Berlin, where a general proposal information session was held, and Bern, which hosted a hackathon focusing on the proposal's impact for taxidermy. See previous Signpost coverage for more details on the effort and its potential impact both on and off-wiki.
Metrics and activities: The Wikimedia Foundation will hold their monthly metrics and activities meeting on March 5th this week. The theme for this month's iteration is "VisualEditor & Mobile". Editors are invited to participate via YouTube stream or via IRC. Remote video participation via Google Hangouts, limited to eight participants, is also available.
Foundation board composition: The Wikimedia Foundation Board has been debating the propriety and nature of policies which may be put in place to increase the diversity of viewpoints on the Board, and is asking movement editors to post their thoughts on the Board's topical talk page.
Zero on video: The Wikimedia Foundation released a short video this week presenting an overview of the Wikipedia Zero initiative. The Zero initiative is a no-charge access mobile data access plan for movement Wikipedias that offers a beneficial reciprocal relationship between the Wikimedia Foundation and service carriers in a number of countries worldwide; see previous Signpost coverage (or, indeed, the video, at right) for more details.
Around the world
Norway: Astrid Carlsen has been elevated to the position of Executive Director of Wikimedia Norway following elections by the Wikimedia Norway board. Carlsen previously served as the organization's GLAM officer; among other things she was integrally involved in the chapter's Wikinobel collaboration last fall.
Tenth anniversary of the Bengali Wikipedia: The Bengali Wikipedia celebrated its tenth anniversary in January. A gala was held on February 26th of this month to celebrate, with Jimbo Wales in attendance.
Contest time: The sixth annual English Wikipedia Core Contest will run all through the month of March this year. The Contest focuses on improving Wikipedia's vital articles, particularly those in the worst state of disrepair; prizes, in the form of electronic store vouchers, are to be awarded.
New administrators: Congratulations to Fenix down, the newest administrator.
Stewards elections: The 2015 Stewards elections officially closed this week. A live final tally is available here.
Art and Feminism challenge: The Art and Feminism Challenge, for content work related to female artists, is set to run on March 7–8.
Editor's note: eagle-eyed readers will have spotted that we promised an interview with Newyorkbrad for last week's Signpost. We were unfortunately unable to deliver the interview as planned, and it is instead below. Our apologies to Newyorkbrad and to any readers who may have been disappointed by the interview's absence last week.
In the first of what the author hopes will become a regular feature of the Arbitration report, the Signpost speaks to veteran arbitrator Newyorkbrad, who recently retired from the committee after almost seven years of arbitrating. The Signpost was keen to hear his thoughts on his time on the committee and on the past, present, and future of ArbCom.
Harry Mitchell: What motivated you to stand for election back in 2008? And to twice seek re-election?
Newyorkbrad: Like almost every new user, I started editing Wikipedia in 2006 with the intention of working on articles. However, I quickly became aware that there was a back-office administrative apparatus to the site, including the arbitration pages. Although I wasn't a party to any arbitration cases, I began to comment on requests and to draft proposals for the workshop pages, which are open to any editor, not just the arbitrators. I also participated some on AN and ANI, making comments on disputes and how they might be resolved. And I started writing essays and thinking about some of the key issues facing the project, notably BLP issues.
Some kind editors saw my work and suggested that I might make a good arbitrator. They suggested that I run in 2006, just a few months after I'd started editing, but it was too soon then. In January 2007, I passed RfA and became an administrator. Around the same time, I also became an arbitration clerk, meaning that I helped run the arbitration pages and assisted the arbs in maintaining them. (The procedures were simpler then, even though there were a lot more cases than there are now.)
By the end of 2007, I thought I had enough experience to be a good arbitrator, so I ran in the election and was elected.
I ran for reelection in 2010 because I was still enjoying the role of arbitrator (well, as much as anyone ever enjoys that role) and I thought I was doing a good job. The majority of the community was kind enough to agree with me. My decision to run again in 2012 was much harder, because by that point I'd been an arb for five years, which is plenty, but several editors I trust suggested that I should seek one more term and so I did. At that time, I vowed that my third term would be my last, and I never had second thoughts about that decision.
HJM: What do you think ArbCom does well? What does it do less well? Is there anything it does at present that you feel it shouldn't do at all?
NYB: I think ArbCom has made some good decisions and some less-good decisions in most areas of its responsibilities. I wouldn't answer your question categorically with anything like "it does a good job on arbitration cases and a bad job on ban appeals and checkuser appointments," or the reverse, or anything like that based on categories of work. Like everyone else, I agree with some of the Committee's decisions over the past seven years and disagree with others.
I also can't think of any categories of the Committee's work as to which I would say "why the heck is the ArbCom handling that? What were they (we) thinking when they took that on?" There are, however, areas of responsibility that have landed on the Committee's plate as a matter of default more than anything else. I doubt that any arbitrators would insist on holding on to these responsibilities if the WMF Office (in a couple of cases) or the En-WP community (in others) agreed to take over the area.
HJM: How effective do you think ArbCom is at resolving the wiki's most interminable conflicts?
NYB: It's a mixed bag. Anyone can take a look at the list of the Committee's completed arbitration cases (found at WP:RFAR/C) and think "this dispute seems really to have calmed down since this case was decided," or conversely, "the ArbCom decision doesn't seem to have made a dent in that one."
One could potentially divide the Committee's cases into two broad categories, albeit with a good deal of overlap: one group dealing with specific editors (including admins), and the other group dealing with specific topic areas. If a case concerns one particular editor, it's comparatively easy to figure out whether that editor is still causing issues (if he or she is still editing), or whether he or she is missed and could have been saved (if the editor wound up being banned). In the case of topic-areas, ongoing contentiousness in the topic-area is often a function of the topic-area's real-world contentiousness today, not anything the ArbCom or Wikipedia does. Not to be flippant, but there will never be real peace on Ukraine until there is peace in Ukraine, and so forth.
As I said when I wrote a book review for the Signpost last year, I think we have a project-wide myopia about evaluating the success of our dispute-resolution mechanisms. No one goes back, a couple of years after an ArbCom decision, and tries systematically to say "well, this approach seems to have done a good job of resolving this type of problem" or "that remedy was pretty much of a disaster." We learn anecdotally, and experientially, but there's no attempt to collate the experience systematically. I say that it's a project-wide myopia because there's not enough effort to learn from the everyday experiences in other dispute-resolution processes either. For example, there must be a way of synthesizing the collective experience of thousands of 3RR reports about whether blocking or protecting or chatting is the best way to solve an edit war—not only to immediately stop the back-and-forth, but to maximize the future good-faith contributions of both parties—but I've never seen it written up anywhere.
HJM: How has the committee changed over your seven-year tenure?
NYB: The main change is that the case workload has decreased radically, because a lot of disputes that would have come to arbitration a few years ago are now resolved in other venues. I discussed that trend here a couple of years ago and it has continued since then. The result is that the Committee has fewer easy or straightforward cases these days, but only complicated morasses to try to help with.
HJM: How much time in an average week did you find yourself devoting to ArbCom business? Do you think the current workloads are too great?
NYB: You refer to "an average week" but I'm not sure there really was such a thing. There were heavy weeks, such as when I was reviewing evidence and drafting a decision or when I was on the Ban Appeals Subcommittee (BASC) and there were a lot of ban appeals, and there were other weeks that were lighter. On average I might say 5 to 10 hours a week but that is just a guestimate. I don't think the current workload is as insuperable as some people would suggest, but it couldn't hurt to lessen it, as long as the responsibilities taken away were handed off to appropriately qualified and selected people.
HJM: Did you implement or contribute to any reforms during your tenure?
NYB: I tried to emphasize the importance of being fair to all the participants in every case. I don't want to call that a "reform", which would suggest that previous arbitrators didn't care just as much as I and my colleagues did, but the arbitration process is complex enough that it's a useful thing to re-emphasize from time to time.
I called a couple of times for trying to simplify the arbitration processes and pages. For the most part I failed miserably at that; there is still more "paperwork" involved in arbitration than I'd like. One of my (and some others') suggestions that was accepted was combining the "clarifications" and "amendments" pages, because we were wasting time worrying about whether a given request was for a clarification or an amendment. This was an improvement, though I wouldn't call it a "reform".
I stood up for the principle that ArbCom has the authority to review and, if warranted, overturn a community ban or community sanctions decision. I simultaneously emphasized that we wouldn't often exercise that authority, but I do think it's important that there be some avenue of appeal from AN and ANI, which like any other decision-making venue can be fallible. I understand the reasons behind the proposals to remove BASC (ban appeals) work from the ArbCom's task-list, but I cannot support them unless there is a genuinely independent, high-level review board taking BASC's place. And even then, some appeals will still be resolvable only by ArbCom because non-public information is involved.
(As a sidenote, I've never understood the wiki-maxim that AN and ANI "are not a part of the dispute resolution process." These days, they're where most of the complicated disputes get resolved—or, often enough, fail to get resolved.)
HJM: There has been significant discussion over the years about the possibility of arbitrators who have not previously been elected administrators. How would you feel about non-admin arbitrators?
NYB: It's never bothered me that all of the arbitrators have been administrators, because that has been a collective community decision (as opposed, say, to having a rule that non-admins can't run in the election, which I'd oppose).
I think that many voters in the election view adminship experience as proof that a candidate is committed to helping administer the project, and as providing a basis for evaluating the candidate's skills in doing administrative work, including dispute resolution. (I don't believe it has anything to do with creating a caste system among editors, as some critics have suggested.)
On the other hand, it also wouldn't bother me if a non-administrator were elected. If that occurred, though, I think the community would need to agree to provide that arbitrator with the equivalent of adminship for the duration of his or her term (or else the candidate should launch an RfA right away, which he or she would certainly pass). I say this because there are rights available only to admins, most notably access to deleted revisions, that are necessary for working on some cases and appeals.
HJM: Is there anything you regret about your time on the committee? Any reform left undone, a decision that had unexpected repercussions? Anything you would do differently with the benefit of hindsight?
NYB: Among other things, I regret the two major incidents in which large numbers of e-mails on the arbitrators' mailing lists were hacked or leaked and published on other websites. This obviously compromised the confidentiality of our discussions and of communications we received from others. We've taken every step we could think of to avoid any recurrence of this problem. (Incidentally, we still don't know who did it.)
I regret a few of the hundreds of votes I cast on Committee decisions, though not very many.
I regret a few of the times I was outvoted, and an editor was banned or an admin was desysopped who I thought need not have been. On the other hand, I was consistently viewed over my tenure as perhaps the most lenient arbitrator—there is truth to that perception, though at times it is oversold—and I probably was in error sometimes in voting to keep an editor around who created more dissension and disruption than we should be prepared to tolerate.
I regret the two times, both early in my tenure, when I was talked out of a first draft of a controversial but necessary decision, and it soon became apparent I should have stuck to my guns. Long-time readers will know which cases I mean.
I regret that I didn't get to serve full terms with some of my most qualified and knowledgeable colleagues. In an earlier draft of this answer I had mentioned a bunch of them by name, but I'm fearful of leaving someone out.
I don't regret my decision to participate in the major Wikipedia criticism sites, which was very unusual for an arbitrator when I first showed up there—but I do regret a few times when I've found myself being blatantly trolled there, which didn't do the Committee or anyone else any good.
And I apologize for the worst of my bad jokes.
HJM: What qualities do you think a prospective candidate in this year's elections should have?
NYB: I think the community has elected very qualified arbitrators in recent elections, so I don't have much to add to whatever criteria the voters have been using.
HJM: What advice would you offer the remaining arbitrators, especially those who are just embarking on their first term?
NYB: I don't have much unexpected advice for the new group of arbitrators, because they are settling into their roles very well. Although my term as an arbitrator expired last December 31, I remained on the mailing list during January, because I was still an active arbitrator on the GamerGate case. During that month, I was highly impressed with the energy level, commitment, and knowledge base of the new group of arbitrators, seven of whom were brand-new to the Committee. Early in the nominating process for the election, there had been concern that there wouldn't be enough well-qualified candidates to fill the nine seats, but that turned out not to be the case.
A major piece of advice that I would give to the new arbitrators is to pace yourselves so as to avoid losing perspective and the possibility of premature burnout.
Another piece of advice—which I struggle to follow myself—is to try to spend at least some of your wikitime in mainspace. That, and not the back-office apparatus, is what the project is about.
HJM: If you could change one thing about ArbCom, what would it be?
NYB: Fewer interviews.
HJM: Where do you see ArbCom in five years' time? Ten years?
NYB: It's hard to answer where I see ArbCom in five or ten years' time without knowing where Wikipedia itself will be in five or ten years' time. There will always need to be a dispute-resolution procedure of last resort, and having a Committee of experienced, community-elected people address the disputes is as good a system as anyone has been able to come up with thus far.
HJM: Would you stand for election again in the future or do you see your priorities changing?
NYB: Given that I was active on GamerGate until it closed at the end of January, I've been fully off the Committee for just a month now—so it's premature for me to address whether I'd ever want to serve on it again. But since you ask, I have no plans to run for arbitrator again, and certainly not in the foreseeable future.
In addition to leaving ArbCom, I've also relinquished my checkuser and oversight rights (which I had rarely used anyway), though I remain an active administrator. I expect I'll comment on an AE or ANI thread on occasion, especially if I believe I could offer a perspective that others might miss. But my plan is to focus my Wikipedia efforts on content for awhile, as I had planned and hoped to do all along.
HJM: Is there anything you'd like to add?
NYB: I'd like to thank all the members of the community who elected me to the Committee three times, and who have said kind things to and about me during my service.
Beyond that, nothing to add off the top of my head, though I'll keep an eye on the comments section below and will probably wind up writing more there.
This fortnight's business
Things appear to be settling down now that the new committee is in place and the traditional rush of cases at the start of the year is slowing. Only one case remains open at the time of writing; another was closed in the fortnight since the last report.
After a stall during the proposed decision phase, this review of 2013's Infoboxes case—opened as a result of multiple clarification requests—finally concluded on 4 March. The purpose of the review was to assess the fitness for purpose of a remedy from the 2013 case, which prohibited Pigsonthewing from adding or removing infoboxes and from discussing their addition or removal. The review, and the enforcement and clarification requests which preceded it, focused largely on whether Pigsonthewing's participation at Templates for Discussion (where he regularly nominates infobox templates for deletion or merging) was in keeping with that remedy.
The arbitrators were satisfied that Pigsonthewing's conduct had improved since the disputes which precipitated the 2013 case—Courcelles (one of the drafting arbitrators) observed "I remember the 2013 case, and I honestly believe [Pigsonthewing]'s conduct is better [now] than it was back then"—but remained concerned that his conduct was still wanting. Arbitrator Yunshui, for example, saw "at least some comparatively recent instances of inflammatory behaviour [by Pigsonthewing], whether provoked or not". Remedies proposed included banning Pigsonthewing from any involvement with infoboxes anywhere on Wikipedia (opposed by all but the proposer on the grounds of Pigsonthewing's progress since 2013), discretionary sanctions on infoboxes (rejected because it was possibly out of scope for the review, and several arbitrators expressed concerns about its workability), and several more complicated restrictions on Pigsonthewing (rejected because of their complexity and concerns about workability). The final result was that all previous remedies against Pigsonthewing were vacated, and in their place Pigsonthewing:
is indefinitely restricted from adding an infobox to any article;
may be banned from further participation in any discussion by any uninvolved administrator, should he behave disruptively in the discussion; and
may add infoboxes to articles which he creates, provided he does so within a fortnight of the article's creation.
The proposed decision in this case was published on 2 March, four days ahead of the target date. The drafting arbitrators propose to sanction four editors for their part in the dispute, which has included edit-warring, failure to adhere to a neutral point of view, personal attacks, and possible sock-puppetry. At the time of writing, arbitrators are voting unanimously to site-ban two editors, while a package of restrictions for another editor are passing (after modifications) by eight votes to one and the committee is currently divided on whether the fourth editor should be admonished or subject to a similar set of restrictions. Arbitrators have begun voting on a motion to close, and the case is likely to be complete within a day or two of the publication of this week's Signpost.
Other business
American politics: The amendment request regarding Arzel (talk·contribs) discussed in last fortnight's report resulted in a topic ban for Arzel.
Eastern Europe: The committee overturned an out-of-process block ostensibly made in accordance with the discretionary sanctions on Eastern European topics, and advised the administrator responsible to better familiarise himself with the discretionary sanctions process.
Wifione: A request to strike a principle from the Wifione case (which stated that ArbCom had "no mandate to sanction editors for paid editing as it is not prohibited by site policies") failed to gain sufficient support among arbitrators, and was archived.
Toddst1: Last year's Toddst1 case was closed by motion after Toddst1 was desysopped for inactivity. Toddst1 indefinitely blocked himself and left Wikipedia while arbitrators were debating whether or not to accept a case about his administrative actions, as a result of which the case was suspended pending his return or desysop for inactivity.