In order to determine how the API Platform can provide value for the Movement, we need to understand how all WMF maintained APIs are currently being used.
Steps:
- 1. Talk to Metrics about what is currently available.
- 2. From that conversation, get more explicit requirements from the product side
- 3. Establsih a
Our goal is to provide transparent, equitable access to our data and knowledge as part of the 2030 WMF strategic direction.
List of known APIs to gather observable data from (in order of priority)
- Action API
- RESTbase
- MediaWiki REST API
- Wikidata Query Service (WDQS)
- Wikidata API
- EventGate
- EventStreams
- Maps Service
- Push Notifications Service
- Mobile View API
- Image Recommendation Service
- Kask Service
- ORES Service
- Proton Service
- Trending Edits
- Thumbor
- Image suggestion API
Acceptance criteria
- Usage and traffic data that describes who/what is using them, what they use them for, how much they use them, and from where geographically are they used
- Raw data and visualized data when possible
Collaboratively gathering the following information:
- Catalog of all know API services supported by technology department
- Current routing and directional (NSEW) information for each independently deployed API service and/or endpoint
- Type of protocol (REST, SOAP, RPC, SparQL, etc) for each
- Known application dependencies
- Technical and product ownership, if known
- Repository for each service
- Documentation for each service