April 3, 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:

• Outstanding PRs
• Adopter questions/topics
• Any additional contributor topics

Please feel to comment below with any additional agenda items or discussion topics! See you there!

[cassidyjames]

Notes

Attendees

• @haileyok
• Govind Mohan (indie atproto dev/enthusiast)
• @cassidyjames
• Giulia
• @EXBreder

Discussion

Outstanding PRs

#174 simplejson bump looks fine, @haileyok will resolve and merge

As we merge dep bumps, we should consider better testing for regressions

• @haileyok was concerned about grpcio but we got that out of the way
• As there are more adopters, we don’t want to just rely on “works for Discord!” as the litmus test

#134 is open; @haileyok to bug @ayu to re-review

#106 is still open but has conflicts; let’s merge #134 first and then see what changes are still relevant in this PR

Contributor topics

Pulling Druid out: might be some progress… tbd

• We could make a pluggable system now upstream rather than waiting for Discord; next step would be documentation/RFC for the approach
• @vinaysrao1 opened Remove druid-specific data model #188, take a look!

Finding contributors (lots more discussion in #185)

• docs can always be improved
• Still not a lot of prior art, especially in the open (and atproto might not translate well to other stacks)
• Kafka can be too intense for medium-sized implementations
• Could be good to have a conversation with Matrix folks (Shay and Travis) to hear about what blockers they hit and how they got past them
• Govind to chat w/cosocial.ca

Contributor velocity: review process can slow things down when just trying things out; not suggesting getting rid of it, but open to think of other solutions

• Could have long lived branches that have fewer requirements to merge in to continue sharing code, while lowering iteration friction; let’s try it! (@EXBreder to try it out)

JSON parsing is done through UDFs, but it’s important to define a more strict schema in some situations; would be helpful to define this in core Osprey

• Both Discord and Bluesky have ran into issues with this
• Next step: @EXBreder to file an issue!

Actions

• @cassidyjames to share notes in GitHub discussion
• @haileyok to bug ayu about re-reviewing/merging Migrate python collection types from typing types to native types #134
• @haileyok to look at/comment on Remove druid-specific data model #188 re: Druid
• @cassidyjames to check in w/Matrix folks, see if they can discuss their Osprey deployment next meeting or async
• @EXBreder to try using longer-lived branches for feature development/experiments
• @EXBreder to file and claim/assign an issue about bringing JSON parsing into core