Hi Fluss community,
We now have a documented, transparent process for running our calls — see the new guide Hosting Community Calls (https://github.com/apache/fluss/pull/2760). As stated there, Fluss holds a community call on the last Friday of each month, and any community member can volunteer to host. To make this sustainable (and avoid the same one or two people doing it every month), I'd like to start a monthly host rotation and use this thread to sign up. Why we need rotating hosts - Spreads the load and lowers the bus factor. - Gives more contributors visibility into how the community runs. - Keeps the call going even when a regular organizer is on PTO or in a tough time zone that month. What hosting actually involves The full step-by-step is in the guide; the gist for one month is: 1. Announce the call in #general (https://apache-fluss.slack.com/archives/C07FCUA8SKS) ~1 week before (template + time-zone block provided). 2. Prep the agenda in the Community Sync Google Doc (mandatory — it's our permanent record). 3. Set up Fathom.ai (https://www.fathom.ai/) (~10 min one-time) for auto recording/transcription/summary. 4. Run the call: admit the Fathom bot from the waiting room, start recording, announce it. 5. Follow up: post the summary + recording to Slack, email [email protected], update the Doc. Prereq tip from the guide: use a personal Gmail (not work email) to avoid restrictions, and have the call already on your calendar before signing up to Fathom. How to volunteer Just reply on this thread with: - Name / GitHub handle - Month you'll host (the call is the last Friday of that month) - Whether it's your first time (so a previous host can shadow / hand off) First-time hosts: don't worry — ping any prior host in #general and we'll walk you through Fathom setup and the meeting-host admit step. I'll keep a running summary of who's signed up for which month at the top of this thread as replies come in. Looking forward to seeing the rotation fill up. Regards, Nicholas Jiang
