Readers/Web/Team
< Readers
Jump to navigation
Jump to search
Reading Web
Responsible for the reading experience of Wikimedia sites
|
Disseminate educational content under a free license or in the public domain effectively and globally.
The Readers Web team focuses on engineering efforts around the experiences for readers of the websites for the various Wikimedia projects.
This page and its subpages are intended to document the team, its various roles/responsibilities, and generally be a repository of articles of team documentation.
Team[edit]
Daniel Cipoletti Engineering Manager
Jon Robson
Staff Engineer & Tech LeadStephen Niedzielski
Senior EngineerEdward Tadros
Quality Assurance Analyst (contractor)Jan Drewniak
UX EngineerJazmin Tanner Technical Program Manager
Projects[edit]
Team documentation[edit]
Process[edit]
- Roles and responsibilities
- Software component responsibilities
- Phabricator information (boards & workflows)
- Deployment procedures/guidelines
- Story estimation
- SOP for Reading Web Phabricator Maintenance
- What to do with an UBN
- Quantitative testing
- How do I become a reading web volunteer?
Meeting minutes[edit]
- Quarterly review meetings:
- Retrospectives
Communication[edit]
- Bluejeans (videoconferencing) @ https://bluejeans.com/463688296//webrtc
- Should Bluejeans fail, we use Google Meet.
Onboarding[edit]
- Team norms
- Team values
- Various wikis of Wikimedia, and how to log in to them
- Reading/Component_responsibility
Onboarding for developers[edit]
- What is MobileFrontend and Minerva ?
- Reading/Web/Getting setup with code review
- Working with Vagrant
- Performance
- Development cycle
- Coding conventions documentation (style, organization, commit message guidelines, etc)
- Caching - see phab:T124954 (Varnish) and ResourceLoader (client code).
Community engagement[edit]
- Recommendations for mobile friendly articles
- Working with editors to get templates fixed
- Graphs of phabricator/irc usage
Software development and testing[edit]
- QA process
- Articles we test on
- Devices and browsers we test on
- Reading/Web/QUnit test guidelines
- Reading/Web/Working with legacy code
- List of server log files known to Wikipedia project
Starting a new project[edit]
- Setting up instances on wmflabs.org
- Setting up a Gerrit repository (general notes)
- Review queue - for getting new projects in production
- Hosting prototypes
Continuous Integration[edit]
Deploying, debugging and releasing[edit]
- Pushing production code from beta to stable
- Reading/Web/Setting up instances on wmflabs.org
- Release process
- How to deploy code
- Deploy gotchas
- SSH configuration notes
- Requesting shell access
- Video showing deployment procedures
- Reading/Web/Debugging with WebClientError
Analytics[edit]
- EventLogging
- Accessing Hive and accessing page view data
- Access data about our projects (page views, editors, edits, change in bytes) using wikistats
- Need to know what % of traffic is Opera Mini? Look no further - Turnilo or User agent breakdowns.
- Using Turnilo
Other[edit]
- Reporting an incident
- Sunsetting a project (killing a project)
- Icinga (network monitoring)