June 26, 2026

[cassidyjames]

Our bi-weekly working group call is 1730–1830 UTC!

• Google Meet
• #osprey in the ROOST Discord
• Discord event series

Proposed discussion topics:

• PRs needing review
• Anything else that can be upstreamed?
• Docs
• Adopter feedback/topics

As always, feel to comment below with any additional agenda items or discussion topics. See you there!

[cassidyjames]

Attendees: @cassidyjames, @haileyok, @julietshen, @chimosky, @scarnecchia

Notes

PRs needing review

• @julietshen has been going through open PRs to review what she can
• Two open PRs replacing highcharts
  • Plotly osprey_ui: replace Highcharts with Plotly #314
    • @cassidyjames and @julietshen to test locally; @cassidyjames didn’t have a demo branch to easily test
  • Echart Replace Highcharts with Apache ECharts in Timeseries chart #374
• Python types Migrate python collection types from typing types to native types #134
  • Approved! Conflicts again; need to resolve those conflicts and then merge. @chimosky will update, then can ping @haileyok on Discord so we can get it merged.
  • Any existing open PRs that haven’t moved to native types will also need to be updated; worth it
• Kafka env vars make kafka topic creation and partition config configurable via env vars #255
  • We want this, but there’s work to be done; @cassidyjames to comment on it, then we can follow-up in ~1 week to finish it if there’s no reply
• Dependabot
  • @julietshen to see if there are some easy ones to get merged in

@cmttt’s PR #341 has been merged! 🎉

• Discord was running a light fork internally; now working to get back onto main and push fixes more directly upstream
• ~20% of the load of the previous version!

Anything else that can be upstreamed?

• @cmttt is working on another performance improvement that should be able to be upstreamed

Next release: 1.1

• Would like to finalize at least a demo of the LLM-assisted stuff; even if it’s not merged in, would be nice to be able to demo it
• Highcharts and licensing audit
  • Dependabot keeps bumping highcharts in other PRs; taking care of this would also reduce that noise
• @haileyok to talk to Discord team for any papercuts/issues/bugs to ensure they get filed as issues
• Stress test Build a stress-test CLI for input sinks + rate-of-success measurement #324 to unblock protobuf upgrade
  • Protobuf bump itself is probably fine; grpcio upgrade is the more scary change
• Open vulnerabilities

Unused/unneeded/unwanted deps

• Unused: Remove unused dependencies (likely Discord-era leftovers) #323
  • We should remove things that are not being imported; if Discord is relying on them in downstream things, they can import them there instead
• GCP: Make Osprey runnable without GCP credentials (tracking) #343
  • Things break/don’t work without GCP credentials; we shouldn’t hard depend on this though (we want ROOST projects to be infra-agnostic!)
  • Needs to be triaged to understand what can be completely removed, and what can be worked around in Osprey when missing the credentials
  • @julietshen is happy to take some time to see what can be removed
  • @chimosky to draft a message in #osprey pinging Discorders to ask them to take a look :)

Docs

• Need to add more setup/architecture info, e.g. “how do I send data to Osprey” → Document how to get data into/out of Osprey #381
  • How do you run it without running a fork??
• If we could pull more rules examples in, that could be helpful → Expand rules examples in the docs #382
• Integration & plugin docs! → Document integrations and plugins #383
  • UDFs + input sinks, output sinks
  • Using hashes, own ML models, connecting to review tool
• New features
  • Dark mode! → Document dark mode #384

Adopter feedback/topics

• Release planning can help adopters as well
• More configuration via env vars as we’ve learned adopters don’t want to have to edit the code
• Something to consider: in-tool way to solicit feedback/file issues. Need to be considerate around not showing to moderators who are actively working on an investigation, but maybe for admins/in a settings area. Also need to be careful/clear around not soliciting screenshots of private/internal data.
• Atproto fork status?? Out of date atm, but would be great to get it closer to upstream
  • How do we make Osprey better at not needing a fork to integrate w/platforms?
    • Using your rules directory? (submodule?)
    • Osprey feels like it should be a docker file you run and pass parameters to give it your stuff; shouldn’t have to download code and sync, or maintain your own docker image of Osprey. Your docker compose or k8s config should pull in the upstream docker image and set up your other dependencies/config.
    • Good example: Home Assistant with its “apps” (formerly add-ons) model, and HACS (Home Assistant Community Store)
    • Could schedule a design session to come up with what the implementation should be here; maybe post-1.1 release
      • Invite some adopters, like Bluesky, Matrix, Discord to identify pain points and inspiration from how they’re handling things
      • Similarly: UX design workshop to discuss pain points, features, etc.

[julietshen]

@haileyok qq - will the UI for the LLM powered query builder land? I would really love to support you in any way on this!