Wikipedia:Wikipedia Signpost/2010-09-06/From the editors Wikipedia:Wikipedia Signpost/2010-09-06/Traffic report Wikipedia:Wikipedia Signpost/2010-09-06/In the media
As the MediaWiki software behind Wikimedia sites grows and matures, it becomes more complicated to manage and to oversee major changes. As such, the Foundation has begun to bring in more paid contractors and employees (though not many for such a large and popular set of websites), each with their own project. The first in a soon-to-be-monthly series of posts outlining these projects was posted this week on the Wikimedia Techblog. The projects that receive some sort of paid support rather than being left entirely to the community to develop include the following. This is not complete list and the items are numbered only for convenience:
Further information on each, including their current status, is available on the original post. Updates on each should be more accessible in future.
Developer Trevor Pascal announced on Twitter that his work on a new ResourceLoader to improve loading speeds on Wikimedia sites had progressed and could now be expected "soon". He went into more detail on the Wikitech-l mailing list, explaining the main features to expect:
“ |
|
” |
He gave the example of a page that would previously require 35 requests (totalling 30kB) now taking just one of 9.4kB. Gains for users on older hardware or mobile devices might be improved even more, he said, since they were being served whole scripts they could do nothing with.
We continue a series of articles about this year's Google Summer of Code (GSoC) with student Jeroen De Dauw, who describes his project to develop a system for managing the extensions installed on a wiki (read full blog post):
“ | My initial proposal was to create an awesome extension management platform for MediaWiki that would allow for functionality similar to what you have in the WordPress admin panel ... I started with porting the filesystem abstraction classes from WordPress, which are needed for doing any upgrade or installation operations that include changes to the codebase. (The current MediaWiki installer can do upgrades, but only to the database.) I created a new extension called Deployment, where I put in this code ... but it turned out that doing filesystem upgrades securely is not an easy task, so after finishing the port, I stopped work on this temproarily. I then poked somewhat at the new MediaWiki installer [due to ship with MediaWiki version 1.17], which is a complete rewrite of the current installer. I made some minor improvements there, and split the Installer class, which held core installer functionality, into a more generic Installer class and a CoreInstaller. This allows for creating an ExtensionInstaller that uses the same base code ...
I decided to create the package repository, from which MediaWiki and extensions could get updates and new extensions, from scratch, and started working on another extension, titled Distribution, for this purpose. I merged it together with a rewritten version of the MWReleases extension written by Chad, which already had core update detection functionality. After the Distribution APIs where working decently I started work on the Special pages in Distribution that would serve as the equivalent of the WordPress admin panel. As I had put off the configuration work, and also the file-system manipulation for the initial version, this came down to simply listing currently installed software, update detection and browsing through extensions available in the repository ...
Although some very basic functionality is working, quite some work still needs to be done to get this to the WordPress-awesomeness level. |
” |
In terms of Wikimedia sites, developments in this field could improve the turnaround time for extension deployment, but the significant gains will be for spreading extensions to and from other MediaWiki-based sites.
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.
danese at wikimedia dot org
for an invite (Wikitech-l mailing list).Wikipedia:Wikipedia Signpost/2010-09-06/Essay Wikipedia:Wikipedia Signpost/2010-09-06/Opinion
The full analysis of the Pending changes trial has been published. The data are an elaboration on an earlier preliminary analysis (see previous story). The full table is here, and a compacted version focusing on anon revert percentages is here. The data ranges widely; the two most common percentages are 100 and 0 percent.
Pending changes is a new form of page protection that makes use of the FlaggedRevs extension, allowing editing as usual but giving visiting IPs only the most recent "approved" version of the protected pages, as decided by trusted editors. Flagged revisions has been praised by supporters as an alternative to semiprotection, opening up editing to IPs while still curbing vandalism; on the other hand, it has been criticized as a contradiction to Wikipedia's open editing model.
A straw poll on the future of Pending changes has concluded. In the light of what many consider a confusing poll, several users have posted analyses aiming to clarify the consensus.
The Wikimedia Foundation Report for July 2010 has been published, following a lapse in the publication of monthly reports (the April, May and June reports are being worked on). Wikification and other improvement of the version on Meta are invited. Apart from many items previously covered in the Signpost, the report shares some highlights from statistics about the usage of the book tool (which allows readers to compile Wikipedia articles into PDF files and order bound paper copies of them), provided by PediaPress: "From May through July, PediaPress shipped 1,671 printed books to 981 buyers in 46 countries. 38% of books were sold to Germany and 28% to the United States. The feature was also used to generate approximately 85,000 PDF files per day." The report says that the WMF's legal team has "been in contact with both the Apple and Android app stores to ask their assistance in policing trademark-infringing apps" and was separately negotiating with Apple about the Wikimedia trademark use in Apple products. The Foundation contracted an attorney specialized in charities, and "confirmed that there are ongoing structural issues, particularly in Europe, with transferring charitable funds to WMF."
Last week, two blogs independently examined the choice of topics featured on the English Wikipedia's main page. "Deeply Problematic", a blog about "feminism, and stuff", examined which persons were mentioned in the various sections of the main page on ten different dates during the past year (using the Wayback machine), finding that 130 of them were men and only 15 were women. Wikipedian Utcursch asked whether there is "Too much bad news on Wikipedia’s main page?" He examined the content of the "In the news" section during August, when it had featured 45 unique news stories. Around 40% of them belonged "to the 'bad news' category (disasters, accidents, wars and terrorist attacks)". In addition, he shared the informal impression that bad news stays longer on the main page because "the new updates are continuously posted, as the casualties keep increasing over a period of time". Utcursch, who is from India, also examined the geographical distribution of the ITN entries, finding "that the 'In the news' section does a decent job of covering stories from all across the world". - In related news, a Twitter feed announcing India-related topics from the "Did You Know" (DYK) section has recently been set up (DYKIndia); the underlying software can be adapted to other topic areas too (WikipediaDYKTweeter).
Wikipedia:Wikipedia Signpost/2010-09-06/Serendipity Wikipedia:Wikipedia Signpost/2010-09-06/Op-ed Wikipedia:Wikipedia Signpost/2010-09-06/In focus
The Arbitration Committee opened no new cases, leaving one open.
This case resulted from the merging of several Arbitration requests on the same topic into a single case, and the failure of a related request for comment to make headway. Innovations have been introduced for this case, including special rules of conduct that were put in place at the start. However, the handling of the case has been criticized by some participants; for example, although the evidence and workshop pages were closed for an extended period, no proposals were posted on the proposed decision page and participants were prevented from further discussing their case on the case pages (see earlier Signpost coverage).
The proposed decision, drafted by Newyorkbrad, Risker, and Rlevse, sparked a large quantity of unstructured discussion, much of it comprising concerns about the proposed decision (see earlier Signpost coverage). A number of users, including participants and arbitrator Carcharoth, have made the discussion more structured, but the quantity of discussion has continued to increase significantly. Arbitrators made further modifications to the proposed decision this week; drafter Rlevse said that arbitrators are trying to complete the proposed decision before the date of this report. However, Rlevse will not be voting on the decision as he has marked himself as inactive for the case.
Several users were not satisfied with this and attempted to seek clarification about the desysop but arbitrator Carcharoth then collapsed these comments as well, and modified the mentions of 'emergency procedures' to 'interim desysop procedures'. A comment by arbitrator Newyorkbrad was left at the bottom of the discussion, which stated:I will request that people refrain from speculating on this matter, nor should any other action being done about the account without Committee approval...this is simply a temporary measure until the matter is cleared up.
There are aspects of this situation that may not be suited for discussion on-wiki. (I say this without criticism of those who have commented, given that the posted announcement created a discussion section; someone should probably have posted here preemptively.) We will appreciate everyone's understanding and consideration in this matter.
The Committee endorsed all candidates that were being actively considered in August for appointment to CheckUser and Oversight positions (see earlier Signpost coverage). Earlier in the week, the following permissions were granted to the following users:
Note: for the reasons reported earlier, MBisanz and Bastique will not be granted Oversight permissions until November 2010 and December 2010, respectively. However, The Signpost notes that these candidates were also successful. Wikipedia:Wikipedia Signpost/2010-09-06/Humour