Erik Sipsma3294 did some maintenance

[marsh pagoda]

Yes saw all that activity, do you think it's time to add branch protection so we have to go through PRs to merge? I'm kind of borderline... as long as CI checks are fast and simple (which I think they are) then maybe it would be good

[digital juniper]

meh, your call

I'm good with the 2 of us pushing directly (at least now we get alerts if stuff breaks)

but I think as soon as we add another team member we should switch to PRs

[marsh pagoda]

Yeah that sounds good

Thanks for adding all that though, I'll append adding tests for the rest of the extensions to my todolist

netlify is the only tricky thing, but we do that in dagger so i'll see if there's a quick path to being able to test here too

[digital juniper]

of course! prepping so we can add more people

[digital juniper]

Yeah, I think just one extension would be enough, to define patterns/best practices. Adding tests to other extensions is a good "first issue" for someone onboarding

I was thinking in terms of "easy" onboarding issues (easy as in doesn't require design work):

• Core parity with LLB (e.g. Copy, etc)
• Testing the Core API
• Testing the extensions
• Writing new extensions (TBD -- whatever makes sense)
• Dogfooding (maybe switching our own CI to cloak? see above)

hard issues (e.g. good sized splittable chunks):

• code generator v2 (needs design work)
• TS SDK (with TS best practices, e.g. from someone with a TS background)
• MAYBE: python/other SDK? (e.g. what Helder was looking into)

btw free now if you want to chat

[marsh pagoda]

will call in 5 mins, just finishing up one chunk of code

[digital juniper]

sure, nothing special to talk about, just general catch up, ok to skip if you prefer

[marsh pagoda]

oh okay, I mainly wanted to make sure you were onboard with the way trivial resolvers were all migrated to user extension code. If you're good with that then can skip.

[digital juniper]

yep happy to chat about that