Skip to content
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

Closed
AramZS opened this issue Feb 8, 2022 · 8 comments
Closed

Schedule next meeting #19

AramZS opened this issue Feb 8, 2022 · 8 comments
Assignees

Comments

@AramZS
Copy link
Contributor

AramZS commented Feb 8, 2022

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.

@AramZS AramZS added the agenda+ Request to add this issue to the agenda of our next telcon or F2F label Feb 8, 2022
@AramZS AramZS moved this to On Agenda in April Agenda In-Progress Mar 16, 2022
@AramZS AramZS removed the agenda+ Request to add this issue to the agenda of our next telcon or F2F label Apr 7, 2022
@bedfordsean
Copy link

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.

@jalbertoroman
Copy link

at least would be great to have recording. In Europe today starts at 00:00 am

@eriktaubeneck
Copy link
Contributor

@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.

@seanturner
Copy link
Contributor

seanturner commented May 17, 2022

@bedfordsean We can do the next one at 2300 (PDT), 0200 (EDT) (next day), 0600 (UTC), 1400 (Signapore), 1600 (AEST).

@bedfordsean
Copy link

Thanks @seanturner - I think that's as "fair" as we can make it to maximise for all regions!

@bmayd
Copy link

bmayd commented May 17, 2022

@seanturner

We can do the next one at 1100 (PDT), 0200 (EDT) (next day), 0600 (UTC), 1400 (Singapore), 1600 (AEST).

Is that 2300 (PDT)?

@bedfordsean
Copy link

Is that 2300 (PDT)?

Yes, in 24h time I assume so based on the 0200 EDT :-)

@seanturner
Copy link
Contributor

Yes. That was me messing it up (always a problem).

@AramZS AramZS closed this as completed Jun 20, 2022
Repository owner moved this from On Agenda to Move to Next Meeting in April Agenda In-Progress Jun 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Move to Next Meeting
Development

No branches or pull requests

6 participants