Web Team/Bookmarks

This page and its subpages are intended to be a repository of team documentation.

To learn about the role, projects, and members of the team, as well as to check how to contact the team, go to Reading/Web.

Process

• Task creation: Submitting a request for the team
• Working with us
• Daily chores
• Release manager
• Phabricator backlog

• Roles and responsibilities
• Software component responsibilities
• Phabricator information (boards & workflows)
• Deployment procedures/guidelines
• Story estimation
• Chore results
• What to do with an UBN
• Quantitative testing

Onboarding

• Newbies guide
• Mobile beta

• Team norms
• Team values
• Various wikis of Wikimedia, and how to log in to them
• Developers/Maintainers. See table for extensions/skins maintained by web team.

Onboarding for developers

• What is MobileFrontend and Minerva ?
• Reading/Web/Getting setup with code review
• Working with Vagrant
• Readers/Web/Dev_notes
• Performance
• Development cycle
• Coding conventions documentation (style, organization, commit message guidelines, etc)
• Caching - see phab: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
• 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
• Readers/Web/Building features with cached HTML in mind
• Releasing libraries

Design

• Logo internationalization

Starting a new project

• 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, debugging and releasing

• Pushing production code from beta to stable
• JavaScript client error alerts
• Setting up alerts with grafana
• Our grafana boards for monitoring production code
• 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
• Running maintenance scripts

Analytics

• Readers/Web/Instrumentation Overview and A/B tests
• EventLogging
• Accessing Hive and accessing page view data
• https://hue.wikimedia.org/
• 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
• Click tracking
  • A bookmarklet exists for exploring EventLogging data:
    • javascript:mw.loader.load('https://en.wikipedia.beta.wmflabs.org/w/index.php?title=MediaWiki:EventLoggingHints.js&action=raw&ctype=text/javascript%27)

Other

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

Security

• https://office.wikimedia.org/wiki/Security/Training/Tech_Basics
• https://wikitech.wikimedia.org/wiki/How_to_deploy_code#Security_patches

Research

• Prototyping
• Mexico Readers Research

Releases

• Release timeline

Archived Notes

• Reading Web 2015 - Q1 Feature stabilization
• Q1 Planning, 2014-2015
• Quarterly review meetings:
  • April 2015
  • January 2015
  • earlier