Skip to content
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

Node.js Technical Steering Committee (TSC) Meeting 2023-10-25 #1457

Closed
mhdawson opened this issue Oct 23, 2023 · 3 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2023-10-25 #1457

mhdawson opened this issue Oct 23, 2023 · 3 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Oct 23, 2023

Time

UTC Wed 25-Oct-2023 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Wed 25-Oct-2023 08:00 (08:00 AM)
US / Mountain Wed 25-Oct-2023 09:00 (09:00 AM)
US / Central Wed 25-Oct-2023 10:00 (10:00 AM)
US / Eastern Wed 25-Oct-2023 11:00 (11:00 AM)
EU / Western Wed 25-Oct-2023 16:00 (04:00 PM)
EU / Central Wed 25-Oct-2023 17:00 (05:00 PM)
EU / Eastern Wed 25-Oct-2023 18:00 (06:00 PM)
Moscow Wed 25-Oct-2023 18:00 (06:00 PM)
Chennai Wed 25-Oct-2023 20:30 (08:30 PM)
Hangzhou Wed 25-Oct-2023 23:00 (11:00 PM)
Tokyo Thu 26-Oct-2023 00:00 (12:00 AM)
Sydney Thu 26-Oct-2023 02:00 (02:00 AM)

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

  • navigator object breaks projects in v21.0.0 #50269
  • test: set test-fs-watch as flaky #50250
  • Revert "doc: promote fetch/webstreams from experimental to stable" #49867
  • tools: add package-lock when installing npm dependency #49747
  • The env var NODE_V8_COVERAGE intermittently causes the process to hang #49344
  • Support for file-system based persistent code cache in user-land module loaders #47472

nodejs/TSC

  • Amir From OSTIF: Discuss Node.js Security Audit #1454
    • covered last week

nodejs/admin

  • Have a mascot #828 (At end Private update from Foundation Staff)
  • Create nodejs/socket repository for Node.js implementation of Cloudflare's Socket API #826

Invited

Observers/Guests

Notes

The agenda comes from issues labelled with tsc-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

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.


Invitees

Please use the following emoji reactions in this post to indicate your
availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure yet
@mhdawson mhdawson self-assigned this Oct 23, 2023
@mhdawson
Copy link
Member Author

Adding this to agenda as well -#1459

@Uzlopak
Copy link

Uzlopak commented Oct 25, 2023

Regarding navigator I wanted to add following aspect to be considered:

The MDN is not a reliable source regarding the deprecation of the navigator properties. They only mark it as deprecated in the MDN because they can not mark something as "avoid as best as you can".

Also some properties are not spec compliant to return an empty string. See e.g. whatwg/html#7762

Even Typescript considers the deprecation of e.g. navigator.platform as a bug:
microsoft/TypeScript#49683

See also for more insights regarding the inability to mark navigator properties in MDN as "avoid at all costs" and thus following back to mark them as deprecated.
mdn/content#14429

Also the part of whatwg and its test suite:
https://github.com/web-platform-tests/wpt/blob/72e06c82933e9d324881b756a3fc48a3cac1c09d/workers/interfaces/WorkerUtils/navigator

@mhdawson
Copy link
Member Author

PR for minutes - #1460

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants