Wikimedia Audiences/2017-18 Q3 Goals
|This page is currently a draft.|
More information and discussion about changes to this draft on the talk page.
Purpose of this document: Goals for the Wikimedia Audiences department for the third quarter of fiscal year 2017–18 (January–March 2018). The goal setting process owner in each section is the person responsible for coordinating completion of the section, in partnership with the team and relevant stakeholders.
Goals for the Technology department are available on their own page.
Status fields can use the following templates: In progress, To do, Postponed, Done or Partially done
ETA fields may use the initialism EOQ (End of Quarter).
Focused on meeting the needs of active Wikimedia editors for improved, expert-focused curation and moderation tools.
Goal setting process owner: Danny Horn
| Anti-Harassment Tools
(Still a work-in-progress!)
|Increase the confidence of our admins for resolving disputes||Allow wiki administrators to understand the sequence of interactions between two users so they can make an informed decision by adding top-requested features to the Interaction Timeline.||End of February 2018||To do|
|Allow admins to apply appropriate remedies in cases of harassment by implementing more granular types of blocking.||EOQ||To do|
|Keep known bad actors off our wikis||Consult with Wikimedians about shortcomings in MediaWiki’s current blocking functionality.||EOQ||To do|
|Keep known bad actors off our wikis by eliminating workarounds for blocks.||EOQ||To do|
|Reports of harassment are higher quality while less burdensome on the reporter||Begin research and community consultation on English Wikipedia for requirements and direction of the reporting system, for prototyping in Q4 and development in Q1 FY18-19.||EOQ||To do|
|Community Wishlist||Improve very active contributors' productivity||Investigate new Wishlist Survey wishes, and start work on the first two projects||EOQ|
|Rollout support for global preferences (2016 wish #4)||EOQ||In progress|
|Represent both large and small communities||Build a Grant metrics tool that automatically counts and updates important metrics||Community Resources||EOQ||To do|
|Analyze the initial effects of ACTRIAL on English Wikipedia, and publish a report with findings based on the first month of data.||EOQ||To do|
Goal setting process owner: James Forrester
|Editing||Goal 3.1: Improve and consolidate our unified editing platform so that it's great on all devices||Publish performance benchmarks and data collected from updated performance analyses. Begin implementation of performance improvements. Update beta feature to include these performance improvements, and solicit feedback.||
||End Q3||To do|
|Global Collaboration||Goal 5.3.2: Improve structured discussion features for the communities that use them, based on user feedback and prioritising technical debt.||Reduce the technical debt in the structured discussion front end, paving the way for work on major improvements requested by the community, scheduled to begin in Q4||
||End Q3||To do|
|Goal 3.1: Improve and consolidate our unified editing platform so that it's great on all devices||Compact Language Links are enabled by default on Wikipedia in all languages. Percent of clicks out of pageviews doesn’t go down anywhere.||
||End Q3||To do|
|New Editor Experiences||Goal 4.2: Improve, adjust, or create features geared at the needs identified in New Editors research project.||Evaluate recommendations that come out of the New Editors Experience process. Conduct research on the top problems and solutions the New Editors team identifies and create designs. Solidify plans for one or more projects that can be proposed for development.||
||End Q3||To do|
|Parsing||Goal 3.6: Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team||
||End Q3||To do|
|Goal 3.4: Reduce product and technical debt to modernise our tools and technologies, and to make future changes more effective and efficient||Support heredoc-style syntax for templates. The syntax can help editors create better-structured content and support future balanced templates work.||
||End Q4||To do|
Goal setting process owner: Jon Katz
|Web||Continue improving the ways that users can download articles of interest for later consumption||Prepare new rendering service for handoff to Reading Infrastructure||Community Liaisons, TechOps, Release Engineering, Reading Infrastructure||To do|
|Increase learning by lowering the cost of exploration||Deploy Page Previews to English and German Wikipedias||Community Liaisons, Reading Infrastructure, Performance||To do|
|Increase learning for all users by providing articles that load quickly in various settings||Present and discuss proposed changes to the new mobile website with internal stakeholders||Community Liaisons, Reading Infrastructure||To do|
|Multimedia||Designs and prototypes produced in this quarter will provide interactive tools that turn the abstract ideas and promises of the SDoC project into concrete items that WMF staff and Wikimedia community members can play with and reach a better understanding of SDoC project direction and impact.||
|iOS||Support power readers and encourage re-use by supporting Reading Lists, including syncing lists across logged in devices||Port the foldering and sorting capabilities of Reading Lists from Android to replace existing Saved Pages. Allow logged in users to sync their Reading Lists across devices.||Reading Services, Community Liaisons||EOQ||In progress|
|Android||Support power readers and encourage "stickiness" or repeat consumption by improving content freshness.||Explorations around improving content freshness of the feed.||Reading Services, Community Liaisons, TechOps||EOQ||To do|
|Infrastructure||Improve maintainability and code sharing of reading clients by incorporating client code into shared services.||Incorporate shared page library functionality into the Page Content Service. Integrate common CSS into the Page Content Service.||EOQ||To do|
Goal setting process owner: Anne Gomez
|Structured Data on Commons||1.1 It is possible to store structured data within wiki pages, in particular on media file pages on Commons. We will enable the MediaWiki storage layer to correctly store and process structured data elements within wiki pages.||Deploy revision storage service (old schema)
Complete page update service (main slot only)
Complete page update service (multi-slot)
Review / finalize / test DB schema update script(s)
Scope and plan work for WebAPI integration and XML dumps
|MediaWiki Platform with support from Wikidata||EOQ||To do|
|Create wireframes and working prototypes illustrating functionality of SDoC's first feature: structured multilingual descriptive captions.|| - The Commons Community will have its first interactive sample of new versions of Search and File pages integrated with structured data.
- The prototypes and designs will provide interactive tools that turn the abstract ideas and promises of the SDoC project into concrete items that WMF staff and Wikimedia community members can play with and reach a better understanding of SDoC project direction and impact - Internal teams achieve a better understanding of the technical and design challenges involved with full implementation of the proposed features
|Multimedia with support from Community Programs, Technical Collaborations||EOQ||To do|
|Prepare backend infrastructure for structured data search||Search Platfrom with support form Multimedia and Wikidata||EOQ||To do|
|4.2 Develop a better understanding of existing needs for Structured Commons||List of GLAM pain points integrated into programmatic work||Community Programs with supoprt from Multimedia||EOQ||To do|
|4.2 Develop a better understanding of existing needs for Structured Commons||Prepare SDC outreach and affiliate planning sessions for WikimediaCon
Continue building network of GLAMs to feedback on and pilot SDC
|Community Programs||EOQ||To do|
|5.1 The Wikimedia communities, GLAM partners, and developers are fully on board with the Structured Data project. They participate in the different stages of planning and development, and adopt the new features.||Facilitating conversations about designs and prototypes
Prepare for activity during hackathon
|Technical Collaborations||EOQ||To do|
|Wikimedia Technology/Goals/2017-18 Q3#Segment 2: Search integration and exposure||Research with support from Community Programs and Mutlimedia||EOQ||To do|
|New Readers||1.1 Coordinated marketing efforts (campaigns) with launch events in target countries/markets that educate potential readers on what Wikipedia is and the value that it offers, developed in partnership with local networks of advocates. The New Readers team pilots awareness-building efforts that consult, collaborate, and train community members on how to continue strategic marketing initiatives.||[India] Video launches and earn more than 3 million total viewership. Deliver wrap-up report of India campaign.||Communications (lead), Programs, Global Reach, WMMX, Hindi Marketing Committee||EOQ||To do|
|1.2. Rapid Grants focused on raising awareness through community advocacy. The Community Resources team will work with Communications to develop a Rapid Grant application for awareness-building projects. We will facilitate a training and a check-in meeting for a cohort of grantees to build capacity, gather feedback, and support knowledge sharing between awareness advocates.
2.2. The Inspire campaign will address awareness, rather than Offline.
|The Inspire campaign and Rapid Grants round should both be conducted in Q3.
Targets: Inspire campaign generates 150 ideas with 300 participants. The Rapid Grants round has 20 proposals.
|Community Resources (lead), Programs, Communications, Finance||
|2.3. Conduct an environmental scan to better understand the existing ecosystem of solutions for offline support of Wikimedia content;develop an offline strategy; conduct impact assessment for offline solutions in India, Mexico, and Nigeria; prepare and test an approach for distributing offline content in each target country that includes context-specific need/demand for offline solutions, recommendations on relevant offline solutions, and potential partners for distribution of solutions.||Current status: selecting strategy/ies from a set.
In Q3: Design and execute strategic tests for chosen strategy/ies. We will update this goal when we have clarity about the strategies.
|Global Reach (lead), Readers, TBD||EOQ||In progress|
Goal setting process owner: Nirzar Pangarkar
|Audiences Design||Standardise our user interfaces to match user expectation of quality from our products||
||Community Engagement, Operations||EOQ||In progress|
|Audiences Design||Work with New Editor Experiences and New Readers teams to collaboratively define goals and objectives for annual planning.||
||Community Engagement, Contributors, possibly Reading, New Readers, New Editor Experiences||EOQ if not before||In progress|