Wikimedia Platform Engineering/MediaWiki Core Team/Check-ins/20140224
who: Bryan, Brad, Tim, Antoine, Nik, RobLa, Chad, Aaron, Greg
Possible joint projects with Wikia
edit- Revision storage
- Making MediaWiki into Composer library
- Structured logging
Budget process
edit- 2014-15 budget process kicking off
- Test infrastructure
- Internal infrastructure
- Small tools
- Admin tools
Bug escalation
edit- https://bugzilla.wikimedia.org/show_bug.cgi?id=32551#c22 - descriptionless files on Commons
- bring up with Fabrice
- https://bugzilla.wikimedia.org/show_bug.cgi?id=31369 - Non-canonical HTTPS URLs quietly redirect to HTTP
Security
edit(Chris is out, but just some quick stuff)
- Security Reviews: Hadoop, Popups, Flow’s templating engine rewrite, OWP’s Compact interlanguage links
- Password Expiration merged (thanks Aaron!)
- Would be nice to get input from Timo (or anyone frontend-y) on bug 60623
- Hoo man asked some stewards, but product’s input on bug 60481 would be helpful too, to understand why werdna disabled the disallow action when other actions were taken (commit from 2009).
CI
edit- json linting to be added to jslint jobs (in addition of jshint)
- bunch of reviews for Parsoid/Mathoid/Extensions tests
- Integration of python tox on labs to provide test infrastructure to our pythonists
Beta
edit- All quiet on the staging front
Search
edit- Starting to make CirrusSearch compatible with Elasticsearch 1.0. Yay.
- Prioritized full bug backlog
- Started work on upstream changes to save us a ton of space (5-30%, depending)
- Rack D in eqiad ready, hardware incoming
Deploy Tooling
edit- Lots of little scap changes pushed to tin/cluster:
- scap-2 and find-nearest-rsync obsoleted by python code changes
- scap no longer uses dsh; replaced by python generator and ssh
- scap now reports elapsed time for many stages of push
- progress messages while running ssh tasks! https://asciinema.org/a/7798
- Talking with Faidon about ways to remove agent forwarding
- Still trying to find time to make a beta test environment but at least I have a plan now
- Working on turning requirements etherpad into wiki content
- where should I (Greg) push my dev/deploy flow chart source (blockdiag)
- draft draft draft draft: http://i.imgur.com/eL7bB7V.png (really, drafty)
- Template:Sources-needed - http://paste.debian.net/83915/
- antoine: come on, use https://gist.github.com/! the paste which is git backed :-d
- but, github?!
- chad: use http://p.defau.lt/ -- it’s domas powered
- antoine: come on, use https://gist.github.com/! the paste which is git backed :-d
HHVM
edit- Amazon EC2 distcc build server idea didn’t work out
- ext_zend_compat exception handling patch still in progress
- random discussion on jobqueues, packaging, etc.