Readers/Reader Growth - MediaWiki
Jump to content
From mediawiki.org
Readers
About the Foundation
Movement Resources
News and Events
Office of CEO
Advancement
Communications
Finance and Administration
Legal
Product and Technology
People
We build and maintain software focused on ways of learning and engagement for new and casual readers.
Wikimedia Foundation projects
Reader Growth
Focusing on new ways of learning and engagement.
Group:
Product & Technology
Team members:
#Team members
Backlog:
The Reader Growth team focuses on new ways of learning and engagement. We aim to invest in creating innovative experiences that leverage new technologies and formats. This includes tools and features that enable users to browse and discover content more intuitively, contextualize and frame knowledge in novel ways, and engage with visual, audio, and other multimedia formats.
Back to Readers
Team members
Sherry Yang
Lead Product Manager
Hilary Swan
Engineering Manager
Jon Robson
Principal Software Engineer
Roan Kattouw
Principal Software Engineer
Eliza Blackorby
Movement Communications Specialist
Justin Scherer
Lead UX Designer
Eric Gardner
Senior Software Engineer, tech lead
Marco Fossati
Senior Software Engineer
Matthias Mullie
Staff Software Engineer
Kimberly Sarabia
Senior Software Engineer
Brooke Vibber
Staff Software Architect
Lauralyn Watson
Software Engineer
Projects
Image browsing
Retention baseline
Expanded mobile sections
Mobile table of contents
Mobile page previews
Contact
Reporting an issue
edit
The Reader Growth Team tracks all engineering related work on our
backlog board
in Phabricator. To submit an issue, please follow these steps:
Search first:
Before creating a bug, check
Phabricator search
to see if the issue's already been reported.
Confirm ownership:
Make sure the issue falls under the Reader Growth team's stewardship or team mandate. Check the
Developers/Maintainers
page if it's regarding a specific extension or skin.
File a bug
Use the Phabricator
Bug Report template
Tag the task with
#reader-growth-team
Add any relevant component tags (e.g.
#vector-2022
#minervaNeue
If you have access to Wikimedia's internal Slack, please post in the
#talk-to-reader-growth
channel after creating the task to get direct feedback.
Requesting a feature
edit
Before submitting a feature request, understand that the Wikimedia Foundation undergoes a rigorous
Annual Planning Process
to determine which features to pursue in any given year. Your feature request is most likely to be accepted if it falls within an existing annual plan initiative.
First, consider adding your feature request to the
Community Wishlist
to have it more formally integrated into our planning process.
Alternatively, you may submit a task to request a feature as well:
File a feature request
Use the Phabricator
Feature Request template
Tag the task with
#reader-growth-team
Add any relevant component tags (e.g.
#vector-2022
#minervaNeue
If you have access to Wikimedia's internal Slack, please post in the
#talk-to-reader-growth
channel to get feedback from our product manager.
If you don't have access to Phabricator, see
phabricator/Help#Creating your account
for detailed instructions on how to create one.
Team documentation
Reader Growth Testing Strategy
ReaderExperiments
Maintenance Levels and Responsibilities
Decommissioned Projects
Subpages of Reader Growth
Code Review Norms
Decommissioned Projects
Expanded Mobile Sections
Expanded Mobile Sections/en
Image Browsing
Image Browsing/en
Image Browsing/fr
Maintenance Levels and Responsibilities
Mobile Table of Contents
Mobile Table of Contents/en
Mobile Table of Contents/ja
Mobile Table of Contents/pt-br
Mobile page previews
Reader Growth Testing Strategy
Retention Baseline
Share Card
Retrieved from "
Readers/Reader Growth
Add topic