-
Notifications
You must be signed in to change notification settings - Fork 168
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
We should try an earlier CPC meeting time #599
Comments
Even though I'm US/Pacific time, the 6am would actually make it less likely that I have a meeting conflict. The 16:00 UTC is kind of prime normal meeting time for meetings with teams across the Atlantic. |
This time would likely work better for me as well so I am all for giving it a try! |
It's not great for me, but I can make it work. |
I can do the proposed time on the 18th. |
Adding my virtual +1 for this time slot to be considered in the future - but as I'm on vacation next week I won't be able to +1 in person. |
As I understand it, we are going to try this new time on Aug 18 at 9am ET. My question is what do we do beyond that? I think a one time thing isn't very meaningful. However, if we go to a 3 week rotation, it will interfere with the bi-weekly standards team meeting. Do we do a 4 week rotating cycle where the 2pm ET slot happens every other week and the 10am/12pm (ET) slot switches every other week? I hate scheduling meetings..... :/ |
Since it sounds likes its agreed I'll move the time in the calendar for the 18th. |
Seems like I cannot edit Foundation calendar events. @joesepi can you move it ? |
I dont believe I can either. Perhaps @brianwarner or @jorydotcom can? |
@joesepi, @brianwarner, @jorydotcom we should probably ensure that more CPC members are able to manage the calendar. |
I can move it. Unfortunately there are security restrictions on that particular calendar, where I can only allow people on the @linuxfoundation.org GSuite domain to make changes. I requested a change to this policy a few weeks back (this isn't the only calendar I'd like to be able to share broadly), I'll follow up and see where that landed. In the meantime, @rginn and @RRomoff also have full access to this calendar. |
Based on the discussion in todays meeting, we've decided to alternate an earlier time with the current later time. The time of today's meeting was not prohibitive to most of the usual attendees, however, we will try moving it one hour later to help with US West attendees. So the plan is to alternate between 10am ET and 2pm ET. Sorry to be ET centric. The question is when do we start this rotation. I propose we start immediately, which would mean next week would be another early meeting - 1400 UTC. And this way, the later time stays as it is in calendar.openjsf.org |
The week goes by fast. Tomorrows meeting is at its regularly scheduled 1600 UTC time. Let's discuss in the meeting and look to move to an earlier time in two weeks. Thanks. |
Closing in favor of new issue #634 |
Since time immemorial, the CPC has been meeting weekly, at a time that switches between 16:00 UTC and 18:00 UTC, This is morning/midday for North America, afternoon/evening for Europe, and middle of the night for Asia.
We should try a different time, and see how that goes. Specifically, I propose that we hold the meeting on 18 August 2020 at 13:00 UTC, rather than its previously planned time of 18:00 UTC. This would be:
The idea here would be to effectively see what happens: do we have fewer or additional participants showing up, thanks to the earlier time? I don't think there's necessarily a better way of testing this except by trying. Based on the experience we can better figure out whether the meeting times should be changed going forward.
The text was updated successfully, but these errors were encountered: