[Scrum] - SUSI Interpretation Project - 20260731

1 view
Skip to first unread message

Eshaan Walia

unread,
Aug 1, 2026, 12:35:44 AM (10 days ago) Aug 1
to SUSI.AI
1. What did I do yesterday?
PR 50:
  1. Area: Data
    Change: Renamed hls_url to stream_url and simplified room status to idle/running.

  2. Area: Stream resolve
    Change: Pulls ingest URL from room module config or stream schedule (YouTube, HLS, etc.).

  3. Area: SUSI wiring
    Change: Sends all streams via SUSI YouTube source using stream_type on configure.

  4. Area: Settings
    Change: Split "logged in" (is_susi_connected) from "ready to run" (is_susi_configured).

  5. Area: Orchestration
    Change: Creates/stops SUSI tenants per room and serializes room interpretation state.

  6. Area: Tests
    Change: Added coverage for URL resolution, session start wiring, settings helpers, and room form parsing.

PR 52:
  1. Area: Video admin API
    Change: Added REST endpoints to get/patch room configuration and start/stop SUSI sessions from the video admin.

  2. Area: Commons UI
    Change: Added a read-only rooms overview in Commons, linked it from the dashboard, and displayed connected vs. ready state.

2. What do I plan to do today?
    • Need to refactor the room interpretation, it should come first to allow different rooms have different interpreters.

    • Explore voxbento

    • Use built lang-source fields in eventyay vidoes to work with interpretation plugin


    3. What is blocking me from making progress?

    No Blocker at the moment
    Reply all
    Reply to author
    Forward
    0 new messages