There was also talk of moving the call to not a European evening time and more of a day time call (so 12.00 Midday to 16.00?) though that could alienate some of the US based folks but includes the middle east/india/asia based folks.
I would perhaps suggest (if there’s appetite) for a US friendly time, Europe friendly time and try to make either of these India/Asia friendly too.
Anywho, I can start another doodle poll on what preferred timings are for folks but I suspect we won’t find a perfect consensus? thoughts?
I think @Erioldoesdesign is probably right. It’s going to be very difficult to find a time slot that suits all three continents. But given the poor call attendance at the moment, it seems the current time is not working either. So yet another Doodle pool might be in order
So I think I got the DST times right. The timings there were done after DST so they are/were included in the original times but I’ve added in time after DST go ‘forward’ again.
So looks like this:
CEST 13.00 / GMT 12:00 / IST 17.30 / JST 21.00 / EAT 15.00 / DST(EST) 07.00 (08.00) /DST (PDT) 04.00 (05.00)
Thanks so much for fixing, it sucks that US is going to get excluded (other than the east coast) if we switch to Europe lunchtime. If there’s anyway people could do early afternoon that would be amazing
But, can I ask for FOSDEM to be added to the agenda? Hopefully some of the people working on the devroom will be in the call and they can give an update.
At this point it would be good to discuss an extension of the submission deadline, something we end up doing every year
Discourse won’t let me reply to this more than 3 times… so I had to edit my previous message
So, Wednesday 6th May at 19.00 CEST? Anyone?
Agenda could be!
OSD virtual Summit? how, why, when?
FOSDEM actions left over? are there any?
@macruzbar Apologies we have yet to talk about a SF/CA meet up and supporting you. We have a busy winter/start to the year it seems! Can we please make sure you’re heard and supported going forward
I didn’t see anyone so I stuck around for few mins before tapping out.
The core team have discussed a meeting tonight on June the 4th at 20.30pm BST/GMT (see other timezones here!)
I think In general, having a single day with a single time doesn’t cover both core team and the potential global communities.
I’m proposing to trial, for 6 months me doing something like:
Over the first week of every month, so from July 1st to July 7th 2020 (and then for each month after) hold 1 hour meetings at different times of the day.
Proposal example for next month:
July Wednesday 1st - CEST ‘evening friendly time’ 19.00 (our regular time)
July Thursday 2nd - EDT ‘evening friendly time’ 19.00
July Friday 3rd - PDT ‘evening friendly time’ 19.00
July Saturday 4th - CEST ‘daytime friendly time’ 13.00
July Sunday 5th - Day off or a request a time day.
July Monday 6th - JST ‘evening friendly time’ 19.00
July Tuesday 7th - IST ‘evening friendly time’ 19.00
Agendas would be the same across the meetings to get feedback on topics from all different folks.
I’ll also send a pull request to the https://opensourcedesign.net/events/monthly-online-meeting/ page to reflect these changes if we’re cool with them? I propose just trying this out and see if it helps with some of the multi-timezone problems. If it doesn’t well…then we don’t have a timing problem and it’s possibly something else like an async agenda topic on the discourse each month or a shared doc or we record calls to watch back.