Wikipedia:Wikipedia Signpost/Single/2011-08-22

After eleven moves, name for islands now under arbitration

This was another active week for the

Senkaku Islands case opened

Background

The Senkaku Islands dispute—over a group of five islands in the East China Sea administered by Japan since 1972 but claimed by China—is itself the subject of dispute here on Wikipedia along with its parent article Senkaku Islands.

The figurehead point of controversy appears to be the name, Senkaku Islands, which, as the Japanese name, has been alleged as supportive of the Japanese side in the dispute. As a result, a handful of editors have been pushing for the Chinese name instead, and many arguing for the anglicized The Pinnacle Islands as a correct, NPOV descriptor. The point has seen many discussions, an RFC, and mediation. Since 2005 the article on the Senkaku Islands has been moved eleven times, but is now back where it started. To what extent the article should acknowledge the other names of the islands has also been a point of edit warring, with the current text including significant coverage. Comparisons to the dispute of the name of the Liancourt Rocks—islands claimed by both Japan and South Korea—have been drawn. In that dispute, an anglicized name was chosen over the Korean or Japanese names, although the dominant consensus has consistently been that "Senkaku Islands" is the name most commonly used in English publications for the islands. Edit warring in the body of the two articles has also been significant, with many users feeling that the article endorses the Japanese claim to the islands.

The dispute has seen established users in good standing on both sides of the issue.

Request

The request was opened on August 13 by Qwyrxian who wrote that (s)he has "come to believe that until the behavioral problems are corrected, we will be unable to make constructive progress on the article content". Eleven parties gave statements and the case was accepted unanimously by eight arbitrators with one recusal. Arbitrator Coren wrote in his acceptance that the Senkaku Islands dispute is "a relatively simple case where it's likely consensus could be reached if everyone behaved and where Arbcom could help by making sure everybody does."

Arbitration

Since its opening on August 17 it has seen little activity so far;

No drafting arbitrator has been assigned yet.

Abortion case proceeds

The case, which centers on the naming of abortion-related articles and related behavioral issues, proceeded into its second week. Three more uses have presented evidence this week:

• NYyankees51 and Haymaker
  of being such accounts, writing that "most people have an opinion about abortion, and those opinions don't disqualify anyone from editing the topic. However, I think in each of these cases there is clear evidence that the editor's personal views on abortion have overwhelmed their ability to edit within policy on the topic." Anythingyouwant and NYyankees51 have disputed MastCell's allegations.
• SarekOfVulcan presented a few diffs of the general behavior that he felt was inhibiting progress.
• NuclearWarfare noted that "This case is simply an amalgamation of two cases: the dispute over the naming of the pro-choice / pro-life articles and the lead sentence of abortion, as well as some smaller matters" and then gave a lengthy narrative of his work on the lead sentence of Abortion (where he reports that after extensive research he concluded that using the word death in the lead was not NPOV). He also pleaded for strict action from the committee, writing that he "doesn't know what will help solve this dispute in a reasonable fashion, but [he] guarantee[s] that a simple 'everyone go play nice and remember to reread WP:OR and WP:NPOV' will not suffice."

In the workshop

Cirt and Jayen466 case proceeds

The case involves allegations of non-neutral editing by Cirt and also allegations against Jayen466 that he has stalked and harassed Cirt. Three more users presented evidence this week,

• Prioryman presented evidence against Jayen466 in support of Cirt.
• Delicious carbuncle wrote in criticism of Cirt.
• Cirt, apologizing for the presenting evidence so late (citing real-life circumstances), said that he was "astonished by the length and intensity of complaints" and that "I’ve reflected on my past behavior and I realize that these complaints have some validity" but countered that he had resolved the issues writing "This case, and the previous RfC and RFAR, have been a learning experience for me, and I’ve already stated at those forums that I’ve withdrawn from the areas in which my editing has been at issue. I undertake to edit in good faith to benefit the project, and to be sensitive to any complaints that might arise concerning my editing." Cirt endorsed proposals by Cbrick77 for a topic ban against himself, covering "new religious movements or their members, and political BLPs, broadly construed", as well as an interaction ban between himself and Jayen466.

Manipulation of BLPs case proceeds

The case, which was broken off from the Cirt and Jayen466 case to be a somewhat unusual investigation of BLP policy, proceeds into its third week. The sluggish addition of actual evidence submitted remarked upon last week appears to have ameliorated. This week nearly twice as much evidence was presented as in the first two weeks of the case combined.

• Wnt wrote "it is difficult to give evidence for such a very wide-ranging proceeding" then went on to challenge the prevailing notion of the case arguing that the real issue is not "diminish[ing] or increas[ing] particular reputations" but that it is instead "almost purely a Wikipolitical conflict between deletionists and inclusionists", alleging that "one side makes use of every policy, including BLP, to oppose what they don't like, while the other defends Wikipedia's breadth of coverage." He suggests that "it should be made clear that Wikipedia policies apply to removal of text just as much as addition", for example that "removing mention of open homosexuality from someone's page because you personally think it's a 'negative' thing violates WP:NPOV"—such removal runs quite contrary to current BLP best practices.
• FuFoFuEd wrote that he was being "misrepresented as a champion of BLP violations" and countered various assertions.
• Tryptofish championed two recommendations: that a guideline to deal with subtle search engine optimization editing be developed, and that the committee establish clear guidelines related to arbitrator recusal, citing SlimVirgin's request in June that Shell Kinney recuse herself during a previous request for arbitration, which Shell Kinney refused, as evidence that clearer guidelines are needed.
• Waalkes, a new user with only 36 edits, accused Will Beback and SlimVirgin of BLP violations on Lyndon LaRouche and LaRouche movement, starting off by noting that "BLP policy discourages the use of insinuation and allegations against living persons attributed to anonymous sources", then accusing of them of using such sources.
• DracoEssentialis presented the articles Kimberly Kagan, Sheila Widnall, Jed Babbin, Michael Eric Dyson, and David Hackworth as examples of where BLP policy was failing.
• Prioryman accused Delicious carbuncle of disrupting a BLP to make a point—for which he was given a topic ban earlier this year, although it has since been overturned—and using Wikipedia Review for off-wiki hounding in a campaign against Cirt.
• Count Iblis has thrown up the section headings "The BLP policy leads to censorship and should therefore be abolished" and "Implementing the BLP policy provokes edit warring", promising evidence at a later date.

The workshop saw little new this week, a few very pointed questions—with the subtext that the case was being unfair to Cirt—for Cla68 from Jehochman and another pointed question from Prioryman for Delicious Carbuncle listing a post of his on Wikipedia Review and asking him to explain. Also a Mathsci posted two standard "proposed principles" adapted from previous ArbCom cases on Decorum and Conduct on arbitration pages, urging civility.

Committee resolves to channel comments into votes

Last week John Vandenberg noted a trend where abstention votes were being increasingly used to give vote-like opinions, which he noted was "causing elements of arbitration cases and motions to technically pass or fail while the abstain section contains many arbitrator votes consisting of comments heavily leaning for or against". He stated that "The Arbitration Committee needs to review its use of abstention in order to ensure that the committee position on an issue is clear and that they have the requisite support to provide legitimacy for that position." This has been the first time the issue has surfaced around ARBCOM, and the need for a motion was questioned. "Well, I probably would have gone for discussion before writing motions, but meh" wrote Risker, however John Vanderberg's proposal did lead somewhere; after going through six drafts, the motion passed, creating a new "comments" section in addition to the support, oppose, and abstain sections, and advising arbitrators that "abstention votes as a vehicle for comments [... are] not recommended". The motion also guarded against slacktavism, stating "an arbitrator who posts a comment is also expected to vote on the proposal".

Reader comments

2011-08-22

Engineering report, sprint, and more testers needed

Contribute  —  

Share this

•  E-mail
•  Facebook
•  Twitter
•  LinkedIn
•  Reddit
•  Digg

By Jarry1250

July Engineering Report published

The Wikimedia Foundation's Engineering Report for July was published last week on the Wikimedia Techblog and on the MediaWiki wiki, giving an overview of all Foundation-sponsored technical operations in that month. Many of the projects mentioned have been covered in The Signpost, including the deployment of the MoodBar, ArticleFeedback and WikiLove extensions. Among those yet to have received significant coverage but that were highlighted in the report were "the successful implementation of a MySQL-based parser cache on Wikimedia wikis" and work on a "Wikimedia Report Card 2.0".

There was good news for performance, too. Seventy-four new servers were purchased to increase the capacity of our Apache cluster to be installed this month, whilst the reliability of database dumps also settled down after a rocky June. The work on the parser cache was also successful, improving the hit rate (the percentage of requests which do not force the server to regenerate the page from scratch) to 80%, from 30%. On the software side, Roan Kattouw and Timo Tijhof worked on delivering "global gadgets and a gadget manager". According to the report, the "back-end for loading gadgets remotely from another wiki" is now in a workable state, as is an "inventory" of available gadgets.

The HipHop deployment, AcademicAccess, App-level monitoring, and Configuration management projects were "mostly on hold" in July, as was work on LiquidThreads 3.0. Documentation of the status of projects came under more scrutiny in July under the guidance of Guillaume Paumier, now the Foundation's Technical Communications Manager. Paumier "continued to create, update, clean up and organize the project documentation pages for most engineering activities" during July, according to the report, which is itself authored by him.

July also saw the arrival of Jeff Green (Operations Engineer for Special Projects), Ben Hartshorne and contractor Daniel Zahn (Operations Engineers) and Ian Baker (Software Developer). At the same time, however, Chief Technology Officer Danese Cooper and Code Maintenance Engineer Priyanka Dhanda left the Wikimedia Foundation.

Fundraiser engineering sprints in progress

Also published this week was a detailed insight into the present fundraising team, who are responsible for making sure Wikimedia websites have the capability to maximise the fundraising potential that the annual drive afford them. It is currently led by Arthur Richards and also includes two developers, an operations engineer, a data analyst, and a general business analyst. The team for this year's fundraiser has now been working on that fundraiser since approximately May, according to the post.

From a technical point of view, Richards stressed that good "code hygiene" was a must, including writing unit tests for all the code they produce in two-week code "sprints". The sprints focus around specific goals which the team can track using the proprietary software

Mingle

. "While we would much prefer to use an open-source solution, we settled on this proprietary tool as it much more closely meets our needs than any of the others we explored" wrote Richards. Examples of sprint targets include improving the banner tracking system to allow for results to be filtered. This allows the team to improve the banner range available to maximise the number of visitors who see the value in donating to Wikimedia. This year's campaign will again feature localised banners and user stories.

In brief

Not all fixes may have gone live to WMF sites at the time of writing; some may not be scheduled to go live for many weeks.

How you can help

Test Kiwix

Try out the latest beta of Kiwix, the offline Wikipedia reader. Then leave feedback for its development team.

• The role of the "Platform Engineering" team at the WMF was explained in a blog post by its head, Rob Lanphier. He writes that broadly speaking the team is split up into three subgroups: the MediaWiki Core subgroup; the Technical Liaison and Developer Relations subgroup (TL;DR); and the Data Analytics subgroup, all of which are currently hiring.
• Among the
  Requests for Bot Approval currently requiring community discussion is a request to create between
  five and ten thousand stubs on certain animal species.
• Director Mobile and Special Projects Tomasz Finc invited testers for two projects within his remit: the second round of mobile testing and the latest beta version of Kiwix, the offline Wikipedia reader that was selected for Wikimedia developer attention.
• After a discussion on the wikitech-l mailing list, it looks unlikely that MediaWiki will fix a date for dropping PHP 5.2.x support so soon after stopping support of platforms running PHP versions 5.1.x (which it dropped in version 1.17, released in June this year). Such a move would allow use of those features of the languages only introduced in PHP 5.3, but would prevent the installation of future MediaWiki versions on older systems.
• During a special bug triage session targeted at those bugs affecting mobile devices, a number of problems and feature requests were analysed. According to bugmeister Mark Hershberger, his department "hope[s] to do one of these mobile triages every month and, for future ones it would be awesome if we could have Kindles, iPads, and maybe even Nooks as well as BlackBerries, Androids, iPhones and even Nokia phones" (wikitech-l mailing list).
• Developer Andrew Garrett has detailed the technical lessons that could be learned from the recent referendum-related mass emailing to potential voters, with 750,000 outgoing emails.
• Diederik van Liere wrote on wikitech-l about the efforts of himself and other Wikimedia-sponsored researchers to harness the power of
  terabytes, are the most efficient way of grabbing large amounts of a Wikipedia's (or other project's) history at one time. In related news, he also published his suggestions
  about how the dumps could be made more reuser-friendly.
• The main page of the Wikimedia Commons showed intermittent errors due to heavy server load. The problem was only relieved when more rigorous caching was reinforced, prompting content elsewhere to become slightly out-of-date (bug #30428).
  
  Reader comments
  

If articles have been updated, you may need to refresh the single-page edition.

Get the latest headlines on your user page — just add {{Signpost-subscription}}.

Home

About

Archives

Newsroom

Subscribe

Suggestions