January 23, 2026

[cassidyjames]

We're having our bi-weekly virtual working group call this Friday at 1830–1930 UTC!

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

Proposed discussion topics:

1. Demoing and getting started with Osprey
2. Work on the docs
3. v1 release
4. FOSDEM!
5. Adopter questions/topics
6. Any additional contributor topics

[cassidyjames]

Meeting notes

Maintainer discussion

Mix of the individuals and the teams: individuals demonstrate that there are specific people who are responsible, but having a team (e.g. @roostorg/discord) helps distribute the load and simplify development. Potentially could point to a @discord/osprey team if possible—not sure if that's possible in the CODEOWNERS.

Actions:

• @cassidyjames to check if we can add a Discord-owned team to CODEOWNERS
• Merge CODEOWNERS change

Docs

• Cassidy working on docs site, deduping info between sections and focusing on reproducible "getting started" guide
• @haileyok did really good docs on rules; could PR? 🥺
  • Also enables Claude to assist in writing rules!!

Osprey v1 Release

• Planning Jan 29 release to support FOSDEM talk!
• Also updating docs to refer to v1 and not v0, etc.
• Matrix also planning to deploy to staging that week!!

Other thoughts/updates

• Thought exercise: We have the UDF documentation, are there other MCP endpoints we'd want?
• We've been getting more questions about if/how Osprey and Coop can interact
  • Osprey puts its results into Kafka, so Coop could interact there
  • Labeling service would probably be a better way to integrate
  • Matrix is interested in this, too!
  • Can call out to the Coop API
• After v1 launch, we plan to have a ROOST product designer take a look at Osprey and seeing how we could abstract the visualizations from Druid so it would work with other backends; also a very engineering and architecture problem to consider

[cassidyjames]

Ah, as I suspected, users/teams in CODEOWNERS must have direct permissions on the repo according to the docs, and since you can't directly grant an external team from another org access to the repo, you can't add them to CODEOWNERS. This means we'll need to manage a separate Discord team on the ROOST org if we want to grant permissions via CODEOWNERS. I've created @roostorg/discord and invited contributors there so we can go that route.