WMF cuts budget for 2016-17 as scope tightens: The Signpost analyzes the WMF's revised annual plan
The Wikimedia Foundation has published its revised annual plan for the 2016–17 financial year (July–June), which has been finalised for board approval after a month-long community consultation on Meta. Responding to a challenging fundraising environment, the organisation is cutting its planned expenses for the first time after more than a decade of unabated growth—from US$65m in 2015–16 to $63m in 2016–17. While the organisation has a track record of underspending actual expenses, the reduction of about 3% represents a shift in its planning. The change includes a slight reduction in planned headcount and adjustments to budgets such as that for grantmaking. Among identified risks, the ongoing Executive Director transition and relatively high rates of staff departure over the past months stand out as significant challenges alongside structural issues like the decline in readership, the increasingly challenging fundraising environment, and the well-being of the volunteer communities.
The centrepiece of the annual plan is "reach"—the WMF's ability to effectively reach our readers and distribute the community's free knowledge to them. This priority emerged from the strategy draft and from related community consultation in early 2016. There are a number of highlights. Field research in Nigeria and India will help WMF Tech's Reading Department to launch a new reader interface for one of the targeted regions—readership in Mexico have been studied in 2015–16. WMF Product will continue to improve the editing interface by upgrading tools such as VisualEditor (which is expected to reach mobile), and expanding the content translation tool. Community Tech will continue to work through the top 10 of the community wishlist, which includes improving diff comparison, numerical sorting in categories, cross-wiki talkpage communication, and the plagiarism detection bot; and the pageview stats tool; the creation of a central global repository for templates, and an integrated cross-wiki watchlist.
The Foundation is rolling out a new process to work with the communities in researching and building better software products. How best to integrate community voices in product decision-making has traditionally been controversial, leading to repeated stand-offs. In cooperation with Wikimedia Germany, Wikidata—which now has the third-largest community after those of the English Wikipedia and Commons—will be more deeply integrated into key aspects of all projects, such as search and infoboxes. WMF Technology is investing in better analytics and research capabilities, APIs, Tool Labs (for community developers working on tools and bots that help users maintain and use wikis), privacy protection, and site reliability.
Following the debates on how to address harassment in 2015–16, the staff aim to build online learning modules on the subject, including one on how to improve the safety of offline community meetings. The Foundation is also restructuring its grantmaking schemes and is resuming support for GLAM volunteers with a staff facilitator. The Communications Department will be enhancing the movement's reach by researching and interacting with new audiences, especially on social media, while the Advancement department (formerly Fundraising) is expanding Wikipedia Zero and new types of partnerships to foster readership. Advancement aims to raise $5m for the Foundation's newly established endowment on top of the $63m target for funding regular operations. WMF Legal will continue its input into the NSA lawsuit.
Discuss this story
@Mdennis (WMF): regarding online courses for the training platform for functionaries, are there any public examples (perhaps with identifying details omitted) of safety problems which we most urgently need to address? Can we please have Twine/Twee versions of such online courses for review? (Please see Entweedle for creation of Twee from Twine.) Can we also please have online Twine/Twee courses about how to edit well? I'm sure you could get the community to make some of those if you asked. Please see [1], [2], [3], and [4] for context. EllenCT (talk) 14:55, 6 June 2016 (UTC)[reply]
Is there any way to get a list of all the individual WMF salaries to calculate a Gini coefficient from year to year? Based on a recent discussion at Jimbo's page I would be interested to see whether there is increasing economic inequality overall within the ranks of WMF employees. Wnt (talk) 03:45, 6 June 2016 (UTC)[reply]
- Super short version: Product makes the things folks use to donate, edit, read, and find, while Technology supports that work and makes sure things don't blow up. :) There's a list of teams within each on MediaWiki.org. CKoerner (WMF) (talk) 14:46, 9 June 2016 (UTC)[reply]
"Wikidata—which now has the third-largest community after those of the English Wikipedia and Commons" - I wonder... how, exactly, is the size of Wikidata's community measured? What's the definition of "community"? After all, many edits on Wikidata are made by people who never actively visit Wikidata, through automated processes. For example, if you move an article in Wikipedia, this may result in a Wikidata edit attributed to your account such as this one - one doesn't need to visit Wikidata or even know of the project... So, if Wikidata's community size would simply be measured by the number of account names showing up as contributors to Wikidata, that would be misleading in my opinion. The actual, active community of Wikidata in the sense of people who participate in project discussions etc. looks rather small to me. Gestumblindi (talk) 03:13, 9 June 2016 (UTC)[reply]