-
Notifications
You must be signed in to change notification settings - Fork 134
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 Schedule #336
Comments
I am +1 with that. |
Considering that the majority of TSC meetings had been skipped lately and
that CTC meeting were moved to every third week, do you think it might make
sense to stick with every two weeks?
|
CTC was every other week, not every third week. My opinion only: I think given the current status of things, every week makes sense. We should have had a meeting this week. I look at it this way: At this point in time, I'd rather have a meeting schedule every week and have half of them canceled rather than have a meeting scheduled every other week and wish we had them more often. |
Yes, what @Trott said is the same what I had in mind. +1 to every week by default, cancelling on case-by-case basis would be better. |
+1 from me as well |
Sgtm.
I was definitely mixing up the schedule
…On Sep 7, 2017 9:10 PM, "Michael Dawson" ***@***.***> wrote:
+1 from me as well
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#336 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV2BRXoyLhAGIJ5vr0sXe7p-556_6ks5sgD-agaJpZM4PPQB_>
.
|
This was ratified at today's TSC meeting. The Node.js calendar has been updated too. |
There's a CTC meeting that had been scheduled for Wed. Sep 13 at UTC 20:00 this Wednesday (1 PM San Francisco, 4 PM New York, 10 PM Germany, 11 PM Moscow, Thu 1:30 AM India, Thu 4 AM China, Thu 5 AM Japan, Thu 6 AM Sydney).
I propose that we use that time for our meeting on that date.
At that meeting, I'd like this to be on the agenda (unless we can get consensus before the meeting, which would be awesome):
I propose that after that meeting, we have a meeting scheduled every week rotating between UTC 12:00, UTC 17:00, and UTC 22:00.
Those times were selected algorithmically based on the contents of the private spreadsheet of everyone's availability. If you think those times are terrible, consider updating your row in the spreadsheet!
The text was updated successfully, but these errors were encountered: