Wikimedia Release Engineering Team/Offsites/2018-01-Sonoma/Topics

Future of SSD

 * Do we have any cross-team ideas/roadmap to work from?
 * Anything from the current program objectives that are in danger?

Nodepool drop

 * Draft requirements for a Kubernetes based solution for CI -
 * Migrate MediaWiki PHPUnit tests to Shipyard (docker-based CI) (~40% of Nodepool usage) -
 * Unify production and CI docker image build process -

Bucketing exercise

 * let's bucket our various work streams and see if we can come up with a sensible grouping that we can turn into Annual Plan "programs".
 * purpose: it will better let us cover all of our work in the annual plan, making it clear where our time is spent and why we need people working on specific things
 * also, the ever present "it'll help us point out our holes"

Gaps document

 * https://docs.google.com/document/d/1GRW02IEvR-NUIg52IvsyjDM_89i21zEF-pDY9eu1edY/edit
 * sparse, badly

New service proposal: Automatic release to packagist/npm/mavencentral etc

 * task?

Future of Differential/Diffusion/Arcanist

 * sigh

System level tests

 * Run system level tests after deployments.
 * Basic requirements:
 * The test suite should be as small as possible, but touch as much code as possible.
 * It should run in a few minutes.
 * It should target wikis that were just deployed.
 * The technology is already there, Selenium tests for mediawiki/core (and extensions).
 * Who owns the project?
 * How do we get the test definitions?
 * Who reacts to them? Fixes them?

scap-vagrant -> scap-docker

 * task?

Develop tests for phabricator search to detect regressions / search quality issues

 * https://phabricator.wikimedia.org/T182160

Continuous integration for mediawiki-vagrant

 * https://phabricator.wikimedia.org/T183456