## 1) Continue REST API build-out and service development mentoring
# Focus on high-traffic end points.
# Thumb API?
# Develop a longer term layout for the REST API. {@eevans //upvote//}
## 2) Migrate several job queue use cases to the change propagation service; start dependency tracking
# Build on work done in Q2 to replace job queue use cases.
# Support dependency tracking (by integrating with link tables, tracking new dependencies), and start using this for change propagation.
# Develop long-term plan for replacement of the job queue
# Light-weight Kafka replacement for small-scale/dev deployments
# Atomic event production from MediaWiki {@eevans //work-on,upvote//}
## 3) Storage: Separate hot from warm content; import full wikitext history
# Store current versions separately, so that they are cheaper to access & can be replicated to PoPs with modest resources.
# Improve compression ratios for old revisions, possibly at the cost of some access latency. {@eevans //work-on,upvote//}
# Import the full wikitext history & evaluate this as an option for a longer-term ExternalStore replacement.
## 4) Community engagement
# Finish the RESTBase-The-Framework work
# Create a showcase on how to use it RESTBase-The-Framework (step-by-step tutorial) {@eevans //work-on,upvote//}
# Convert RESTBase to ES6
# Community engagement / marketing: tech talks, blog posts, updated docs & showcase {@eevans //work-on,upvote//}
# Push distribution for third party users forward (docker images, https://phabricator.wikimedia.org/T92826#1804775)
# Release RESTBase 1.0 (signaling a level of readiness, maturity). {@eevans //work-on,upvote//}
### Legend
| //upvote// | indicates an opinion that the item should be included in the goals |
| //work-on// | indicates a desire to work on the item |
## See also:
- {T120171}
- {T120242}