-
Notifications
You must be signed in to change notification settings - Fork 17
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
Comments
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) |
We have used three meeting times (roughly)* for four meetings (excluding the 2021 TPAC):
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.
|
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. |
@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! |
After talking with Aram, we settled on the latter dates: August 9 & 11. I will get the formal announcement out soonest. |
Thanks for all those that participated. |
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.
The text was updated successfully, but these errors were encountered: