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

August 2022 Meeting #66

Closed
seanturner opened this issue Jun 27, 2022 · 7 comments
Closed

August 2022 Meeting #66

seanturner opened this issue Jun 27, 2022 · 7 comments
Labels
logistics Hashing out meeting logistics

Comments

@seanturner
Copy link
Contributor

Please fill out this poll to indicate your availability. We would like to make the decision by July 8th so please indicate your preferences by then.

Aram and I would like to schedule the next patcg meeting for either the 1st Tuesday/Thursday (2/4) or the 2nd Tuesday/Thursday (9/11) of August; sometime zones will be 3/5 and 10/12. We will again have the two 3 hour sessions. As agreed, we are going to rotate the time of day around so that at some point everybody will need to be up early/late. This time we are proposing 2400 CET / 2300BST / 2200 UTC / 1800 EST / 1500 PST / 0600 Singapore (next day) / 0800 AEST (next day). An early set of apologies to those who have bad start times.

@seanturner seanturner added the logistics Hashing out meeting logistics label Jun 27, 2022
@jaylett-annalect
Copy link
Contributor

We appear to be favouring US timezones; this will make three meetings in five crossing midnight in Europe. That wasn't what I expected given the discussion following #19 (comment)

@seanturner
Copy link
Contributor Author

We have used three meeting times (roughly)* for four meetings (excluding the 2021 TPAC):

  • 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

My plan was to rotate through them. I see now that when picking this meeting's time, I went back to time B (1st/3rd meeting's time) when I should probably have gone to time C (2nd meeting's time). Going forward, I'll cycle through these times, i.e., in Sept/Oct we'll meet at time C, the next meeting will be time A, then time B, and so on.

  • With daylight saving time followed in some timezones and not others the times listed here might move and hour or here or there.

@seanturner
Copy link
Contributor Author

This is a reminder to please fill out the poll for the August meeting. Aram and I would like to be able to decide sometime around the 8th of July.

Thanks for those who have filled out the poll.

@eriktaubeneck
Copy link
Contributor

@seanturner looks like it's pretty even between the two weeks (and comes down to @bmayd, @michaelkleber, and myself OR @rmirisola, @wseltzer, and @jaylett-annalect.)

Most importantly, though, it would be great to lock in the date!

@seanturner
Copy link
Contributor Author

After talking with Aram, we settled on the latter dates: August 9 & 11. I will get the formal announcement out soonest.

@AramZS
Copy link
Contributor

AramZS commented Jul 29, 2022

@seanturner
Copy link
Contributor Author

Thanks for all those that participated.

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

4 participants