- Discuss over of ORES in sync meeting (20 mins)
- Discuss product needs, cache invalidation, maintenance scripts, etc.
- Summarize concerning potential scaling issues & create new tasks.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T145829 Trending API should consult ORES | |||
| Declined | None | T157132 Add ORES articlequality data to summaries? | |||
| Resolved | Tgr | T153321 [Spike] Review ORES architecture for Reading Product plans |
Event Timeline
Comment Actions
@dr0ptp4kt, I created a task for the ORES architecture review. Can you make sure that anyone who ought to be is subscribed and that we move forward with getting this review done?
Comment Actions
It's a top priority. Gergo will be primary from the Reading Infrastructure engineering perspective, and I've added Corey, Bernd, and Brad, as well. We'll be discussing the work ahead for the quarter and - more pressing for annual planning purposes - the immediate near term 4-6 week timeframe today.
Comment Actions
Great. Thanks @dr0ptp4kt. @Tgr, would you be willing to have this task assigned to you?
Comment Actions
@dr0ptp4kt is there a ticket for the development of the plan itself? If not I can create one, just let the know.
Comment Actions
This has been scoped down to reviewing architecture needs for T157132 and T145829 specifically, and the consensus seems to be that the current architecture is suitable (on both the ORES and services sides). There is a discussion about scaling and hardware needs in T157222 but that's mostly unrelated since it needs to happen anyway. So this task can be closed without any new action items.