-
Notifications
You must be signed in to change notification settings - Fork 78
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
Revisit meetings frequency #426
Comments
@mhdawson we decided to go back to bi-weekly meetings, with the first 15-ish minutes dedicated to updates on issues labeled to the WG and the remaining time dedicated to deep dive on a specific topic (and occasional one-off deep dives when needed). Two questions wrt the automated meeting issue creation: 1) can we fetch issues from multiple labels when creating the agenda? 2) can we disable the deep dive issue creation so it doesn't create for next week? also cc @nodejs/diagnostics for awareness |
I'll remove the calendar entry for the deep dive issue. In terms of labels, the tool currently only supports a single one for generating the meeting issue. |
Calendar entry removed |
Closing as the frequency has been reduced. We can open another issue if we need to go back to weekly. |
What do folks think about the current frequency of meetings we have? We've been having weekly meetings for a while now with the goal of working on the Users Journey documentation every other week, and as a result we made great progress on it, with the first "version" almost finished (we'll probably finish it today if it's not finished already). With the goal being achieved, I'd like to suggest we move back to bi-weekly meetings, alternating between deep dives and regular meetings, with the possibility of scheduling one-off deep dives when necessary.
The text was updated successfully, but these errors were encountered: