Wikimedia Product/2018-19 Q3 Goals

From MediaWiki.org
Jump to navigation Jump to search
TriangleArrow-Left.svgQ2 Wikimedia Audiences Goals, FY2018–19, Q3 (January-March) Q4TriangleArrow-Right.svg

Purpose of this document: Goals for the Wikimedia Audiences department for the third quarter of fiscal year 2018–19 (January - March 2019). 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.

Contributors[edit]

Goal setting process owner: Danny Horn

Program Annual Plan Outcome Annual Plan Output Team Quarterly Goal Dependency
Community Wishlist Outcome 1: Productivity and satisfaction Completing wishes from the 2017 survey and investigating new wishes from the 2019 survey Community Tech
  • Deliver first release of Event Metrics tool.
  • Rollout support for SVG Translate tool.
  • Work on data portability
  • Work on “Who wrote that?” tool
  • Analytics, Design, and Design Research help for Event Metrics
  • Legal and Core Platform team's support for Data Portability project
  • WikiWho is a dependency for completing work on "Who wrote that?"
New Content Outcome 1: Progressive Onboarding Output 1.1: Human-to-human help Growth
  • Deploy and iterate on "Focus on help desk" with controlled experiment. Determine whether it increases activation.
  • Deploy an engagement email program and/or beginnings of a newcomer homepage with controlled experiments.
  • Community Relations Specialist
  • Product Analyst
  • QA Engineer
  • Legal for email protocols
  • Approvers in Analytics Engineering, Readers Infrastructure, and Legal for instrumentation plans
Outcome 3: Mobile contribution Output 3.4: Simpler editing on mobile web Editing
  • Build and test high-fidelity prototypes for section editing
  • Build, prototype and deploy VE Loading Screen Overlay to all wikis on mobile
  • Select two non-English Wikis to interface with surrounding toolbar improvements
  • Gather community feedback of toolbar improvements on mobile
  • Community Relations Specialist
  • Product Analyst
  • QA Engineer
  • Design
  • Approvers in Analytics Engineering, Readers Infrastructure, and Legal
  • Readers Web
  • Parsing
  • Services
Outcome 4: Local Language Content Output 4.1: Content translation Language
  • Content Translation 2 becomes the only version for starting new translations.
  • Graduating Content Translation out of beta: improvements required to avoid blockers, and releasing it out of beta for one wiki.
  • Human Perception of Machine Translation : initiate evaluation of qualitative feedback on machine translated content, at scale
    • Editing (technical support on VE editing surface)
    • Research (user research to learn how the tool works for newcomers)
    • Community Relations Specialists (announcements of new version availability and tracking feedback)
    • Partner to share live environment for use in study
Output 4.2: Improve Translate extension & Translatewiki process
  • Improve processes for i18n support to be more fluent by completing key maintenance tasks captured for this area.
Community Health 1: Timely, informed decisions when harassment occurs. Output 1.2: Blocking tools AHT
  • Release partial blocks to 6 willing wikis
  • Ensure that partial blocks are incorporated into policy and practice
  • Investigate applications and prepare business case for device blocking.
  • Analytics
  • Legal
  • MediaWiki core
Output 1.1: Reporting system
  • Research Wikipedia harassment reporting and produce at least one written analysis
  • Conduct consultation with Wikimedians to determine direction of User Reporting System
  • Hold internal Stakeholder’s Summit
  • Determine enhancements to the Interaction Timeline
  • Finalize Impact Measurement framework
  • Learning & Evaluation (Dana)

Design[edit]

Goal setting process owner: Nirzar Pangarkar and Margeigh Novotny

Program Annual Plan Outcome Annual Plan Output Team Quarterly Goal Dependency
Platform evolution/ New Content Better Interfaces/ Advance Mobile Contributions Improving usability and accessibility of Special pages on MobileFrontend Audiences Design
  1. Improve mobile OOUI on Special:Recent Changes
-
New Content Mobile Contribution Research-driven mobile contribution for new contributors Audiences Design
  1. Evaluate the usefulness and usability of Contribution feed for Android App
Android Engineering to deliver the prototype
-- -- -- Audiences Design
  1. Improve WikimediaFoundation official website
Communications, Release Engineering

Programs[edit]

Goal setting process owner: Anne Gomez (New Readers and Structured Data on Commons)

Program Annual Plan Outcome Annual Plan Output Team Quarterly Goal Dependency
New Readers 2. Awareness: More people in target countries/languages know what Wikipedia is. Comms 2: Marketing campaigns to support general awareness, conducted in partnership with community volunteer committee. In previous fiscal year, these have been online video campaigns.

Supporting: Aud PM 2 &3, P&GR 3 &4

P&GR 2 (now Comms): Survey general population in target markets before and after awareness activities.

Comms Complete report about Mexico campaign, including video reach, awareness change, and traffic impact. Make recommendation for extension of campaign based on results.


Details in phab task: task T210795

Audiences analysis, Partnerships & Global Reach
2. Awareness: More people in target countries/languages know what Wikipedia is. Community Resources 1: Complete Inspire campaign / Rapid Grants round that began in previous fiscal year. Support grantees to raise awareness in their communities and use those projects to inform future grant requests.

Community Resources 2: Create Rapid grant application templates and funding guidelines focused on awareness. These templates and guidelines will be developed based on evaluation of and learning from Inspire campaign grants.

Community Resources Complete report about Inspire campaign / Rapid grants. task T210800

Roll out Rapid Grant application templates and funding guidelines for awareness. Publicize new grant type to communities.

task T210801

Satdeep Gill, grantees
4. Retention: More people in target countries/languages find Wikipedia useful and return to it. Aud 3: A series of data-driven product experiments to support better experiences of Wikipedia. [more detail] Audiences Design, Product, Engineering Staff agency and complete product concepts for prototype development. Develop plan for testing and evaluating prototypes. Communications
Structured Data on Commons 1. Commons contributors can edit metadata more easily, in any MediaWiki-supported language Multimedia 1: Release of features that enable structured data editing and addition on the file page and as part of the media upload process. Multimedia 1. Launch file captions in January

2. Launch depicts only

3. Launch support for other statements

Wikidata, MediaWiki Platform, Search Platform
Comm Rel 1: Facilitate community conversations and feedback requests around editing features, uploading features, and multilingual support. Community Relations Announce and communicate ongoing releases, design proposals and solicit targeted feedback from relevant stakeholder groups. Multimedia
Comm Rel 2: Ensure community involvement and satisfaction with development process. Facilitate community conversations with communities and share feedback with Multimedia team. Multimedia
GLAM 0: Facilitate community conversations and feedback requests around editing features, uploading features, and multilingual support. GLAM GLAM-Wiki stakeholders (Wikimedians and interested parties in the GLAM sector) are informed and involved in the SDC releases in Q3. Multimedia
3. GLAM institutions have more reliable and less challenging workflows for sharing media files and metadata on Wikimedia Commons. GLAM 2: Structured Data on Commons and its value for GLAMs is tested and demonstrated with at least 8 experimental GLAM pilot projects. GLAM GLAM pilot project organizers agree to shared commitments for SDC pilots. The first pilots are kicked off, dependent on deploying features to add, edit, and search for depicts and other statements by the end of the quarter. Multimedia
4. Developers who create and maintain key Commons tools, including volunteer developers, can transition those tools to work with structured data on Commons. Multimedia 10: Extend and release updated API(s) for developers to use. Multimedia Ensure the label API works, and shut off statements until statements are deployed.

Readers[edit]

Goal setting process owner: Jon Katz

Program Annual Plan Outcome Annual Plan Output Team Quarterly Goal Dependency
New Content 3. Mobile Contribution 3.3 Research-driven mobile contribution for new contributors Android User test prototype edit action feed and leverage research to make improvements. Release V1 feed. Reading infrastructure

Multimedia

Community relations

Research

3.1: Contribution tools on mobile web via an existing mediawiki skin Web
  • Build and deploy initial advanced contributions navigation functionality to test wikis (Spanish, Arabic, Indonesian)
  • Build Special Pages prototypes
Community Relations
3.2: Mobile for existing contributors iOS
  • Ship improvements to editing navigation to support small focused edit tasks: find-in-page, long press menu to open element for editing and wiki-text "code" folding to hide long/distracting blocks of mark-up.
Community Relations
Search Engine Optimization Outcome 2: Improvement and Analysis 2.1: Interventions implemented Web
  • Publish report on the effects of the sameAs schema property, sitemaps, and canonical urls on traffic for search engines
  • Assuming positive report results, deploy the sameAs schema property, sitemaps, and canonical urls to a wider audience
WMDE, Performance, Community Relations
Better Use of Data Outcome 2: Define Responsibilities Output 2.1: Measurement expectations Product Analytics
  • Train Product Managers and Engineers on selecting the right metrics & day-to-day working with data
Web, Multimedia, Editing, Growth, Language, Parsing, Android, iOS, Anti-harassment, Community tech
Output 2.2: Data Stewardship Product Analytics
  • Build a data dictionary with core metrics and annual plan metrics defined
Outcome 3: Data collection Output 3.1: Instrumentation Infrastructure
  • Document existing and best practices for instrumentation from Audiences teams on Mediawiki.org
  • Compile and prioritize a list of tasks to fix issues and improve instrumentation implementation in a Phabricator board
Output 3.2: Controlled experiment (A/B test) capabilities Infrastructure
  • Document existing and best practices for implementing and running controlled experiments from Audiences teams on Mediawiki.org
  • Compile and prioritize a list of tasks to fix issues and improve instrumentation implementation in a Phabricator board
Outcome 4: Deliverable Creation Output 4.1: Report stewardship Product Analytics
  • Ensure 5 key reports are added to the report portal
Analytics Engineering
Output 4.3: Wiki segmentation Product Analytics
  • Draft of static segmentation model for Wikis
Design Strategy
Platform Evolution CDP Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs Output 2.7: Refactor presentation layer away from business logic code in MediaWiki Web Make Minerva Independent of Mobilefrontend
Output 2.5: Parser Unification Work Parsing Kick off porting of Parsoid to PHP Core Platform
Output 2.5: Parser Unification Work Parsing Complete Q2 goal: Production use of Parsoid Language Converter for read views of phase 2A and 2B languages