Wikipedia:Wikipedia Signpost/2012-02-20/From the editors Wikipedia:Wikipedia Signpost/2012-02-20/Traffic report Wikipedia:Wikipedia Signpost/2012-02-20/In the media
Over three days in the middle of the week, MediaWiki 1.19 went live to its first twelve (Wikimedia) wikis (a spread of different types of project including Wikisources, two Wikipedias, a Wikiquote, a Wikiversity and Meta). As expected, the deployments shed light on a number of issues with the release, including the appearance of a number of bugs that needed fixing before the planned rollout to Wikimedia Commons on February 21 (an up-to-date list of such bugs and their statuses is available).
For example, developers are currently wrestling with a number of JavaScript-related issues, including a problem (filed as bug #34409) which resulted in certain core variables not being defined. Since other scripts relied upon these variables (mw.user.options and mw.user.tokens), end users quickly reported problems with their watchlists and user gadgets. The problems were exacerbated by a fault with the deprecated secure.wikimedia.org server (wikitech-l mailing list), which caused some scripts to fail simply of their own accord and by the kind of dependency problem developers were already expecting (example). Although developers looking at the issue were initially puzzled by the intermittent nature of the main problem, there is now a growing consensus that most of the problems will resolve themselves as various caches get invalidated. Unfortunately, problems with the release were not confined to user scripting; indeed, quite a number of short-term fixes were needed to stop the update crashing servers due to its unexpectedly high memory footprint, whilst bugs relating to merging accounts and the recent changes IRC feed are still outstanding (also wikitech-l: 1, 2, 3)
Nonetheless, the deployment team is still expected to be able to keep to the original deployment timetable, which sees the final Wikimedia wikis upgraded during the early hours of March 2. Indeed, there are significant incentives to make sure that it does: the main Git switchover has already been scheduled to begin on March 3 (see below), making any overrun inherently problematic.
WMF developers confirmed this week that the canonical repository for the core MediaWiki software will be changed from the current Subversion repository to a new Git repository over the course of March 3–4 (wikitech-l mailing list). The long awaited move will therefore immediately follow the deployment of MediaWiki 1.19 to Wikimedia wikis, but precede its full release to external wikis.
The relatively tight schedule will head-off the risk that code review is allowed to get out of hand between the deployment (for which the number of unreviewed revisions was driven down to zero) and the switchover (for which the number of unreviewed revisions needs to be at zero). It also prevents the potential for any overlap between old-style "post-commit" review and new style "pre-commit" review, and hence the possibility of the same code being reviewed twice. Staff took the opportunity this week to explain the reasoning behind the switchover on the Wikimedia blog, and on the wikitech-l mailing list there was a discussion of the elements of the new system most likely to take developers by surprise, including references to several bugs. A separate thread discussed instructions for those who did not develop MediaWiki, but were still reliant on the old repository for keeping their installations of MediaWiki on the bleeding edge.
Extensions running on Wikimedia wikis will be transferred to Git immediately after the core MediaWiki code. Non-WMF extensions in the shared Wikimedia.org SVN repository can either take up the offer of a transfer, or elect to sort out their own hosting arrangements. Developers suggest that extension maintainers are likely to have around 12 months to make the decision before the old repository goes read-only.
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.
Wikipedia:Wikipedia Signpost/2012-02-20/Essay Wikipedia:Wikipedia Signpost/2012-02-20/Opinion
In the wake of heated discussions concerning a possible restructuring of the way in which the Wikimedia Foundation and Wikimedia chapters handle the raising and spending of donor funds (see Signpost special report), staff at the Foundation released a memo in an attempt to reiterate the argument for abandoning the current role of chapters in processing payments (and pocketing some of them) during the annual fundraiser, in favour of a central committee made up of an international group of volunteers. As with previous communications from the Foundation's board of trustees, the memo ignited much criticism, with many chapter-affiliated editors critiquing its factual accuracy and impartiality at length. The discussions took centre stage at the 2012 Finance meeting, which was held in Paris over the weekend and which is expected to further spur the ongoing debate.
Terry Chay has been hired by the Wikimedia Foundation to fill the position of Director of Features Engineering. Chay holds an M.S. in Physics from the University of Illinois at Urbana–Champaign, and is a former member of Automattic, the company behind WordPress, and in that capacity helped in "implementing an A/B testing framework, improving the blog domain name registration process...[and] creating better support mechanisms for first-time users". Before that he was an engineering manager and software architect for several start-ups and tech companies between 1999 and 2009, such as Plaxo and Tagged. He has attended the O'Reilly Open Source Convention, contributing to the PHP talks there, and given over 25 public talks about web development.
As the new Director of Features Engineering, "Terry will be responsible for helping ensure the success of some of our key feature teams: the visual editor team, the editor engagement team (including the article feedback project), and the fundraising engineering team." His hiring also means that the current occupant of the position, Alolita Sharma, will be moving into another directorial role, although what this will entail exactly remains to be seen.
Wikipedia:Wikipedia Signpost/2012-02-20/Serendipity Wikipedia:Wikipedia Signpost/2012-02-20/Op-ed Wikipedia:Wikipedia Signpost/2012-02-20/In focus
The Arbitration Committee opened no new cases this week, but closed one case, leaving two open.
On 20 February, a motion to close reached four net votes, triggering the closure of the Civility enforcement case. This case was initially opened due to the actions of several administrators in relation to an editor who was blocked over perceived incivility. That editor, Malleus Fatuorum, will be subject to an RFA talk page ban. Specifically, he is banned from "any page whose prefix begins with Wikipedia talk:Requests for Adminship", but is not prevented from !voting on RFAs, according to the Arbitration Committee's proposed decision. Further, arbitrators voted to admonish him over "repeatedly personalizing disputes and engaging in uncivil conduct, personal attacks, and disruptive conduct". In approving this sanction, the Committee rejected a proposal to ban him on a 2–8 vote.
The decision includes a provision to desysop Hawkeye7. The basis for this is the finding that Hawkeye7 has engaged in "wheel warring and conduct unbecoming of an administrator". The Committee also voted to admonish administrators Thumperward "for conduct unbecoming an administrator, and for failing to adequately explain his actions when requested by the community and Arbitration Committee" and John for "reversing another administrator's actions while said actions were under review through community discussion."
A general reminder to all editors was passed "to engage in discussion in a way that will neither disrupt nor lower the quality of such discourse. Personal attacks, profanity, inappropriate use of humour, and other uncivil conduct that leads to a breakdown in discussion can prevent the formation of a valid consensus. Blocks or other restrictions may be used to address repeated or particularly severe disruption of this nature, in order to foster a collaborative environment within the community as a whole."
This warning is directed at conduct that deteriorates the quality of discussions, reminding all editors that uncivil conduct can be a factor in the breaking down of consensus forming, and that blocks or other restrictions may be used in the event of repeated disruption to ensure the collaborative environment of Wikipedia is maintained.
This case was brought to the Committee by an editor to appeal a ban that was imposed by Jimbo Wales. The proposed decision was posted today by drafter Roger Davies. Proposals range from vacating TimidGuy's site ban to the desysop and ban of the accusing administrator. A great deal of the proposals discuss the Conflict of Interest guideline and its interaction with anti-harassment policies. Committee voting on these proposals is expected to continue into the week.
This case was opened to review alleged disruptive editing on the Manual of Style and other pages to do with article naming. Today, the workshop phase closed with a total of eight submissions from involved parties. Suggestions ranged from guidance on Wikipedia policies to claims of specific incidents of disruptive editing. Arbitrators AGK, David Fuchs, and Casliber will draft a proposed decision which is due to be posted by next Sunday (26 February).
Wikipedia:Wikipedia Signpost/2012-02-20/Humour
