Node.js Technical Steering Committee (TSC) Meeting 2025-01-15

[mhdawson]

Time

UTC Wed 15-Jan-2025 15:00 (03:00 PM):

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

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2025-01-15&iso=20250115T1500
• or https://www.wolframalpha.com/input/?i=03PM+UTC%2C+Jan+15%2C+2025+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1xFs-RFqX0PmNLDguZdoXC-C5SGcTbzEte_Uq65zc--o/edit

Agenda

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

nodejs/node

• doc: change smartos support type to experimental #56220
• test: improve zlib tests #55716

nodejs/TSC

• Status of smartOS support and what future holds #1663
• Clarify the Charter so that contractors are explicity counted as affialiated #1650
• Let's talk about the CI situation #1614

Invited

• Antoine du Hamel @aduh95 (voting member)
• Yagiz Nizipli @anonrig (voting member)
• Benjamin Gruenbaum @benjamingr (voting member)
• Ruben Bridgewater @BridgeAR (voting member)
• Gireesh Punathil @gireeshpunathil (voting member)
• James Snell @jasnell (voting member)
• Joyee Cheung @joyeecheung (voting member)
• Chengzhong Wu @legendecas (voting member)
• Marco Ippolito @marco-ippolito (voting member)
• Matteo Collina @mcollina (voting member)
• Michael Dawson @mhdawson (voting member)
• Rafael Gonzaga @RafaelGSS (voting member)
• Richard Lau @richardlau (voting member)
• Robert Nagy @ronag (voting member)
• Ruy Adorno @ruyadorno (voting member)
• Paolo Insogna @ShogunPanda (voting member)
• Michaël Zasso @targos (voting member)
• Tobias Nießen @tniessen (voting member)
• Anatoli Papirovski @apapirovski (regular member)
• Beth Griggs @BethGriggs (regular member)
• Ben Noordhuis @bnoordhuis (regular member)
• Colin Ihrig @cjihrig (regular member)
• Geoffrey Booth @GeoffreyBooth (regular member)
• Moshe Atlow @MoLow (regular member)
• Shelley Vohr @codebytere (regular member)
• Rich Trott @Trott (regular member)
• Joe Sepi @joesepi (Guest - Node.js CPC rep)

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

[mcollina]

cc @rginn

[mhdawson]

The plan is for most of this meeting to be a private session with @rginn.

[bahamat]

Since #1663 is still on the agenda, I will be attending.

[mcollina]

@bahamat I don't think that would be covered today. This session is mostly a private session with @rginn. That's a long discussion and probably worth a whole meeting.

[jclulow]

@bahamat I don't think that would be covered today. This session is mostly a private session with @rginn. That's a long discussion and probably worth a whole meeting.

Would it be possible to constrain the agenda list in the issue, then, to the items that will actually be discussed?! I got up at 0630 US/Pacific to be in this meeting on the basis that the illumos ("SmartOS") stuff is on the agenda...

[bahamat]

@mcollina Then it should probably be removed from the agenda? Also, from the other thread where all of this started, people have stated that things seem fine as-is.

I'm not really sure what we are expected to do other than attend if it's listed on the agenda. There's no other way for us to know if/when it will be discussed.

[joyeecheung]

I think we should just remove it from this meeting, even if we are still going to discuss the issue, it won't be in this one as we'll mostly talk with @rginn about other stuff in this meeting, which is more urgent and we don't get @rginn come to the meeting regularly.

[kriscoleman]

A colleague and I are interested in observing these meetings. We work in the cybersecurity space and are trying to make advances with node provenance.

Is it possible we could gain an invite and the password to the zoom meetings?

[marco-ippolito]

A colleague and I are interested in observing these meetings. We work in the cybersecurity space and are trying to make advances with node provenance.

Is it possible we could gain an invite and the password to the zoom meetings?

It is possible to watch recordings of the meetings https://www.youtube.com/@nodejs-foundation/streams
I don't think it's possible to participate unless invited.

[jclulow]

As per discussion in the meeting: @mhdawson is going to set up another session later with at least @bahamat and myself about the illumos/SmartOS situation.

Thanks all!

[anonrig]

I think we should just remove it from this meeting, even if we are still going to discuss the issue, it won't be in this one as we'll mostly talk with @rginn about other stuff in this meeting, which is more urgent and we don't get @rginn come to the meeting regularly.

I'm waiting on this discussion to proceed to open a voting session. Removing it from agenda isn't a path forward for any dispute.

[mcollina]

We can cover SmartOS in the next meeting.

[joyeecheung]

Removing it from agenda isn't a path forward for any dispute.

I was talking about removing it from this meeting because we clearly would not spend time talking about it on this meeting on January 15, as we already set out to discuss other stuff. And indeed keeping it the agenda only led to us wasting 10 minutes talking about the agenda and not the issue itself, while that time could've been spent discussing other stuff that we specifically invited people from the foundation for in this meeting.

[mcollina]

I want to apologize to @bahamat and @jclulow on behalf of the project. We should have been make it way clearer if we were talking about Illumos in today’s meeting or not.

@mhdawson message was clear enough, and we would have needed to update the OP.

[rginn]

+1 for our SmartOS friends @bahamat and @jclulow. I’m so sorry for the scheduling mixup today. I’m also on Pacific Time, so I get it. Today I also learned about inviting guests around specific agenda items. I agree that the Node.js public meeting information is confusing, and we’ll work with the team on making updates on the website and calendar, in addition to the project posts on GitHub.

[mhdawson]

We used the full meeting for a private session this week so no minutes, closing.