Web Team/Bookmarks

Our mission: "Disseminate educational content under a free license or in the public domain effectively and globally."

The Reading 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

 * Max Binder - Scrum Master


 * Nick Ray - Engineer


 * Piotr Miazga - Engineer


 * Jon Robson - Senior Engineer & Tech Lead


 * Sam Smith - Engineering Manager




 * Stephen Niedzielski - Engineer


 * Olga Vasileva - Product Owner


 * Anthony Borba - Exploratory QA


 * Stephen Niedzielski - Engineer


 * Jan Drewniak - UX Engineer


 * Alex Hollender - User Experience Designer

Projects

 * A list of our current and ongoing projects
 * daily chores

Process

 * 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

Meeting minutes

 * Quarterly review meetings:
 * April 2015
 * January 2015
 * earlier
 * Retrospectives

Communication

 * Google Hangouts
 * Should Google Hangouts fail, we will fall back to https://bluejeans.com/3591815659/browser (MBinder's personal link) given its reliability (Chrome or Chromium only). This will remain until at least June 2017, when OIT will review the BJ contract. If all else fails, the team will fall back to appear.in given its simplicity.


 * Team IRC Channel

Onboarding

 * Newbies guide
 * Mobile beta


 * Team norms
 * Team values
 * Various wikis of Wikimedia, and how to log in to them
 * Reading/Component_responsibility

Onboarding for developers

 * Reading/Web/Getting setup with code review
 * Working with Vagrant
 * Performance
 * Development cycle
 * Coding conventions documentation (style, organization, commit message guidelines, etc)
 * Caching - see T124954 (Varnish) and ResourceLoader (client code).


 * QA - how to use browser tests
 * Wikimedia Design Style Guide

Community engagement

 * Recommendations for mobile friendly articles
 * Working with editors to get templates fixed

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 projects

 * Setting up instances on wmflabs.org
 * Setting up a Gerrit repository (general notes)
 * Experience notes & followup
 * Review queue - for getting new projects in production
 * Hosting prototypes

Continuous Integration

 * Entry points
 * Popups Gerrit autorebase tool

Deploying and releasing

 * Pushing production code from beta to stable
 * Release process
 * How to deploy code
 * SSH configuration notes
 * Requesting shell access
 * Video showing deployment procedures

Analytics

 * 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

 * Reporting an incident
 * Sunsetting a project (killing a project)
 * Icinga (network monitoring)

Research

 * Prototyping


 * Mexico Readers Research

Releases
Release timeline

Archived Notes

 * Reading Web 2015 - Q1 Feature stabilization
 * Q1 Planning, 2014-2015