[Scrum] - SUSI Interpretation Project - 20260630

1 view

Skip to first unread message

Eshaan Walia

unread,

Jul 1, 2026, 12:43:45 AMJul 1

to SUSI.AI

1. What did I do yesterday?

(eventyay-interpretation) - Updated Issue(#29) - Switch caption delivery to Websocket (primary) with SSE signaling/fallback, remove polling
open
(eventyay-interpretation) - Updated Issue(#12) - Establish plugin communication layer between eventyay and eventyay-interpretation
closed
(eventyay-interpretation) - Updated PR - Feat/Milestone 1: SUSI connection layer for eventyay-interpretation
use the standard plugin settings backend
Move the Interpretation page under the Admin Settings section.
Update HLS to pass through SUSI for Eventyay testing.
Finalize PR #19 and prepared it for merge.

Yesterday, I improved the Eventyay Interpretation plugin by integrating it with the standard plugin settings backend and moving the Interpretation page under the Admin Settings section. I also updated the HLS workflow to pass through SUSI for Eventyay testing, refined the WebSocket/SSE communication design, and finalized PR #19 for merge.

2. What do I plan to do today?

Today, I plan to extend the Interpretation plugin to support multiple providers, like SUSI and VoxBento. I will also update the per-room configuration and event caption settings, and improve the connection flow by making WebSockets the primary communication method for SUSI and eventyay communication with Server-Sent Events (SSE) as the fallback.