Wikimedia Release Engineering Team/Checkin archive/20160125

= 2016-01-25 =

Vacations/Important dates
How to do it: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Time_off
 * Jan 29- Feb 1st - FOSDEM - Antoine. Travel Friday afternoon, back monday Noon (CET)
 * Feb 3rd - core narrative annual plan due
 * Feb 15: US HOLIDAY - President's Day
 * March 4th - strategic narrative annual plan due
 * March 11th - draft Q4 (April 1st - June 30th) goals due
 * March 31st - April 3rd : Hackathon in Israel
 * April 1st - Q4 goals published
 * May 9-Mid June-ish?: Greg - paternity leave - exact dates TBD
 * May 17-(?): Dan - paternity leave :D
 * Late May - draft Q1 (July 1st - Sept 30th) due
 * May 30: US HOLIDAY - Memorial Day
 * June (mid): Chad - EDC
 * June 22nd - 28th : Wikimania in Italy
 * July 1st - Q1 goals published
 * July 1st – Annual Plan, Budget, Risks Document and FAQ are posted
 * August: France holiday - because french. :)
 * January 2017 : Dev Summit + All Hands (presumably)

Team Business
=== Actions from last meeting ===
 * TODO - No One Yet: investigate carbon aggregation of stats >1 month old behavior
 * ACTION: Antoine to create a task
 * Overdue

KPIs

 * https://grafana.wikimedia.org/dashboard/db/releng-kpis

New vs Maint time spent

 * Q3: https://docs.google.com/spreadsheets/d/1LJDc5W2Mlpzc0L1i7WyPwWU8AgWMn0fXRuNEEmg1EMU/edit#gid=0

Scrum of Scrums

 * https://phabricator.wikimedia.org/project/board/64/
 * Blocked on us: https://phabricator.wikimedia.org/maniphest/query/h7YTCBTJsepS/#R

Hackathon attendance
Who wants to go?
 * Antoine: no
 * Chad: no
 * Dan: no
 * Greg: no
 * Mukunda:no
 * Tyler: no
 * Zeljko: no

Trains shift first week of Febuary
Can we move them one hour later? Antoine would like to pair deploy it and level up :-} Ie: Tuesday, February 02 MediaWiki Wednesday, February 03 Thursday, February 04

Would like to shift by an hour ie: 11:00–13:00 PST --> 12:00 - 14:00 PST Or 21:00 -> 23:00 CET

Outcome: Agreed.

Idea: Grafana Deployment dashboard

 * Something that keeps track of salient stats in grafana
 * Often don't need the detail that logstash provides while deploying (post-deploy/problem determination: sure; while deploying: is shit blowing up?)
 * Something like HTTP error rate + Mediawiki errors. Annotate with sync-wikiversions, something like that
 * Played a bit with annotations this weekend...found out that they are poorly documented: http://docs.grafana.org/reference/annotations/

Annual Planning

 * Spreadsheet (team only) - https://docs.google.com/spreadsheets/d/1GBokh9zeO5vflAAZLjMuagV4FeFQHCFrApjs_KXNZ7o/edit#gid=0
 * https://www.mediawiki.org/wiki/Team_Practices_Group/Tracking_core_and_strategic_work

Past ideas and things:
 * https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Wishlist
 * https://phabricator.wikimedia.org/tag/release-engineering-epics/
 * https://docs.google.com/spreadsheets/d/14aLP8LumCz9ZSmViCrqFR14L6w0bPcbGbx-Z3rKmuWE/edit#gid=0

To discuss: How to go about this team planning.

Planning etherpad (for any notes we want to create on this): https://etherpad.wikimedia.org/p/releng-1617-plan-ideas

NOTES MOVED TO ^^^

Reduce CI Wait time

 * KPI: https://grafana.wikimedia.org/dashboard/db/releng-kpis?panelId=2&fullscreen
 * Migrate remaining CI jobs to Nodepool -
 * php composer (Zend and HHVM) -
 * as many miscellaneous jobs as possible -
 * Migrate Jenkins to Jessie -

Consolidate deploy tools

 * Migrate MediaWiki to scap3 -
 * Q2 Quarterly Goal hold over: Migrate all Service team owned services and MW deploys to scap3 - https://phabricator.wikimedia.org/T109926

Differential Migration

 * https://etherpad.wikimedia.org/p/diffuerential-weekly
 * Integrate Differential with our Continuous Integration infrastructure -
 * Shepherd the RFC -
 * Discuss at WikiDev16 -
 * Garner early adopter projects (goal: 1 project per WMF "team")