-
-
Notifications
You must be signed in to change notification settings - Fork 16
meeting cadence should be offset by 1 week #10
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
Comments
OK, so it appears the benchmarking WG meets every three weeks, so if we want that time slot we too will need to meet every n weeks where |
I’m still not clear on why “one at a time” is a constraint, can’t we pay YouTube or something for the ability to do two streams at a time? |
fine for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our current meeting cadence conflicts with the benchmarking WG's meeting, which means we won't be able to stream on YouTube and may force some attendees into an awkward decision. 😄
However, I think our next meeting should stay on December 18, because the following Tuesday is a holiday.
Thereafter, I propose we offset the meeting schedule by one week to avoid further conflicts. So the next meeting after December 18 would be January 8.
Sound OK?
@nodejs/tooling
The text was updated successfully, but these errors were encountered: