Node.js Foundation Modules Team Meeting 2020-01-15

[mhdawson]

Time

UTC Wed 15-Jan-2020 20:00 (08:00 PM):

Timezone	Date/Time
US / Pacific	Wed 15-Jan-2020 12:00 (12:00 PM)
US / Mountain	Wed 15-Jan-2020 13:00 (01:00 PM)
US / Central	Wed 15-Jan-2020 14:00 (02:00 PM)
US / Eastern	Wed 15-Jan-2020 15:00 (03:00 PM)
London	Wed 15-Jan-2020 20:00 (08:00 PM)
Amsterdam	Wed 15-Jan-2020 21:00 (09:00 PM)
Moscow	Wed 15-Jan-2020 23:00 (11:00 PM)
Chennai	Thu 16-Jan-2020 01:30 (01:30 AM)
Hangzhou	Thu 16-Jan-2020 04:00 (04:00 AM)
Tokyo	Thu 16-Jan-2020 05:00 (05:00 AM)
Sydney	Thu 16-Jan-2020 07:00 (07:00 AM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Modules%20Team+Meeting+2020-01-15&iso=20200115T20
• or http://www.wolframalpha.com/input/?i=08PM+UTC%2C+Jan+15%2C+2020+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1odxHwuFIuZsbaQ9SgH23riGiwvKg0y2pHlTwdaIOIbE/edit

Agenda

Extracted from modules-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

• WIP: Move ESM loaders to worker thread #31229
• esm: implement import.meta.resolve #31032
• module: unflag conditional exports #31001

nodejs/modules

• Table source type detection #465
• Stabilizing the resolver #451
• unflagging in 12.x LTS #450
• ERR_REQUIRE_ESM LTS backport #468
• Chartering the Modules team #412
• Loader Hooks #351
• Patch/Instrument a module #339

Invited

• Modules team: @nodejs/modules

Observers/Guests

Notes

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.

Joining the meeting

• link for participants: https://zoom.us/j/656987750
• For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live

[jkrems]

Are we back to the original schedule? I'm not sure if we ended up moving to the other week..?

[MylesBorins]

We never changed the schedule. if we want to change the time we should run a doodle and explore many options. Last week's meeting was an out of band call agreed upon before the holidays so we could sync and not miss LTS shipping deadlines

…

On Mon, Jan 13, 2020, 11:21 AM Jan Olaf Krems ***@***.***> wrote: Are we back to the original schedule? I'm not sure if we ended up moving to the other week..? — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#466?email_source=notifications&email_token=AADZYV6YTWHLSN6FC4O2OMLQ5SIIRA5CNFSM4KGCBTQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIZKW4Q#issuecomment-573746034>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADZYV7KAETPBZYEERZ72DTQ5SIIRANCNFSM4KGCBTQQ> .

[ljharb]

It seems, though, like it was agreed upon in the 12/18 meeting and never posted to or discussed on GitHub :-/ (altho obv i may have just missed that too)

[jkrems]

Maybe it should be the first agenda item for this one and we'd go from there? I think we could definitely use a meeting this week, given the release timing(s).

[MylesBorins]

I've personally never agreed to a permanent time change, shifting a week would not work for me and I've voiced this before. If the notes say otherwise that is a mistake. We agreed to having an out of band meeting not a permanent shift. I think it would be very reasonable for us to do a new survey of committee members

…

On Mon, Jan 13, 2020 at 11:49 AM Jan Olaf Krems ***@***.***> wrote: Maybe it should be the first agenda item for this one and we'd go from there? I think we could definitely use a meeting this week, given the release timing(s). — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#466?email_source=notifications&email_token=AADZYVYYQD6QPRLD2LMSLILQ5SLQPA5CNFSM4KGCBTQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIZOCPY#issuecomment-573759807>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADZYVY7F3SKKHJBVYRSSNDQ5SLQPANCNFSM4KGCBTQQ> .