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 yes I have that link for the server side setup, but I wanted to check that the UI on the ID server uses the same setup toolkit and build as for the player. (Is Choo, bankai, nanohtml and so on and that the readme is up to date, any tips and so on…).
You will need to setup wordpress for the Track API v2. We only still need to release it publicly. Until then I can add you to our github team so you can see the repo.
@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?
@developers Thanks for a good call yesterday guys. As mentioned we’ll have these calls monthly, and use these other channels for async and 1:1 discussion in the interim
resonate telegram dev chat (technical chat only). Ping @auggod or @angusmcleod on telegram and we’ll add you.
One-on-one meetings 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.
Development policies
Branch policy
We’re going to move to this branch policy across all of our repos
Development (default)
Main (production)
Branch Protection on main
Commit prefix conventions
We’re going to use these commit prefix conventions as a starting point
Continuous Integration and Access
We’re going to adopt the following github CI and access
A Github Team for push rights to repos
Require all tests to pass on every PR
Stream: linting and syntax
API: Go tests
User API: Go tests
Epic that focuses on integrity
Documentation
We’re going to update the readmes of the main repos to ensure it’s easy for folks to get started with developing with the code locally
Make it clear that there is swagger
Remove references to bankai
“You can find an example nginx configuration file in the docs.” Doesn’t work. If you want to use it include it as nginx.conf.
mkcert put some example commands
Make it explicit that the backend is needed to run it locally
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.
Maybe we can circle back on this after that community meeting?