-
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
Monthly meeting suggestion #602
Comments
+1 |
It does tend to slow down around the holidays, but also the group has just not been super active lately so turning the meeting frequency down a bit could be reasonable. I think we should do something about expanding the group to get more activity happening though. I don't think it's inactive for a lack of things to do, just a lack of people doing them. 🤔 |
@Qard Absolutely. I think we could clean up the README and perhaps set up new goals. Pretty much the same as we are doing for Security (nodejs/security-wg#846). But, until we have this issue and people engaging, I'm still +1 to monthly meetings. |
I’m still interested in joining and attending the meeting even though I couldn’t in the past month. Out of topic but seemed like a good place to ask: I’m having some trouble keeping in track of future meetings, and issues created are not super helpful. Any recommendations? |
+1 |
To be clear, I'm +1 to this. I just also think we should do something to get the activity back up. 😅 |
+1 |
@mhdawson could you do it for us? |
I've changed it to every 4 weeks as otherwise it may rotate and then conflict with other meetings. |
I would like to propose changing our meeting schedule from bi-weekly to monthly meetings. The reason is that very often we don't have much to discuss in that short timeframe.
Of the last 5 meetings, 4 were canceled:
Hopefully, this group will get more traction over the year, but until we have many items on the agenda, I believe it's reasonable to meet once per month. What do you guys think about it? @nodejs/diagnostics
The text was updated successfully, but these errors were encountered: