GeezerVison

Contact us

• About the Foundation
• Movement Resources
• News and Events

Main Help

• Office of CEO
• Advancement
• Communications
• Finance and Administration
• Legal
• Product and Technology
• People

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
• 
  Eliza Blackorby
  Movement Communications Specialist
• 
  Justin Scherer
  Lead UX Designer
• 
  Elliott Etzkorn
  Senior Software Engineer
• 
  Marco Fossati
  Senior Software Engineer
• 
  Matthias Mullie
  Staff Software Engineer
• 
  Kimberly Sarabia
  Senior Software Engineer
• 
  Lauralyn Watson
  Software Engineer

Projects

• Image browsing

• Retention baseline

• Expanded mobile sections

• Mobile table of contents

• Mobile page previews

• Share card

Contact

The Reader Growth Team tracks all engineering related work on our backlog board in Phabricator. To submit an issue, please follow these steps:

1. Search first: Before creating a bug, check Phabricator search to see if the issue's already been reported.
2. 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.
3. File a bug
   1. Use the Phabricator Bug Report template
   2. Tag the task with #reader-growth-team
   3. 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.

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:

1. File a feature request
   1. Use the Phabricator Feature Request template
   2. Tag the task with #reader-growth-team
   3. 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