Good points raised here, @Axia. I think this discussion is much needed. Before diving into format or budget though, I’d like to clarify what’s actually being proposed:
Is your idea for the Collective to fund this through the treasury? Or is this a coordination effort for people already attending? Or a coordination for some of us to attend? Or a coordination so that Rootstock Labs to cover initiative costs, given that ecosystem visibility and developer pipeline arguably sit within their scope?
I remember we’ve had similar conversations before around event sponsorship, and the conclusion was for not evaluating events individually, but that there should rather be an organized annyual strategy, coordinated with Rootstock Labs.
On the event itself, I agree with @Eren_DAOplomats. TABConf is technically substantive, the Builder Days and open-source schedule format attract serious developers rather than the typical conference retail crowd. A workshop or side event would attract much better than passive branding. Good fit for Rootstock’s audience.
I feel we need to define the “how we organize and fund this” question in order to confidently capitalize on these opportunities.