-
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
2023 Meeting Schedule #89
Comments
Those July dates conflict with IETF 117. Otherwise, these are all so far out I can't see a problem. |
Funny IETF 117 wasn't in my calendar - fail. We could move it one week prior or after. After might be better? |
TPAC was just announced for 11-15 September in Sevilla, Spain. member-only announcement |
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. |
Agreed if what I proposed in September is right there, then yeah we would meet in person at TPAC. |
As discussed at the F2F meeting in Feb:
|
***LOCKED IN DATES ***
***LOCKED IN DATES *** REVISED TENTATIVE DATES
REVISED TENTATIVE DATES If the June meeting ends up being a F2F meeting, the timezones for the following meetings will be revisited. |
Because I can't remember the timezone letters to time translations, copying this from the referenced comment:
|
@seanturner The W3C PATCG calendar is showing me a start time of 03:00, not 02:00 for this meeting:
|
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. |
Thanks for clarifying. I mentioned it because the previous comment from jaylett-annalect indicated 0200 EDT:
|
On reflection that was talking about a specific historical one, so apologies for introducing that confusion. |
I find timezone hard so clarifying questions are always welcome ;) |
June meeting is F2F: patcg/admin#14 |
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.
|
I'll let this settle for a week and then I'll close it out. |
This works and happy to accommodate any schedule if folks want to make changes. |
Okay will submit meeting request today. |
Meeting announcements posted for Sept, Oct, and Dec. As noted somewhere, we'll start pulling together the 2024 meeting schedule sometime after TPAC 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. **
TENTATIVE DATES
The text was updated successfully, but these errors were encountered: