Node.js Foundation Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-12-12 #639
Comments
|
I'll be chairing this meeting if no one objects. |
|
The datetimes are not in English 😮 |
|
@thefourtheye fixed! Seems that make-node-meeting generates times in whatever locale is set! |
|
Not sure why the meeting was not auto generated. Good to see Matteo created it. Back home but its late so I'll check tomorrow. |
|
I'll be at the meeting but @mcollina happy to have you chair anyway. |
|
I may not be able to make it tomorrow as I'll be in ECMA meetings nodejs/node#24811 I'm +1 on landing and added comments in thread #476 Board meeting is on Thursday, will have a full update afterwards. strategic initiatives updateModulesQuite a bit of discussion happening right now in two break out proposals https://github.com/GeoffreyBooth/node-import-file-specifier-resolution-proposal A proposal to utilize metadata to determine the module type of a package allowing for us to support importing both esm and cjs modules. https://github.com/jkrems/proposal-pkg-exports/ An alternative approach to the current Node.js resolution algorithm. Meta Data in package.json would be used to identify exports. Compatible with import-map proposal GovernanceWe started a project board to track responsibilities of various stakeholders within the proposed foundation. We will be using this artifact to help determine how many Top-Level committees there will be and what they will be responsible for. https://github.com/nodejs/bootstrap/projects/1 Open Web StandardsIntroducing a namespace to node. This has implications to other runtimes. Dynamic Modules proposal. This proposal would allow spec compliant named imports from CJS modules. TC39 and V8 want to ensure we have consensus within node before changes can land upstream. If you have concerns please raise them before next Wednesday (next modules team meeting) |
|
Feeling a bit unwell, gona try to get some extra sleep. Sorry folks. |
|
Bit of a rough night 😕 ... I've repeated my comment from last week re nodejs/node#24267 on the issue as well. |
|
(Sorry, I got kicked out repeatedly because of connection issues :/) |
|
PR for minutes: #640 |
|
Moderation Team Updates: No significant events this week. @nodejs/tsc @nodejs/community-committee @nodejs/moderation |
Time
UTC Mer 12-Dic-2018 16:00 (04:00 pm):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/nodejs.org
nodejs/TSC
nodejs/community-committee
Invited
Notes
The agenda comes from issues labelled with
tsc-agendaacross 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
Zoom link: https://zoom.us/j/611357642
Regular password
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: