Polis: Set up regular community call schedule

[patcon]

Re-ticketed from https://github.com/pol-is/polis-issues/issues/128

Details in first notes: https://hackmd.io/1U58Q-KOSpeDUagCMCDwzQ?view

We decided last call:

• we can do a monthly "mandatory/main/full/primary" open call (e.g., patcon, ballpointpenguin, crkrenn, urakagi, metasoarous, ... [you?])
• a biweekly "optional/secondary/bonus" open call (e.g., patcon and crkrenn are interested)
• alternating other weeks, a newcomer-friendly "orientation/hello/newcomer/onboarding/welcome/open" call, foremost for newcomer orientation and hellos with potential new ppl, but also any other facetime (e.g., patcon happy to take lead for now)
• the same timeslot as first call works for now (10:30am ET Fridays)

Proposal

Schedule (Fridays @ 10:30am Saturdays @ 3pm ET):

• 🌕 Full: Apr 3 (up to 1h)
• 🙋‍♀️ Hello/Orientation: Apr 10 (up to 30min)
• 🌓 Optional: Apr 17 (up to 30min)
• 🙋‍♀️ Hello/Orientation: Apr 24 (up to 30min)
• 🌕 Full: May 1 (up to 1h)
• ...

Notes (ongoing): https://bit.ly/polis-calls

This sound ok? Open to any and all feedback!

If this seems good enough, I can create a PR to get details into the README :)

(Expecting this week to be a bit ceremonial in nature, but will still plan to be there)

Might work on a runsheet for the future, as I've done that for other sets of calls, e.g. https://hackmd.io/2Yey0BhMSDaKrdWFKR9NeQ

cc: @colinmegill @metasoarous @pol-is/community @crkrenn

To Do

• [ ] get feedback and confirm
  
  
  
  • what names should we use to refer to the 3 types of calls?
  
  
  • anything else?
  
  
• [ ] add to README (pol-is-trial-balloon/polisCode)
• [x] run first call

[patcon]

Any preferences for video call tools? I'm inclined to just choose https:// meet.jit.si/polis https://meet.jit.si/pol.is for starters (no setup, no accounts, quite stable) but am open to suggestions!

[patcon]

Unsurprisingly, no attendees for today's unannounced call :)

Created a running pad for notes: https://hackmd.io/xJ2XZa6mSWeCp4sd_rQepg?view

[colinmegill]

Jitsi works for me, thank you Patcon for volunteering to do onboarding

On Fri, Apr 10, 2020, 11:50 PM Patrick Connolly [e-mail]
wrote:

Unsurprisingly, no attendees for today's unannounced call :)

Created a running pad for notes:
https://hackmd.io/xJ2XZa6mSWeCp4sd_rQepg?view

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pol-is/polis-issues/issues/130#issuecomment-612316777,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANQGGLTK2G5BKVIELRNUHDRL7SJPANCNFSM4ME7P3KA
.

[patcon]

Quick update: I hosted another today, but no participants. (This was aspiring to be the casual biweekly one for regular-ish contributors.) One new person jumped in briefly, but then immediately ran away before I could make them feel less skittish ;)

@crkrenn, was this something you were planning to attend in future? I recall you mentioned being down for a biweekly catch-up during the first call, so I thought I might see you today (no worries, this is super informal rn!)

Open to suggestions! E.g., if a gcal event would make this easier to remember, I'd be happy to manage that :)

[patcon]

Heh, people seem to randomly drop into the chosen jitsi channel once or twice per 30 minute slot -- including some kids laughing on the street speaking a language I didn't understand :)

(Apparently "polis" is "police officer" in Turkish/Kurdish, and "cops" in Spanish, and who know what else in other languages.)

Going to switch jitsi urls from here on out, just to be safe:
https:// meet.jit.si/polis ▶️ https://meet.jit.si/pol.is

EDIT: had a neat gesture-based conversation with a flock of laughing school children from iran, but not very productive 😆

[crkrenn]

+1 on gcal

[patcon]

fyi started keeping track of folks who've participated in some way in issue queue or PRs:
https://docs.google.com/spreadsheets/d/1ASDJ_9hgCnfLkX_rSzQ6m3hYpqVKQxY7rIFZg5djxiY/edit#gid=1531697710

Current ideas for who to take stock of:

• people who've openned issues
• people who've commented on existing issues
• people who've submitted code/docs (PRs)
• people who've reviewed code/docs (PRs)
• people who've dropped into gitter chat
• people who've participated in semi-public slack
• people who've engaged on twitter
• ...[other?]

Will use this list to some extent for community calls, perhaps creating a issue thread per month to make invites and post notes or decisions or shout-outs to new ppl. After all, the easiest ppl to engage with are the one's who already been here :)

open to suggestions on other ways to make note of ppl who've been active at any point in the past (and might be interested to contribute or follow progress in near future)

[patcon]

We've been meeting regularly and taking notes at https://bit.ly/polis-calls

@crkrenn and @ballPointPenguin and I have been regulars for the past two weeks, and @joshsmith2 dropped in 2 weeks ago.

There's a weekly gcal event that I've been inviting people to.

The format we've been getting into a groove with is this:

1. intros (if newcomers)
2. agenda-building (any things ppl wish to discuss)
3. standup (what'd you do last week? hope to do this week? any blockers?)
4. process check-out (how'd this go? anything we should do differently next call?)

Current time slot (Fri @ 10:30am ET) doesn't work for @metasoarous, so we're planning to reschedule this coming week onward. We'll mostly keep timeslot consistent, but for any future call scheduling, we're tracking our general weekly availability here: (feel free to add yours if reading!)
https://www.when2meet.com/?9086143-sc4QA

We're tentatively planning to move to Saturdays @ 3pm ET, though may rotate weeks with another slot.

Had some loose discussions this week on call, about how format might shift. Specifically, if new ppl start attending, every second week might prioritize onboarding those first-timers who show up -- with other conversations taking lower precedent in agenda. (Newcomers still welcome on all calls, just might have to ask them to observe instead of asking questions on weeks that aren't geared for onboarding.)

[patcon]

@colinmegill want a gcal invite on these? also, feel free to complete the when2meet linked above (so we can keep you in mind when scheduling, in case you ever want to drop in)

[metasoarous]

As stated in #907, we're now only going to be hosting developer calls.