That's a fair question.
To be transparent, we're still very early, so there aren't rigid day-to-day roles yet. People generally gravitate toward the areas they're most interested in and end up owning those over time as the project evolves, rather than us assigning fixed responsibilities from day one.
I'd rather not go into detail here about some of the things we're currently working on since a few are still unannounced, but if you join the Discord I'd be happy to give you a fuller picture there.
There's also no mandatory activity or minimum contribution expected if you join. We're an open-source project first, so people contribute when they have the time and interest.
On the ownership side, we're still figuring out what the long-term structure should look like ourselves. Everything we've released so far is under MIT or Apache-2.0, and we'd actually be interested in hearing your thoughts on how ownership and responsibilities should evolve as the project grows.
For the technical problem: happy to fix it tomorrow, or wait for your PR (let me know)