Hi folks,
Tim, Ori and I got together yesterday and then, from our raw notes, I've added a few things to our idea backlog. My cleanup may not be entirely faithful to our conversation, so bear that in mind as you read this. I've included the relevant bits below for convenience, but it's also available here: https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team/Backlog
Rob
Installation consolidation
Aligning MediaWiki developer and third party installation methods. Easy install of more complicated MediaWiki installs (e.g. Parsoid, PDF rendering, Math, etc). Possible use of Vagrant-Composer?
- - https://developers.google.com/compute/docs/containers
- - Composer package types: - https://github.com/composer/installers - there exists a very nominal 'mediawiki-extension' type: https://github.com/composer/installers/blob/master/src/Composer/Installers/M... - https://bugzilla.wikimedia.org/show_bug.cgi?id=65188#c3
- - Assess viability of deploying MediaWiki using Containers to both the production cluster and various cloud platforms - ...as a way of improving our internal deployment process - ...as a way of making MediaWiki substantially easier to install by third-parties
Library-ization of MediaWiki
- MediaWiki components - CLDR parser - cssmin - HashRing - Aaron's UUID generator - Zip directory reader - PHP JSON parser - Monolog - Profiler - There is a lot of code that is reusable save for wfDebug / WfProfile calls are often the only things
- Other components - Pybal
Benefits:
- Encourages open-source contributions - Encourages developers to think in terms of clearly-defined interfaces
Configuration management
- Allowing Stewards to set certain things in the UI (e.g. per-wiki logos) - Cleaner command line methods to make configuration changes - Get rid of configuration globals - Requests for comment/Extension registrationhttps://www.mediawiki.org/wiki/Requests_for_comment/Extension_registration