Reading/Web/Chore list

Checklist
The checklist can be considered to be in priority order. Do not worry if the whole checklist is not completed.

Check if browser tests are failing

 * Are there any browser test failures?
 * If so, has the issue has recurred for at least 2 builds?
 * If so, is there a bug open?
 * Is the bug a deployment blocker?
 * Note: If a branch cut is about to happen or happening (Monday/Tuesday) extra care is needed in this checklist item.
 * Find "Blockers:" in https://wikitech.wikimedia.org/wiki/Deployments#Near-term to identify the Phabricator task for deployment blockers and add as a subtask if necessary.

Review the Web Dashboard
https://phabricator.wikimedia.org/dashboard/view/125/
 * Are there tasks in the Triage section that need to be tagged with the backlog?
 * Are there tasks that need to be escalated to "Unbreak Now!" status and pulled into the sprint?

Review #mobile
https://phabricator.wikimedia.org/tag/mobile/

Sometimes users incorrectly tag our bugs...
 * Are there any new tasks tagged mobile in the "needs triage" column?
 * Tasks that are not reading web specific should be moved to triaged (tag with relevant teams if you know)
 * Tasks that are reading web specific should be tagged with "reading web backlog" and relevant components.

Review the current sprint

 * Is there unplanned sprint work?
 * Are there any tasks that still need the Unplanned Sprint Work tag?

Review the next sprint (Reading Web Backlog Upcoming column)

 * Review the cards currently lined up for Upcoming.
 * Is anything not clear in the description of the card?
 * Is there information missing?
 * Are there assets missing?
 * If you were to work on the task right now would you be able to?
 * Add comments with those questions and move to the needs analysis column of the web dashboard.
 * Feel free to add a reassuring token if you want to note that the card is looking in good shape :-)

Check the performance dashboards (devs only)

 * Take a look at the mobile performance dashboard and consider:
 * Is there anything suspicious about the beta cluster in comparison to production?
 * If so, then does it correlate with other performance dashboards based on Real User Monitoring (RUM), e.g. https://grafana.wikimedia.org/dashboard/db/navigation-timing.
 * Are there any obviously related entries in the Server Admin Log?
 * Consider the differences between the beta and production Barack Obama articles
 * The idea of these graphs is to get a sense of what the next train push will lead to e.g. will it increase bytes or decrease bytes?
 * Have the HTML and image sizes deviated considerably? If so re-import the article from production.
 * How do JS/CSS differ? These values should be very very close. If they are not, it probably warrants investigation.
 * Is the next deploy likely to reduce bytes shipped, result in no change or increase them?
 * If there is any difference between the values - debug.
 * Have any new extensions been deployed or changed that might have led to an increase?
 * Did we do any refactoring that may have led to a decrease?
 * Did a new feature we've been working on it increase our payload?
 * Is it possible MediaWiki.Mobile.js or MediaWiki.Mobile.css may need updating on the beta cluster?
 * Do the same for the Page Previews Perf dashboard.

Check the logs (devs only)

 * Take a look at the Logstash dashboard. Is there a log entry that's new and trending or indicative of a breakage?

Check if there are patches from volunteers

 * One place to look may be "Tasks you can help us review" in the Web Dashboard.
 * Escalate to team code review etc. as necessary.

Review the Reading Web Backlog
https://phabricator.wikimedia.org/tag/reading-web-backlog/
 * Are there any tasks assigned to you in the "Needs Analysis" column? Can you do anything now to help them become actionable?
 * Are there tasks in "To Triage" that need priorities and/or can be moved to "Needs Analysis" or "Tracking"?
 * Are there hidden Priority=Low/Lowest tasks in the "To Triage" column? (Tip: use the filter link on the lefthand menu of the board).
 * Are there tasks in "Needs Analysis" that can be moved along? Even one or two can make a dent in grooming. :)
 * As part of grooming Needs Analysis, assign a team member to the tasks that require their attention, and attend to those tasks with your username attached.
 * Are there tasks that haven't been poked (old) in a while? Poke them!

Admin

 * Check if meetings are scheduled for days off in the current week.
 * If so, notify the team so that they can adjust accordingly.

Order

 * 1) Stephen
 * 2) Olga
 * 3) Piotr
 * 4) Jon R
 * 5) Baha
 * 6) Joaquin
 * 7) Nirzar

Everyone chips in on Fridays.

Status Update
The team member responsible for their time frame should email their progress via the daily standup email threads.

Links

 * [http://chimeces.com/wikimedia-phab-html-links/?t=%23%23%23%20Check%20if%20browser%20tests%20are%20failing%0A%0A-%20%20%20Are%20there%20any%20%5Bbrowser%20test%20failures%5D%3F%0A%20%20%20%20-%20%20%20If%20so%2C%20has%20the%20issue%20has%20recurred%20for%20at%20least%202%20builds%3F%0A%20%20%20%20%20%20%20%20-%20%20%20If%20so%2C%20is%20there%20a%20bug%20open%3F%0A%20%20%20%20%20%20%20%20-%20%20%20Is%20the%20bug%20a%20deployment%20blocker%3F%0A%20%20%20%20%20%20%20%20%20%20%20%20-%20%20%20Note%3A%20If%20a%20branch%20cut%20is%20about%20to%20happen%20or%20happening%20(Monday%2FTuesday)%20extra%20care%20is%20needed%20in%20this%20checklist%20item.%0A%20%20%20%20%20%20%20%20%20%20%20%20-%20%20%20Find%20%E2%80%9CBlockers%3A%E2%80%9D%20in%20%3Chttps%3A%2F%2Fwikitech.wikimedia.org%2Fwiki%2FDeployments%23Near-term%3E%20to%20identify%20the%20Phabricator%20task%20for%20deployment%20blockers%20and%20add%20as%20a%20subtask%20if%20necessary.%0A%0A%23%23%23%20Review%20the%20Web%20Dashboard%0A%0A%3Chttps%3A%2F%2Fphabricator.wikimedia.org%2Fdashboard%2Fview%2F125%2F%3E%0A%0A-%20%20%20Are%20there%20tasks%20in%20the%20Triage%20section%20that%20need%20to%20be%20tagged%20with%20the%20backlog%3F%0A-%20%20%20Are%20there%20tasks%20that%20need%20to%20be%20escalated%20to%20%E2%80%9CUnbreak%20Now!%E2%80%9D%20status%20and%20pulled%20into%20the%20sprint%3F%0A%0A%23%23%23%20Review%20the%20current%20sprint%0A%0A-%20%20%20Are%20there%20tasks%20in%20%E2%80%9CNeeds%20Analysis%E2%80%9D%20that%20need%20discussion%20or%20estimation%20with%20the%20team%3F%0A-%20%20%20Is%20there%20unplanned%20sprint%20work%3F%0A%20%20%20%20-%20%20%20Are%20there%20any%20tasks%20that%20still%20need%20the%20%5BUnplanned%20Sprint%20Work%5D%20tag%3F%0A%0A%23%23%23%20Review%20the%20next%20sprint%20(Reading%20Web%20Backlog%20Upcoming%20column)%0A%0A-%20%20%20Review%20the%20cards%20currently%20lined%20up%20for%20***Upcoming***.%0A%20%20%20%20-%20%20%20Is%20anything%20not%20clear%20in%20the%20description%20of%20the%20card%3F%0A%20%20%20%20-%20%20%20Is%20there%20information%20missing%3F%0A%20%20%20%20-%20%20%20Are%20there%20assets%20missing%3F%0A%20%20%20%20-%20%20%20If%20you%20were%20to%20work%20on%20the%20task%20right%20now%20would%20you%20be%20able%20to%3F%0A-%20%20%20Add%20comments%20with%20those%20questions%20and%20move%20to%20the%20needs%20analysis%20column%20of%20the%20web%20dashboard.%0A-%20%20%20Feel%20free%20to%20add%20a%20reassuring%20token%20if%20you%20want%20to%20note%20that%20the%20card%20is%20looking%20in%20good%20shape%20%3A-)%0A%0A%23%23%23%20Check%20the%20performance%20dashboards%20(devs%20only)%0A%0A-%20%20%20Take%20a%20look%20at%20the%20%5Bmobile%20performance%20dashboard%5D%20and%20consider%3A%0A%20%20%20%20-%20%20%20Is%20there%20anything%20suspicious%20about%20the%20beta%20cluster%20in%20comparison%20to%20production%3F%0A%20%20%20%20-%20%20%20If%20so%2C%20then%20does%20it%20correlate%20with%20other%20performance%20dashboards%20based%20on%20Real%20User%20Monitoring%20(RUM)%2C%20e.g.%20%3Chttps%3A%2F%2Fgrafana.wikimedia.org%2Fdashboard%2Fdb%2Fnavigation-timing%3E.%0A%20%20%20%20-%20%20%20Are%20there%20any%20obviously%20related%20entries%20in%20%5Bthe%20Server%20Admin%20Log%5D%3F%0A-%20%20%20Do%20the%20same%20for%20the%20%5BPage%20Previews%20Perf%20dashboard%5D.%0A%0A%23%23%23%20Check%20the%20logs%20(devs%20only)%0A%0A-%20%20%20Take%20a%20look%20at%20the%20%5BLogstash%20dashboard%5D.%20Is%20there%20a%20log%20entry%20that%27s%20new%20and%20trending%20or%20indicative%20of%20a%20breakage%3F%0A%0A%23%23%23%20Check%20if%20there%20are%20patches%20from%20volunteers%0A%0A-%20%20%20One%20place%20to%20look%20may%20be%20%E2%80%9CTasks%20you%20can%20help%20us%20review%E2%80%9D%20in%20the%20%5BWeb%20Dashboard%5D.%0A-%20%20%20Escalate%20to%20team%20code%20review%20etc.%20as%20necessary.%0A%0A%23%23%23%20Review%20the%20Reading%20Web%20Backlog%0A%0A%3Chttps%3A%2F%2Fphabricator.wikimedia.org%2Ftag%2Freading-web-backlog%2F%3E%0A%0A-%20%20%20Are%20there%20any%20tasks%20assigned%20to%20you%20in%20the%20%E2%80%9CNeeds%20Analysis%E2%80%9D%20column%3F%20Can%20you%20do%20anything%20now%20to%20help%20them%20become%20actionable%3F%0A-%20%20%20Are%20there%20tasks%20in%20%E2%80%9CTo%20Triage%E2%80%9D%20that%20need%20priorities%20and%2F%0A%0A%20%20%5Bbrowser%20test%20failures%5D%3A%20https%3A%2F%2Fintegration.wikimedia.org%2Fci%2Fview%2FReading-Web%2F%0A%20%20%5BUnplanned%20Sprint%20Work%5D%3A%20https%3A%2F%2Fphabricator.wikimedia.org%2Fproject%2Fprofile%2F1318%2F%0A%20%20%5Bmobile%20performance%20dashboard%5D%3A%20https%3A%2F%2Fgrafana.wikimedia.org%2Fdashboard%2Fdb%2Fmobile-2g%0A%20%20%5Bthe%20Server%20Admin%20Log%5D%3A%20labsconsole%3AServer_Admin_Log%20%22wikilink%22%0A%20%20%5BPage%20Previews%20Perf%20dashboard%5D%3A%20https%3A%2F%2Fgrafana.wikimedia.org%2Fdashboard%2Fdb%2Freading-web-page-previews%0A%20%20%5BLogstash%20dashboard%5D%3A%20https%3A%2F%2Flogstash.wikimedia.org%2Fapp%2Fkibana%23%2Fdashboard%2FReading-Web%0A%20%20%5BWeb%20Dashboard%5D%3A%20phab%3Adashboard%2Fview%2F125%2F%20%22wikilink%22 Markdown editor template] (Prettifies links to phab tasks and gerrit patches)