After the re-org, the team formerly known as mobile web inherited a large number of extensions, many of which we are responding to reactively. We should have a broader conversation with stakeholders about where we can/should be reflective and proactive.
To quote a member of the web team:
The Reading Web team is tasked with maintaining a number of extensions some (most/all? *) of which make up our dashboard. In my experience, we've very rarely stopped to survey any of the projects that we tend to – be it long outstanding Phabricator tasks, open changes in Gerrit, proofreading documentation, or doing whole-codebase reviews.