Should we split the sync into two meetings for time zone coverage?

voxpupuli / community-triage

Notes and Docs for the Puppet triage google hangouts.

4 stars 5 forks source link

Should we split the sync into two meetings for time zone coverage? #15

Open binford2k opened 6 months ago

binford2k commented 6 months ago

The existing meeting is rather European time centric and is hard for other time zones. It's 7:30 am for me and 4am for @smortex.

binford2k commented 6 months ago

If we literally split the meeting in half, then we risk making a small meeting smaller.
but that's a bit of confirmation bias, the people here at this meeting now are the ones who can make this time
on the other hand, we could alternate instead of running two in parallel
maybe we should do a survey to all Vox about time zone availability and interest.

I will start with the survey.

ekohl commented 6 months ago

on the other hand, we could alternate instead of running two in parallel

I had to run out due to phone call so I couldn't propose it, but this would be my preference.

nmburgan commented 6 months ago

I think it could be really valuable to have an additional sync at a US-friendly time. It's hard getting the Puppet engineers to go at 7:30 AM, and I think it could be a huge benefit to have a face-to-face zoom call with Puppet eng and Vox. It's so helpful to see the human on the other side of the Slack message.

jstraw commented 6 months ago

if nothing else, if we put it on a top of the hour, the slack bot would stop announcing it 15 minutes into the meeting reminding me that I'm so late as to not be worth joining anymore.

I think alternating makes a lot of sense, and if it's not past 11 am Pacific, it would still be plausible for Europe to come to it.

kenyon commented 6 months ago

I'm also in Pacific time zone and have been wanting to join the meeting, but 07:30 is tough. Alternating times sounds good.

jay7x commented 5 months ago

Hello from Singapore (UTC+8) 😃 While usually I was ok to join calls at midnight, these days I should be in the office at 7am. That makes late calls almost impossible for me (except weekend maybe). From another side, I'm not participating in Vox calls yet.. so I'm totally fine if you'll keep it between EU and US :)

ekohl commented 5 months ago

Could we host a .ics somewhere that I could subscribe to? The Vox bot could also read that and announce it.

smortex commented 5 months ago

Could we host a .ics somewhere that I could subscribe to? The Vox bot could also read that and announce it.

@ekohl I use this link to add the Puppet Community calendar to my calendar: https://calendar.google.com/calendar/ical/puppet.com_1bv1p3pc433btsejtm5hikhmec@group.calendar.google.com/public/basic.ics

Unfortunately, the time-zone of the event for the Vox Pupuli meetings is not the right one, so on daylight saving change, the event may be off by one hour depending on when changes happen in Central Europe vs America/Los_Angeles.

IIRC, @binford2k said that with the switch to Perforce, they are moving from a Google-centric to a Microsoft-centric organization, and calendaring with Microsoft is a PITA. Maybe having this calendar as a community-accessible and maintained calendar (e.g. through a GitHub project, with a github page that expose an ICS to subscribe to) could help?

binford2k commented 1 month ago

@davidsandilands and I will talk technology to figure out the office hours calendar hosting, and then we can make a decision about what times for the two meetings and how we'll distribute topics.

davidsandilands commented 1 month ago

I've pinged our IT help desk to ask for their official options