-
Notifications
You must be signed in to change notification settings - Fork 133
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
TSC Meeting frequency discusion #286
Comments
I like the idea of a month to start. We can trial this frequency for a while and in, say, six months check in with everyone to see how it's working. I also like once a month because it lines up with our previous schedule, i.e. there are no new times introduced, only times removed. Related, we should figure something out for #198 though. |
I definitely prefer a monthly schedule |
In terms of #198, looking at the meeting time options rated by the CTC members, 2 hours later than the current time is worse for some and better for others. 0 UTC is also better for a number of people but also not possible for a number of people. Two options would be those shown below. Please suggest others if you think there is another one we should consider based on the CTC availability spreadsheet.
|
Both options work well for me, I'm fine with whichever is easier for everyone else. |
Based on discussion in last TSC meeting unless we hear objections in the next week, we are going to move to monthly. @nodejs/tsc can you those of you for which the current time is a challenge please comment ? We'd like to consider if we need to move but we need to know if its going to make a difference before do that as it will affect attendance of some of the existing regular attendees. |
Monthly makes sense based on recent experience. Of the two options above I prefer the 20/22 UTC slots slightly. Thanks! |
We agreed on monthly, closing. |
It was suggested in the issue for the last meeting by @jasnell that we reduce the meeting frequency to
once a month.
This issue is to discuss and come to an agreement on what we want the meeting frequency to be going forward.
The text was updated successfully, but these errors were encountered: