UTC Wed 21-Oct-2020 19:00 (07:00 PM):
| Timezone | Date/Time |
|---------------|-----------------------|
| US / Pacific | Wed 21-Oct-2020 12:00 (12:00 PM) |
| US / Mountain | Wed 21-Oct-2020 13:00 (01:00 PM) |
| US / Central | Wed 21-Oct-2020 14:00 (02:00 PM) |
| US / Eastern | Wed 21-Oct-2020 15:00 (03:00 PM) |
| EU / Western | Wed 21-Oct-2020 20:00 (08:00 PM) |
| EU / Central | Wed 21-Oct-2020 21:00 (09:00 PM) |
| EU / Eastern | Wed 21-Oct-2020 22:00 (10:00 PM) |
| Moscow | Wed 21-Oct-2020 22:00 (10:00 PM) |
| Chennai | Thu 22-Oct-2020 00:30 (12:30 AM) |
| Hangzhou | Thu 22-Oct-2020 03:00 (03:00 AM) |
| Tokyo | Thu 22-Oct-2020 04:00 (04:00 AM) |
| Sydney | Thu 22-Oct-2020 06:00 (06:00 AM) |
Or in your local time:
Extracted from modules-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
The agenda comes from issues labelled with modules-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Doesn't look like we have much of an agenda this week.
one thing we only briefly go to last week was a meta discussion about the ongoing role of the modules team and if it were perhaps time to spin the group down.
Should we dedicate this week's meeting to that discussion topic?
That sounds like a good plan to me.
Perhaps we can also include some discussion about the experimental status of the modules implementation at the same time, as the group is still responsible for this as well.
@guybedford want to make a tracking issue for that if there isn't one yet?
Sure, I've posted https://github.com/nodejs/modules/issues/564.
Most helpful comment
Doesn't look like we have much of an agenda this week.
one thing we only briefly go to last week was a meta discussion about the ongoing role of the modules team and if it were perhaps time to spin the group down.
Should we dedicate this week's meeting to that discussion topic?