Community Call Cadence & Process

[depatchedmode]

In Community Call #1 we decided to keep a monthly cadence for the calls. I think that's worth continuing.

Things to consider / discuss

Predictability

I think we should keep that monthly cadence at a steady time so that folks can plan their attendance around it. So I'd propose we say: first Tuesday of the month at 8am Pacific Time.

Timezone accessibility

Call 1 had 5 participants.
Call 2 had 17 registrations and 11 participants.

One assumption I have is the timing of the call skewed to folks able to join between UTC-8 to UTC+4. Would love to accommodate more timezones and availabilities. I think we address this in 2 ways:

• maximize async communication: keep as much of the activity as possible happening async on these forums, and via adhoc calls
• two timezone cohorts: We could potentially run two calls per month. One for UTC-8 to UTC+4 and one for UTC+5 to UTC-9 (or however we'd like to establish the dividing line). Folks on the boundary could feel free to float between the two. Any volunteers to chair & scribe a second cohort?

Process

Juan has integrated HackMD to archive notes into this code repository. We'll keep the notes running in a single markdown file, latest meeting at the top, and archive them as we hit size limits.

• How do we solicit agenda topics?
• Rotating through scribing duties
• Archiving of the video?
• What would we like to do differently next time?