September 4, 2026

[cassidyjames]

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

• Google Meet
• #osprey in the ROOST Discord

Proposed discussion topics:

Adopters!

• Pain points, feedback, questions, etc.

ROOST/Community updates

• Docs updates: versioning, meetings calendar, platforms
• Working on: Clearer community team membership community#83, Define an RFC process community#92, Document PR/change submission tips/guidelines community#90, Document code review tips/guidelines community#89

Contributor topics

• Changelog: Keep a Changelog format, difference from release notes
  • CHANGELOG: Add notable changes since 1.1.0 #485
  • chore: Add changelog guidance to AGENTS.md, symlink CLAUDE.md #486
• Release planning
  • Cut a new release: 1.2.0?
  • Draft rules for 1.2-next? What else?
• Code-free rules management through UI #58 and related work
• Improve testing story by migrating to vite/vitest? #492
• Discord downstream fork: how far are we actually diverged? What's the plan to get synced up?
• Security advisories: who do we have looking at/working through these? A lot of the work is updating major dependency versions (and thus updating code that uses those deps)

[cassidyjames]

Attendees: @julietshen, @cassidyjames, @ThisIsMissEm, Arjun

Notes

Adopters

Feedback from potential new adopter: Osprey is too complex to get set up, and costly to run

• With the upcoming release’s performance improvements, does that meaningfully reduce the cost? E.g. @haileyok mentioned that Bluesky should see a reduction in operating costs as a result.

ROOST/Community updates

• Docs updates: versioning, meetings calendar, platforms
• Oh yeah: community.roost.tools URL now!
• Working on: community#83, community#92, community#90, community#89

Contributor topics

Changelog: Keep a Changelog format, difference from release notes

• CHANGELOG: Add notable changes since 1.1.0 #485
• chore: Add changelog guidance to AGENTS.md, symlink CLAUDE.md #486
• @ThisIsMissEm: Changesets could help avoid conflicts! It encourages documenting the changeset for each PR, and there’s a GitHub Action to check if the metadata was included.
  • Is this just moving the overhead from “update CHANGELOG.md” to “update changesets”?

Release planning

• Cut a new release: 1.2.0?
  • Yes: it’s been 2 months, we have a nice mix of new features, improvements, and fixes in main that should go out to adopters
  • Flag: [ci] isolate compose test stack #469 looks like it’s not actually isolated; it could clobber the db. @ThisIsMissEm has a fix for this in the rules-authoring PR that she can pull out and propose separately.
  • Let’s get that ^ fix plus CHANGELOG: Add notable changes since 1.1.0 #485 in, then do a look at anything else we might have missed
  • Decision: Since we’re right before a holiday weekend, let’s cut a pre-release (e.g. 1.2.0-rc) and ask for testing/feedback, then promote to stable release after ~1 week
• What should we aim for 1.2-next?
  • Code-free rules management through UI #58
  • Plugin to use LLMs w/Osprey + natural-language query authoring that uses that

Rule authoring (#58 and related work)

• Walkthrough feedback
  • Above SML textarea, add inline docs/link to SML docs
  • Occasional bug: when switching between builder/code tabs w/out making changes, sometimes it detects a change
  • Some weirdness with the URL path: switches between path and draft parameter
  • “Engine accepts” → “Osprey accepts” or just “This rule is valid”
  • Deploy modal: should the heading or warning copy be different?
  • Minor layout bugs: related to antd which begs the longer-term question… should we plan moving to a more modern UI framework?
• Flag: can’t actually edit main.sml right now, but we think we want to be able to… maybe get @ayubun or @haileyok’s input on this
• @cassidyjames is wondering about documentation… we should make sure we at least cover
  • From a user perspective: that UI-based rule authoring exists + the basics of the workflow
  • For developers/deployers:
    • How it interacts with ACL/user roles (which probably implies documenting ACL/user roles separately…)
    • How it interacts with existing rules on disk
    • How to backup/persist rules, e.g. to git (if that’s what’s familiar to adopters)
• Since this covers so much, we should break it down into (at least) three pieces:
  • ACL/user role changes
  • Rule authoring/deploying
  • Fix for isolating compose test stack
• Things to address as follow-ups (not blocking this initial work):
  • Could technically render a diff, which seems useful
  • Could make more of a workflow: edit, preview, save, deploy
  • In features registry you can see and expand all the features, but in the rule authoring sidebar you can’t…
  • It’d be nice to have another box w/UDFs on the sidebar
  • Rules aren't versioned yet, but could be added later

Security advisories

• Who do we have looking at/working through these? A lot of the work is updating major dependency versions (and thus updating code that uses those deps)
  • Currently have contributors addressing when possible, but this is the type of work that will be assigned to a staff engineer (ROOST is making progress on hiring!)
• We’re on an old version of SQLAlchemy; should actively work to upgrade to 2.0
• Several would also necessarily be addressed in a vite migration

AST parsing discards comments (#483)

• Performance impact seems to be a valid tradeoff in the context of retaining comments e.g. for UI-based rule authoring; the impact is only at startup and being able to use the AST (while retaining comments) opens up more possibilities in the future as well (automatically updating rules if the core syntax changes, providing an SML language server)

[ThisIsMissEm]

Okay, have split out a bunch of commits from #487 into separate PRs (they're still in #487 as it needs all those pieces to be worked on easily):

• Improve GET /config test coverage #495
• Make the query tests independent between UI API and storage #496
• Improve editor tooling #497
• Fix tests deleting osprey database #499
• Improve dev user selection #500

Also opened:

• GET /queries is paginated but does not include pagination info in the response #498