Thank you @Raphael_Anode for sharing the output of the harmonica.chat session.
As @tamlerner clarified, the scope of tomorrow’s call a focus only on Events, with attendance from the RLabs Events manager.
I wanted to share a few thoughts to help frame the conversation.
The focus of this call is events — specifically, we want to understand RLabs’ existing strategy, their roadmap for the year, and where they see gaps. From the Collective’s side, we want to make sure we’re funding teams that are genuinely additive to Rootstock’s goals, not duplicating work RLabs is already driving. Alignment here will help us allocate events grant funding more strategically.
One area I think deserves attention is the lack of institutional knowledge being retained from the events grants we’ve funded to date. When an event is completed , a lot of valuable information disappears — the events/hackathons funded, the materials that were used, photos and artifacts, and what results were achieved.
To solve this, I’d propose we work toward building a structured events knowledge base that includes:
- A registry of all grantees and events the Collective has funded
- A shared database of photos, metrics, and KPIs from those events
- Reusable materials and documentation — templates, booth assets, talking points, etc.
Point 3 is especially important. Right now, grantees are likely reinventing the wheel each time. Furthermore, there is a lack of consistency in messaging. A library of reusable materials would raise the quality floor across all events and reduce overhead for future grantees and delegates when reviewing events grants.
There’s a practical, near-term event already in front of us: TabConf, which has been shared with the Collective previously (thread here). If The Collective wants Rootstock to have a presence, the scope, budget, and level of participation will need to be determined. This could be a great test case for developing a more deliberate events strategy — working through it together with RLabs would give us a concrete example to stress-test our strategy against.
I will not be able to attend tomorrow’s conversation tomorrow due to time zone constraints, but I’m looking forward to watching the recording!