Readers/Structured Data/Chore list

This is an experiment. The team would like to perform regular maintenance on certain processes and tasks (following the lead of Reading/Web/Chore list and Wikimedia Apps/Team/iOS/User feedback review SOP).

For now, each dev will do this one day a week, then report back at a retro


 * feedback on the frequency and scope of chores
 * preferred communication channels for alerting others (e.g. email, Phabricator)
 * preferred communication channels for indicating the state of chores (e.g. wiki page table)

Chores
This should be timeboxed to 1 hour for each time chores are tackled. The following is the priority order.
 * check if this https://integration.wikimedia.org/ci/view/Selenium/job/selenium-daily-betacommons-MediaWiki/ has failed more than twice in a row, if it has be the steward for taking action about it
 * check https://sonarcloud.io/dashboard?id=mediawiki-extensions-WikibaseMediaInfo ... atm (2019-11-27) we have 28 issues (all of which we should fix!), if the number increases then let the team know and we'll prioritize a fix
 * if anything that has passed CI has been in code review for >1 working day then review it (volunteer or not) - sample search here
 * look over recent Wikibase patches
 * document Wikibase knowledge - we had proposed to make a wiki page with headings about key parts of wikibase, and to fill in info there as part of chores
 * add individual sub-tickets of T227278 until we have a ticket for automating each test on the QA checklist (or have decided not to automate it)