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

2023 Meeting Schedule #89

Closed
seanturner opened this issue Jan 11, 2023 · 19 comments
Closed

2023 Meeting Schedule #89

seanturner opened this issue Jan 11, 2023 · 19 comments
Labels
logistics Hashing out meeting logistics

Comments

@seanturner
Copy link
Contributor

seanturner commented Jan 11, 2023

We have settled on having meetings every 6 to 8 weeks. We should schedule the 2023 meetings now. We would like some help determining what dates would work best for the group. Please let us know if there are known conflicts with any of the dates that follow.

Remember we are alternating timezones (see #66 (comment)) so I have put A, B, C to indicate the timezone. The October 2022 meeting was in the C timezone and the February meeting is in the B timezone so we are going to skip a B timezone meeting in May. The days are relative to the timezone so depending on where you are they might shift around some - but you should get the idea.

Likewise please see the F2F meeting cadence issue about whether we should turn one or more of these virtual meetings into a F2F meeting.

TENTATIVE DATES

** Keep reading the dates that were proposed here were changed. **

Month Days Timezone
March 21 & 23 A
May 2 & 4 C
June 13 & 15 A
July 25 & 27 B
September 5 & 7 C
October 24 & 26 A
December 5 & 7 B

TENTATIVE DATES

@seanturner seanturner added the logistics Hashing out meeting logistics label Jan 11, 2023
@martinthomson
Copy link
Contributor

Those July dates conflict with IETF 117. Otherwise, these are all so far out I can't see a problem.

@seanturner
Copy link
Contributor Author

Funny IETF 117 wasn't in my calendar - fail.

We could move it one week prior or after. After might be better?

@samuelweiler
Copy link

TPAC was just announced for 11-15 September in Sevilla, Spain. member-only announcement

@martinthomson
Copy link
Contributor

I don't mind which way things get nudged. For the IETF conflict, either side is good. For TPAC, we probably should drop the 5&7 and plan to meet in person.

@seanturner
Copy link
Contributor Author

Agreed if what I proposed in September is right there, then yeah we would meet in person at TPAC.

@seanturner
Copy link
Contributor Author

As discussed at the F2F meeting in Feb:

  • Locking in the March and May proposed times. @seanturner will submit W3C calendar and GitHub issues.
  • June is the next potential F2F meeting. Location is TBD, but not likely N.A. No objections to meeting in APAC.
  • July meeting time clashes with IETF so we will proposed sliding it forward one week.
  • For F2F meetings, plan to have them not start on Monday.
  • For TPAC, Chairs will request more time.

@seanturner
Copy link
Contributor Author

***LOCKED IN DATES ***

Month Days Timezone
March 21 & 23 A
May 2 & 4 C

***LOCKED IN DATES ***

REVISED TENTATIVE DATES

Month Days Timezone
June 13 & 15 A
July 18 & 20 B
September 5 & 7 C
October 24 & 26 A
December 5 & 7 B

REVISED TENTATIVE DATES

If the June meeting ends up being a F2F meeting, the timezones for the following meetings will be revisited.

@jaylett-annalect
Copy link
Contributor

Because I can't remember the timezone letters to time translations, copying this from the referenced comment:

A (4th) 0800 CEST / 0700 BST / 0600 UTC / 0200 EDT / 2300 PDT (previous day) / 1400 Singapore / 1600 AEST
B (1st/3rd): 2400 CET / 2300 BST / 2200 UTC / 1800 EST / 1500 PST / 0600 Singapore (next day) / 0800 AEST (next day)
C (2nd) : 1500 CEST / 1400 BST / 1300 UTC / 0900 EDT / 0600 PDT / 2100 Singapore / 2300 AEST

@bmayd
Copy link

bmayd commented Mar 14, 2023

@seanturner The W3C PATCG calendar is showing me a start time of 03:00, not 02:00 for this meeting:

21 March 2023, 03:00 - 06:00 America/New York

@seanturner
Copy link
Contributor Author

3am (eastern) is the correct time. Also see patcg/admin#12.

If the A, B, or C times fall on one side or the other of daylight savings time the scheduled time might change.

@bmayd
Copy link

bmayd commented Mar 14, 2023

Thanks for clarifying. I mentioned it because the previous comment from jaylett-annalect indicated 0200 EDT:

A (4th) 0800 CEST / 0700 BST / 0600 UTC / 0200 EDT / 2300 PDT (previous day) / 1400 Singapore / 1600 AEST

@jaylett-annalect
Copy link
Contributor

On reflection that was talking about a specific historical one, so apologies for introducing that confusion.

@seanturner
Copy link
Contributor Author

I find timezone hard so clarifying questions are always welcome ;)

@samuelweiler
Copy link

June meeting is F2F: patcg/admin#14

@seanturner
Copy link
Contributor Author

We need to select the timezones for the July, October, and December meetings. Look up a couple of comments for the timezones (note they might move an hour one way or the other based on daylight savings). I was going to suggest July=B, October=C, and December=A.

Month Days Timezone
February 6 & 7 F2F - EST friendly
March 21 & 23 A
May 2 & 4 C
June 14 & 15 F2F - BST friendly
July 18 & 20 TBD
September Schedule is TBD but a couple of hours the week of 11-15 F2F - CEST friendly
October 24 & 26 TBD
December 5 & 7 TBD

@seanturner
Copy link
Contributor Author

I'll let this settle for a week and then I'll close it out.

@bmayd
Copy link

bmayd commented May 5, 2023

I was going to suggest July=B, October=C, and December=A.

This works and happy to accommodate any schedule if folks want to make changes.

@seanturner
Copy link
Contributor Author

Okay will submit meeting request today.

@AramZS AramZS pinned this issue Jul 10, 2023
@seanturner
Copy link
Contributor Author

Meeting announcements posted for Sept, Oct, and Dec.

As noted somewhere, we'll start pulling together the 2024 meeting schedule sometime after TPAC 2023.

@martinthomson martinthomson unpinned this issue Nov 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
logistics Hashing out meeting logistics
Projects
None yet
Development

No branches or pull requests

5 participants