|operations/puppet||production||+7 -0||ores: Add varnish backend in the misc cluster|
|operations/dns||master||+3 -0||Introduce ores.wikimedia.org|
|Resolved||Ladsgroup||T130210 [Epic] Deploy ORES extension as a Beta feature|
|Resolved||Halfak||T140002 [Epic] Deploy ORES review tool|
|Resolved||Ladsgroup||T130212 Deploy ORES review tool to wikidatawiki|
|Invalid||Halfak||T106398 Revscoring tasks from Wikimania discussions|
|Resolved||Halfak||T106867 [Epic] Deploy Revscoring/ORES service in Prod|
|Resolved||akosiaris||T124203 Setup varnish endpoint for ORES|
So, we've done a lot of work since we last thought about varnish endpoints.
We now have several routes that ORES serves.
- /ui/ the reference UI for scoring edits with ORES
- /v1/scores/ the base of the version 1 scoring API
- /v2/scores/ the base of the version 2 scoring API
It's only within the scoring APIs that we get wiki project specific. E.g. /v2/scores/enwiki/ will return a list of the available models for English Wikipedia. If we were still going to make an endpoint at https://en.wikipedia.org/api/ores/, it should roughly reflect that. But in doing so, we'd hide the reference UI from users.
I see two good options.
- Add another endpoint to the reference UI for every wiki such that https://en.wikipedia.org/api/ores/ui/ loads the reference UI and https://en.wikipedia.org/api/ores/scores/ loads the base of the scroring API for enwiki.
- Stop trying to shoe-horn ORES into a project-specific URL pattern and just host it at something like https://ores.wikimedia.org and allow the #MediaWiki-extension-ORES to include scores within api.php.