Responsible for the reading experience of Wikimedia sites
Disseminate educational content under a free license or in the public domain effectively and globally.
The 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.
Quality Assurance Analyst
Please note: these are currently intended for internal WMF staff.
You can join our online Meet room meet.google.com/zpj-gmkx-cau. Our goal is to openly discuss our work, and to answer any of your questions. We would like to invite anyone interested in our projects, current and future work, and in particular Desktop Improvements.
Please plan on attending if:
- You have questions for our team
- You would like to collaborate with us more closely in the future
- You want to discuss plans and strategies for our desktop and mobile sites in the future
If you plan on attending, feel free to add your notes to the agenda - this will help us prepare for your questions ahead of time. We are planning to host office hours twice a quarter.
- 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?
- Submitting a request for the team
- Bluejeans (videoconferencing) @ https://bluejeans.com/463688296//webrtc
- Should Bluejeans fail, we use Google Meet.
- Team norms
- Team values
- Various wikis of Wikimedia, and how to log in to them
Onboarding for developers
- What is MobileFrontend and Minerva ?
- Reading/Web/Getting setup with code review
- Working with Vagrant
- Development cycle
- Coding conventions documentation (style, organization, commit message guidelines, etc)
- Caching - see phab:T124954 (Varnish) and ResourceLoader (client code).
- Recommendations for mobile friendly articles
- Working with editors to get templates fixed
- Graphs of phabricator/irc usage
Software development and testing
- 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
- Setting up instances on wmflabs.org
- Setting up a Gerrit repository (general notes)
- Review queue - for getting new projects in production
- Hosting prototypes
Deploying, debugging and releasing
- Pushing production code from beta to stable
- Setting up alerts with grafana
- 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
- 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