-
Notifications
You must be signed in to change notification settings - Fork 3
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
Regular monthly meeting alternating between American and Asian time zones? #54
Comments
Both these time slots work for me 👍 |
Perfect with me!
Stewart Heitmann
***@***.***
… On 23 Nov 2021, at 8:34 pm, Ankur Sinha ***@***.***> wrote:
Hi @OCNS/software-wg <https://github.com/orgs/OCNS/teams/software-wg>
I was wondering what folks thought of having a regular meeting time set up for each month so we can block it off in our calendars early?
At the moment we do a whenisgood each time, but that takes time and availability often changes while it's being populated by everyone.
So I propose that
we set up a regular meeting time for a one hour meeting every month
this time alternates between a time friendly for the American time zone, and a time friendly for the Asian time zones.
So, starting from January, how is the second Monday each month at:
1700 UTC
0800 UTC
What do you think?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub <#54>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEN6U4UGHUZ7P44AW2TEIFLUNNNZHANCNFSM5ITA3VMA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Both times work for me. |
the 8am might not work for me (school run) but not necessarily a reason to not do it ... |
Yeh, I think some of us will be able to make one and not the other sometimes, but as long as there are a few of us who overlap to keep the alternating meetings connected in a way, we should be fine. (Just to be clear: I'm suggesting that in Jan we do 0800 UTC, then in Feb we do 1700 UTC, March 0800 UTC and so on---so most of us should at least be able to attend one meeting that suits them) |
That works.
… On Nov 23, 2021, at 12:05 PM, Ankur Sinha ***@***.***> wrote:
Yeh, I think some of us will be able to make one and not the other sometimes, but as long as there are a few of us who overlap to keep the alternating meetings connected in a way, we should be fine.
(Just to be clear: I'm suggesting that in Jan we do 0800 UTC, then in Feb we do 1700 UTC, March 0900 UTC and so on---so most of us should at least be able to attend one meeting that suits them)
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Excellent suggestion. I'll be there half the time! |
Great, I'll leave this open for a few more days for others to chime in, and then I can set up a recurring meeting reminder for us somewhere. 👍 |
OK, since we haven't received any other feedback, this is now good to go. We will meet on the second monday each month, and the time will alternate between 1700 UTC and 0800 UTC. I'll update our blog etc., and open a new ticket for the January meeting. |
Hi @OCNS/software-wg
I was wondering what folks thought of having a regular meeting time set up for each month so we can block it off in our calendars early?
At the moment we do a whenisgood each time, but that takes time and availability often changes while it's being populated by everyone.
So I propose that
So, starting from January, how is the second Monday each month at:
What do you think?
The text was updated successfully, but these errors were encountered: