User:Daniel Kinzler (WMDE)/Architecture 2018

This is just an "if Daniel was King" brain dump, it’s not sorted or qualified in any way, and rather incomplete.

If Daniel was king, these would be the hot platform topics we would focus on in 2018: See also:
 * Addressing Database Scalability issues
 * Addressing tech debt, improving test coverage
 * Making all of MW core aware of Multi-Content-Revisions
 * Alternatives to mediawiki/vendor, including JS libraries
 * Strategy for dependency tracking / change propagation; Future of the JobQueue (see DependencyEngine)
 * Deciding on which platform we need to support for 3rd parties (SOA vs LAMP, node.js or not...).
 * Future of deployment (at WMF and 3rd parties): Vagrant vs Docker vs Kubernetes...
 * JS framework experiments and consolidation (React vs Vue vs OOUI, ResourceLoader)
 * Deciding on support level for old software on the client side (what needs to work without JS? what needs to work with old browsers? this is mostly product, but highly tech-dependent)
 * Overhauling the code review process (cross-team, cross-org, volunteers, 3rd party pros)
 * The future of Parsoid, WikiText 2.0, etc
 * Unified strategy for offline reading support (mostly product, but highly tech-dependent)
 * “Content Assembly at the edge” (Reading/Web/Projects/NewMobileWebsite etc)
 * Support for multilingual wikis (especially for anonymous users)
 * Status and Future of Multi-Datacenter capabilities
 * MediaWiki_Platform_team/Simplifying_the_Wikimedia_Foundation_technology_stack
 * Wikimedia_Audiences/Needs_from_APIs