Wikimedia Release Engineering Team/Local Dev Sync/2020-02-13

Works in progress:

restrouter https://gerrit.wikimedia.org/r/c/releng/local-charts/+/570236
- keeping chart in local-charts for easier review
docker compose https://gerrit.wikimedia.org/r/c/mediawiki/core/+/550708
xdebug https://gerrit.wikimedia.org/r/c/releng/dev-images/+/571828
- asking people in core clinic duty for some review before finally merging
- should this work go in a subdirectory in core?
  - James: people should accept that RelEng owns enough files in root of repo that this shouldn't be an issue. There aren't multiple files here.
  - Kosta: advantage of keeping file in root is file completion for docker exec. Needs less documentation and is less complicated this way
  - James: maybe we should add some docs about things like how to run unit tests?
    - See https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Running_and_debugging_unit_tests for comparison
    - Otherwise good to go. point questions to #mediawiki channel
  - Kosta: could purge maintenance/dev scripts as an offer to others. need to save router.php for quibble (move it into quibble) if we do so.
  - James: At some point quibble could be replaced with docker for orchestration
  - How do we know we're not breaking the world when we rev this file in the future?
    - Brennen: You tear down your env and make a new one. could have data loss
    - James: Need some docs there.
    - Kosta: in the future would be advantageous to have tests for changes to the docker image
      - https://www.mediawiki.org/wiki/Docker/Recipes Where should this live? How to share it?
    - Brennen: We've had convo about this but no clear answer
  - James: Update main landing page with our official docker thing
  - Kosta: Phab project for tracking changes
  - Brennen: What should we call it?
mariadb replication https://gerrit.wikimedia.org/r/c/releng/local-charts/+/571621
proposal for complex dev environment: https://docs.google.com/document/d/1Z3yiRRtuux4yvI4V_9FmKkHlgfm9zPZ0aqe9wAsEgGc/edit#
- Kosta: wach out for running on things on the host that gives different results for different OS for composer.php/npm modules
- Jeena: We should definitely consider whether IDEs can integrate with a k8s cluster before continuing down this roa
- Mukunda: VSCode has some k8s integration
- Jeena: Let's work on that together
- Kosta: Could ask Jetbrains about phpStorm & K8s
- Brennen: Does anyone know how many people use a certain IDE?
- James: people go back and forth but we have Jetbrainz licenses that we give to staff and community members so people probably use those. 1/3-1/2? of peple use some kind of IDE
- Mukunda: have some instructions on basic setup
- The idea of tests and quick keyboard shortcuts is nice

Action Items

[kosta] Docs docker in core on how to run unit tests, note that it's for temporary testing not long-term data storage, etc.
- [done!] also added notes about running selenium and api-testing tests
File task for cleaning up maintenance/dev scripts
Docs for what happens when there is a new version of the docker image
Update the main (Docker?) dev page with our new solution (once it's merged) and figure out where the docker recipes should go
[brennen] Phab component for tracking changes, update DEVELOPERS.md with reference to it and #mediawiki support channel - Using existing mediawiki-docker tag
- [kosta] updated the docs for that
Trying to get IDEs to test with k8s - Mukunda & Jeena
Do something about the mediawiki-docker in github