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

Added minutes of 2023-01-18 meeting #1332

Merged
merged 2 commits into from
Jan 18, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
77 changes: 77 additions & 0 deletions meetings/2023-01-18.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
# Node.js Technical Steering Committee (TSC) Meeting 2023-01-18

## Links

* **Recording**: <https://www.youtube.com/watch?v=UuV-rRMkKvE>
* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1331>
* **Minutes Google Doc**: <https://docs.google.com/document/d/1ZrEQooH2yp9GpPe-j0SDBpR8-kOihNIANM-v5L_PErg/edit>

## Present

* Antoine du Hamel @aduh95 (TSC) Matteo Collina @mcollina (TSC)
mcollina marked this conversation as resolved.
Show resolved Hide resolved
* Joyee Cheung @joyeecheung (TSC)
* Chengzhong Wu @legendecas (TSC)
* Robert Nagy @ronag (TSC)
* Darshan Sen @RaisinTen (TSC)
* Michaël Zasso @targos (TSC)
* Gireesh Punathil @gireeshpunathil (TSC)
* Ruben Bridgewater @BridgeAR (TSC)
* Tobias Nießen @tniessen (TSC)

## Agenda

### Announcements

* OpenJS Collaborator [OpenJS World / Linux Foundation Open Source Summit 2023](https://events.linuxfoundation.org/open-source-summit-north-america/), 10-12 May, Vancouver, Canada
* (ronag) Performance WG <https://github.com/nodejs/performance> - looks promising and good work!

### CPC and Board Meeting Updates

Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting.

* OpenJS World as part of Open Source Summit
* Project Directed funding <https://github.com/openjs-foundation/cross-project-council/pull/999>.
* CoC updates <https://github.com/openjs-foundation/cross-project-council/pull/984>.

### nodejs/node

* Expose Undici's ProxyAgent and setGlobalDispatcher within Node [#43187](https://github.com/nodejs/node/issues/43187)
* ronag: This comes from the requirement of making fetch() proxy-aware. How can we achieve this proxying behavior? There are also other ways - support environment variables (<https://github.com/nodejs/undici/issues/1650>)?
* mcollina: Support for SOCK4/SOCK5 in Undici is missing atm but available in 3rd party modules.
* antoine: Deno and Python support it. Java doesn’t.
* tobias: Does undici use CONNECT for proxying?
* ronag: yes
* ronag: Should we just implement HTTP\_PROXY env var? That would make the problem go away.
* matteo: Deno does it like that.
* matteo: Wrangler (CloudFlare CLI) also supports it.
* tobias: Is there any chance that implicitly proxying in undici based on the env var might break packages that explicitly proxy based on the same env var?
* matteo: add HTTP\_PROXY and NO\_PROXY environs support in undici and discuss the semver-ness

* ronag: how urgent is <https://github.com/nodejs/node/issues/46234> ?
* mcollina: revert and backport everywhere

### nodejs/llhttp

* Handle extra spaces in status line [#216](https://github.com/nodejs/llhttp/pull/216)
* ronag: <https://github.com/nodejs/llhttp/pull/216>
* ronag: we have a maintenance issue with llhttp. Not a security issue atm.
* mcollina: I agree with your worry
* mcollina: Paolo Insogna has been maintain llhttp so far
* mcollina: we can do all the changes in one big semver-major change or treat them as minors
* mcollina: open a public issue to talk about it
* joyee: llhttp is supposed to be easier to maintain than a pure c/c++ codebase
* mcollina: the previous codebase is hard to maintain
* joyee: is it about the dsl part?
* mcollina: it’s well written. it’s more about lacking of documentation on internal library (<https://github.com/nodejs/llparse>).
* joyee: is it still possible to reachout to Fedor to document the project?
* mcollina: i can reach out to Fedor for documentation with a contributor guide. I will also open an issue on having a meeting about the new RFC.

## Strategic Initiatives

Single executable: <https://github.com/nodejs/node/pull/46212> needs review

## Upcoming Meetings

* **Node.js Project Calendar**: <https://nodejs.org/calendar>

Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.