Wikipedia:Wikipedia Signpost/2012-08-06/From the editors Wikipedia:Wikipedia Signpost/2012-08-06/Traffic report Wikipedia:Wikipedia Signpost/2012-08-06/In the media
“ | In July 2012:
|
” |
—Engineering metrics, Wikimedia blog |
The Wikimedia Foundation's engineering report for July 2012 was published this week on the Wikimedia Techblog and on the MediaWiki wiki, giving an overview of all Foundation-sponsored technical operations in that month (as well as brief coverage of progress on Wikimedia Deutschland's Wikidata project). All three headline items in the report have already been covered in the Signpost: Wikimania and the pre-Wikimania hackathon; the launch of new software to power a refreshed Wikimedia report card (named in the report as Limn); and the ongoing deployment of version 5 of the Article Feedback tool.
Among other developments noted in the report was work on what is now being called the "Page Curation" project, a package including Special:NewPagesFeed and an opt-in "curation toolbar" that recreates much of Twinkle's functionality as well as a number of other mechanisms for helping editors deal with page creations. In July, the report says, developers "completed development of all key curation tools and are now adding a couple final features ... [and] now plan to pre-release Page Creation on the English Wikipedia in mid-August — with a full release in September 2012". Elsewhere, the first Wikipedia Engineering Meetup was set for August 15. Held in the Wikimedia Foundation's home city of San Francisco, the meetups are an attempt to engage local programmers, of which there are many. The meetups are due to be held every two months, the report noted.
There was also mixed news with regard to site performance (see also related stories below). Performance Engineer Asher Feldman hit gold with an upgraded version of the parser cache server cutting the 90th percentile response time from 53.6ms to 7.17ms, and the 99th percentile response time from 185.3ms to 17.1ms, meaning that 99% of all page requests going through the cache are now served and sent back to the user in 17 thousandths of a second or less. Lead Platform Architect Tim Starling had less success, however, with his project investigating the possibility of optimising PHP processing at the bytecode level, which "looked like a promising direction for performance optimization". Unfortunately, despite a significant "theoretical gain ... actual performance [seemed] disappointing", causing the project to be suspended indefinitely.
Developers are closing in on a first deployment of Wikidata, it became clear this week. Phase one of the project, aiming to provide a central repository of interwiki links, is expected to launch on the Hungarian Wikipedia within weeks (wikitech-l mailing list).
Confirming that all major work on the project, which is split across four extensions, is complete, the past week and the next couple will be dominated by work getting code reviewed, Project Director Denny Vrandečić suggested in his post on the developers' mailing list, picking out seven actionable items that will need to be negotiated ahead of a first deployment.
After the Hungarian Wikipedia, where community members have already agreed to trial the extension, the extension is likely to be deployed to either the Italian Wikipedia or the Hebrew Wikipedia, where its right-to-left support can be scrutinised; next up will be the English Wikipedia and finally all other Wikipedias. Deployment of phase 2 with centralised infobox-style data is not expected until the end of the year, if not earlier next.
Not all fixes may have gone live to WMF sites at the time of writing; some may not be scheduled to go live for several weeks.
{{PAGESINCATEGORY}}
, allowing filtering to just subcategories, pages or files (bug #14237); and a fix that allows communities to set their own default block expiry time (bug #32178).Wikipedia:Wikipedia Signpost/2012-08-06/Essay Wikipedia:Wikipedia Signpost/2012-08-06/Opinion
On August 1, the Funds Dissemination Committee (FDC) portal was launched on Meta. The FDC will implement the Wikimedia movement's new grant-orientated finance structure in accordance with the WMF board's recent resolutions (Signpost coverage). As a volunteer committee, the FDC will make recommendations to the WMF board on a $11.4 million budget for 2012–13.
Movement organizations can apply for FDC funds when they meet transparency criteria and have a successful WMF grant track record of at least two years or take part in the annual fundraiser payment processing (detailed criteria catalogue). To date, only two entities meet these criteria – the foundation itself and Wikimedia Philippines – and can submit grant application proposals. Sixteen chapters are eligible in principle but have yet to make transparent all required reports on financial conduct and grants. Twenty-two chapters, most of them recently established – are ineligible under the criteria, in particular the two-year track-record requirement.
Non-FDC funds can be requested through the WMF grant program. The foundation will make its own non-core programs subject to the FDC's volunteer review and recommendation process and will request FDC funds for its own grant program. This program budget, advised in turn by the volunteers of the Grant Advisory Committee (GAC), will allocate $400k in 2012–13 to support organizations and individuals that are not eligible to apply for FDC funds. Other resources available to individual Wikimedia volunteers are the participation support program, which has a wide non-Wikimedia centered scope, and the Wikimania-focused scholarship program, currently under review (Signpost coverage).
The early start of the FDC portal on August 1 drew some criticism due to the not-yet-concluded corrections of key documents such as the application form, and continuing work on other parts of the portal. To improve the community participation process in these efforts, the FDC staff has set up a central input page on Meta, where community members can leave their notes and get responses by the staff.
Volunteers interested in serving on the committee can submit (self-)nominations on Meta in accordance with the FDC membership criteria until 23:59 UTC August 15. The community can ask the candidates questions.
The WMF board will appoint the seven inaugural FDC members and an ombudsperson (nomination page) later this quarter and FDC eligible entities can submit their application proposals for funds until October 1. Subsequent FDC members will be partly community-elected (5) or WMF board appointed (4) and the membership will therefore be extended to 9 members.
Wikipedia:Wikipedia Signpost/2012-08-06/Serendipity
As Senior Designer of the Wikimedia Foundation, it's part of my job to stimulate conversation about the future of Wikimedia's user experiences. This op-ed is first and foremost intended to do so, although it's not an exact roadmap with deliverables and deadlines. If you'd like to see our goals for the year, please take a look at the 2012–13 goals.
At this year's Wikimania, I gave a talk entitled The Athena Project: Wikipedia in 2015 (slides). The talk broadly outlined several ideas the foundation is exploring for planned features, user interface changes, and workflow improvements. We expect that many of these changes will be welcomed, while others will be controversial.
During the question-and-answer period, I was asked whether people should think of Athena as a skin, a project, or something else. I responded, "You should think of Athena as a kick in the head" – because that's exactly what it's supposed to be: a radical and bold re-examination of some of our sacred cows when it comes to the interface.
I'm certain many people are asking, "Why do we need a change? Why is this important?" Simply put: the software is a barrier and it is dragging you down.
There's no need to throw up graphs about editor decline or toss around numbers about participation and gender imbalance here – you've either seen them and agree that something needs to be done, or you've dismissed them. Let's skip those arguments and talk about why these changes will benefit the editor community at large and not just a hypothetical group of newbies.
If we can attract and retain new contributors we'll reduce the overall workload for everyone. How quickly will backlogs disappear if we add even 5,000 new editors who can easily get into the mix?
I've spent the past year studying the many workflows used on Wikipedia, speaking with hundreds of Wikipedians. I've watched screencasts of editors doing page patrol that filled me with a sense of agony and sympathy for those doing the work. I've watched so many people – people who could be productive, good Wikipedians – quit in frustration simply because using Wikipedia is too hard.
What's the takeaway from all of this? The software (or lack of it) is a barrier. It doesn't do the right things, it makes simple things difficult, and it hides features and information that should be front and center. Did you know that no two page patrollers do the work the same way? That's because the software is so bad that everyone has to make up their own way to work around it and get things done.
We need to revisit these workflows. We need to make it easier to read, contribute, and curate. With better tools come streamlined processes and thus less work.
Increasing the size of our community will naturally adjust the voice of the community. I don't think anyone believes we should be writing only from one or two points of view – featured articles are so good precisely because they are edited by so many. Bringing on more skilled editors will create a more accurate encyclopedia. It means that the voice of Wikipedia is more powerful by virtue of being diverse. The sum of our parts becomes greater than the whole.
Let's face it: our interface would feel right at home in the year 2002. However, we find ourselves rapidly moving towards 2013. Our editors and readers deserve a modern interface with modern tools. The Visual Editor is one project to help make this a reality. Here are several others:
The fear that Wikipedia will turn into a social networking site is one I hear fairly often. However, I don't see that as a real threat: there's a distinction between becoming a social network and having modern software to support the building of an encyclopedia.
Wikis are collaborative software engines, which makes them social software – and social networks – by definition. What makes us different from other social networks is our purpose. Sites like Facebook and Twitter are motivated by making connections between people, but we are motivated by producing something: the greatest encyclopedia ever to exist. To do that, we have to connect people with tasks they are interested in.
For us, features like Echo, Flow, and Global Profile will be used to make collaboration easier and faster. They'll do this by tying interest graphs together. Imagine a day when the software will detect a "Needs sources" tag on World War II, and members of WikiProject Military History can be automatically notified in real time if they want, without having to go check their watchlist?
Imagine a world in which every single human being can freely share in the sum of all knowledge.
What a powerful idea that is. The Mission (and I always capitalize it) is what's important here. We are here to educate, to open minds, to make the world a better place. I believe in this so much that I had it tattooed on my arm.
Indirectly, our work will do magnificent things. By educating the people of the world, we are sparking the growth of a new era in thinking. We speak to genius-level intellects who have no access to formal education. Maybe one of them will cure cancer, or discover ways for faster-than-light travel, or develop new ways of philosophical thinking that change the world? We can change the course of history. Right here. Today.
We do this by showcasing our content. By emphasising it, by curating it, by editing it. By being proud of it.
To do this, we must make the software easier to use. We must make it easier to collaborate, to read, to contribute, to curate.
Which means we have to change. Sadly, change is difficult and often painful. The good news is that after a time of chrysalis, we'll emerge as something better.
It's time to become a butterfly. Wikipedia:Wikipedia Signpost/2012-08-06/In focus
The closure of Fæ two weeks ago marked the closure of the last open case before the Committee. This has only happened on three occasions: in 2009, 2010 and in May of this year. At the time of writing, the Committee has no requests for arbitration before it.
Arbitration cases do not form all of the Committee's workload, however, as two requests for clarification and one request for amendment are being discussed.
Arbitrator Kirill Lokshin proposed a motion for a procedure on the alteration of an editor's previous username(s) in arbitration decisions to reflect their name change(s). Any instances appearing within the:
A significant body of arbitrators have opposed the motion labelling the motion's stipulations "dogmatic and inflexible" and "administration creep". Arbitrator Elen of the Roads proposed making it a policy that clerks update records upon being made aware of a name change. Concerns about such a move would then be raised to the Committee accordingly. The suggested change to the motion also requires the editor-in-question to inform the Committee beforehand.
The Devil's Advocate initiated an amendment request for the controversial Race and intelligence case. The request calls for the amendment of review remedies 1.1, 6.1 and 7.1.
Amendment 1 concerns 6.1 and 7.1; calls for the modification of SightWatcher's and TrevelyanL85A2's indefinite omni-namespace edit and discussion ban from Race and intelligence topics, including participation in discussions concerning topic-editor conduct, to be a standard topic ban from Race and intelligence-related edits (broadly construed) with a clearly-defined route for appeal of the sanction.
Amendment 2 concerns 1.1; calls for the modification of Mathsci's admonishment for engaging in battlefield conduct to include an explicit warning that further battleground conduct (towards editors) related to the topic will be "cause for discretionary sanctions." Wikipedia:Wikipedia Signpost/2012-08-06/Humour