-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schedule next meeting #19
Comments
As one further point on this (super minor) I'd like to discuss timezone logistics. I was under the impression we were going to alternate for one "super bad" timezone per region. This is the third meeting and we've gone "bad for EMEA" > "bad for APAC" > "bad for EMEA". I think for equality we should have probably done a "bad for NA" (3 way rotation) rather than a 2 way rotation. |
at least would be great to have recording. In Europe today starts at 00:00 am |
@jalbertoroman see #10 for the discussion around recording. It's both not viable by W3C rules (linked in that issue) as well as opens some real accessibility issues for some who face harassment online (also discussed in that issue.) As such, the group has decided to not have recordings and is considered a closed issue. @bedfordsean this was what I proposed (also in #10), and as someone from NA, I'm happy to have my share of badly timed meetings. |
@bedfordsean We can do the next one at 2300 (PDT), 0200 (EDT) (next day), 0600 (UTC), 1400 (Signapore), 1600 (AEST). |
Thanks @seanturner - I think that's as "fair" as we can make it to maximise for all regions! |
Is that 2300 (PDT)? |
Yes, in 24h time I assume so based on the 0200 EDT :-) |
Yes. That was me messing it up (always a problem). |
At the end of the upcoming meeting we should determine the time for the following meeting and related topics
This is an agenda item to mark that we will be discussing the following meeting timing and participation as well as future topics for that meeting. I've set up a label for issues that are potentially up for discussion for following meetings and we can briefly (no more than 30m) talk through what we intend to discuss--in the knowledge that it is just a leaping off point for further discussion on this issue asynchronously after the meeting.
The text was updated successfully, but these errors were encountered: