This is where we can discuss general Resonate development, ranging from help with getting set up and development policies. Essentially any development work that doesn’t fit into #platform:epics. There’s a few ways we’re doing this
Monthly meetups (see below)
Telegram dev chat (technical chat only). Ping @auggod or @angusmcleod on telegram and we’ll add you.
One-on-one calls with the senior resonate devs (currently @auggod and @angus) if docs + chat isn’t doing it for you.
#platform forum category for any general development discussions that don’t fit into one of the sub-categories.
@boopboop@auggod@Nick_M@datafruits If you’re ok with it, given the “timezone shuffle” factor, and that we’re scheduling in a lot of meetings atm, I suggest we tackle this like so
Add whoever wants to join to the resonate telegram dev chat (technical chat only). Ping @auggod or @angusmcleod on telegram and we’ll add you. You can ask questions when you get stuck with local setups / the readmes there.
Setup one-on-one meetings with the senior resonate devs (currently Aug and myself) if docs + chat isn’t doing it for you. One-on-one is better for this kind of thing and timezones.
Have a monthly meetup where we can also cover things like Resonate github policy. Aug and I have been discussing this on and off.
For 3, I propose we start that 2021-09-14T11:00:00Z. @auggod does that work for you?
there’s a swagger that works? I’ve tried looking for it but seem to have missed it.
Make it explicit that the backend is needed to run it locally - it would be nice to have instructions for running just the stream frontend locally (my task) and also instructions for running the frontend and backend(s) locally. I can attempt this second one.