Platform Guides:
2 Likes
I’ve been on one call with the new Huddle meetings and it worked well.
I live in New Zealand and most DAO calls are my 2-6am local time.
I rely heavily on recordings, transcription, AI summaries.
Right now the Huddle solution isn’t compatible with AI notetaking tools and isn’t fulfilling the needs I have to participate effectively in the DAO in an async manner which is a critical design constraint for a Globally diverse and participatory DAO membership base.
I’d like to hear from @ramitphi how these needs can be addressed?
3 Likes
agreed on the global diversity part, right now we do have recordings available and very soon we plan to bring the transcripts for the meeting (probably around next week).
It will be helpful for the other people to catchup on the discussion.
4 Likes
We support adopting Huddle01 Meet as the default platform for all DAO video calls. Recordings will no longer stay on a delegate’s personal Google Drive; instead, every session is automatically saved to IPFS, which guarantees permanence and transparency. Choosing Huddle01 also strengthens the Arbitrum ecosystem, as the team builds exclusively on Arbitrum.
The plan is free for the first six months, then only $50 per month. This is a negligible expense the Arbitrum Foundation can easily cover.
Transitioning from Google Meet will require an adjustment period, so a well-publicized trial phase is essential. During this test window we should verify call stability (latency, audio/video quality), user-experience quirks (mobile log-ins, screen-share permissions), and edge-case bugs. Hosting a few open trial sessions before the first official meeting, paired with a fallback Google Meet link just in case, will let delegates familiarize themselves with wallet log-ins, token-gating, multi-streaming, and the multiple-host feature that prevents a single point of failure.
We also agree with Gauntlet’s suggestion that a volunteer working group such as the ARDC, Entropy, or L2Beat run Huddle01 for their office hours over the next few months and deliver structured feedback before the DAO commits to a full migration. Once those boxes are checked, Huddle01 can confidently become our day-to-day governance meeting hub.
I echo Arana’s support and the general phasic approach. I do want to reiterate that a simple, yet valuable addition to this transition will be a formalization of pre / post meeting process to accommodate for the permanence of IPFS storage. Arana, Sinkas, and other meeting leaders make it a great habit to inform attendees that a meeting is starting and prepare their audio/video settings accordingly. I believe this is a small bit of added care which benefits the respect and privacy of attendees greatly, given that, though myself and many others aren’t, a good number of community contributors are non-doxxed, etc…
This would simply include a brief one or two line intro as standard process to all calls as well as perhaps a short, time limited space at the end of the call by which those who wanted to contribute off record could add comments / ask questions, etc…
Perhaps this could even be a standard recommended process made by Huddle itself.