Description
This quarter, we are experimenting with creating MW REST API modules for installed extensions. To inform the migration priority, we need to better understand which extensions are used most commonly and heavily across Wikimedia hosted projects.
Conditions of acceptance
- Audit MediaWiki extensions that expose MW REST API endpoints to uncover:
- How many Wikimedia hosted wikis they are installed and active on
- Usage/traffic measurement. This can be as simple as the total traffic to the base route, traffic per endpoint, or other ideas that may act as a better proxy for utilization.
- If there is any nuance or potential blockers for API module creation.
- Create a document that reflects this information and can be shared with the team.
- For the extensions, review and update (if necessary) proposed ownership in the API Maintainer's list: https://docs.google.com/spreadsheets/d/1-fcgVYgM0elpTizqN93VEsBINgcs88Gp_6Kw-wrczIs/edit?gid=0#gid=0
- Finalize priority order for team-specific follow ups and module creation with Halley.
Implementation details
The following extension APIs are currently surfaced in the test wiki and are considered in scope/prioritized for API module creation. This is a non-exhaustive list, and additional extensions may be surfaced based on other wiki configurations.
- math
- securepoll
- oAuth
- reportincident
- checkuser
- ipinfo
- eventbus
- growthexperiments
- wikifunctions
- campaignevents
- wikimediacampaignevents