Express TC Meeting 04-08-2020

[dougwilson]

Who

The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:

Invited:

• @expressjs/express-tc
• @expressjs/triagers

When

Apr 8, 2020 - 23:30 UTC

Where

Zoom, broadcasting on YouTube Live

• Viewers: https://youtu.be/CWlOklAfiTY
• Participants: https://zoom.us/j/305917849

Agenda

• Security issue update
• Expressjs.com updates for 5.0, and further Express 4.18 / 5.0 updates (specific list coming on tuesday)
• Triage topics; ideally entire second half as much as we can get done. Ex "discuss direction and handling of some issues", "[how] to decide when an issue can be closed", "how [companies] could help support open source projects [...]?"

Propose other agenda topics which can be added to this list.

[gireeshpunathil]

I propose expressjs/express#4210 for TC's attention and action (of course, doesn't need to be on the agenda if it lands before)

[jonchurch]

I've opened a PR for a popular package express-async-errors that adds promise support to middleware/route handlers to help their users upgrade to Express v5.

I'd like to ask anyone involved in Express to take a look and help get a PR landed to provide a smooth transition to v5. This is a package I'm personally familiar with. The maintainer has been responsive and is asking for help getting things ready for v5. I'm sure there's more packages in the ecosystem that might need some help or a heads up with the release of v5, so I propose this small project as a trial for us helping get the word out to maintainers about impending changes.

[ghinks]

As a triager who has been looking at express-session I would like to talk over my findings and present a very small 2 minute bullet point style presentation of what I would like to do as prospective maintainer of this module.

[jonchurch]

I tried to add @davidmashe to the triage team but github told me they aren't part of the express org so I was unable to.

[Sushmeet]

Would be great to try and have a discussion as to how companies could help support open source projects.

[wesleytodd]

I tried to add @davidmashe to the triage team but github told me they aren't part of the express org so I was unable to.

I posted in the discussions area just to see how it works, but it looks like team maintainers can only add existing org users to a team, not people from outside the org.

Would be great to try and have a discussion as to how companies could help support open source projects.

This is a topic I would love to discuss. Do you think there are some express specific things you want to talk about? Or could we maybe have that conversation in a format more applicable to a wide audience, perhaps in the package maintenance working group?

[helio-frota]

Viewers: TBD

/me waiting, thanks in advance 👍

I'm back from PTO btw, but yeah with the limited time allocated to triage effort I'll keep learning, to be able help on jshttp repositories in the future.

[wesleytodd]

@helio-frota I sent Doug the recording and he will be uploading! Sorry we didn't have a stream because zoom to youtube is broken right now. Always feel free to join the zoom and just watch!

[helio-frota]

@wesleytodd no worries! thanks for the feedback btw 👍

[davidmashe]

@wesleytodd i accepted the expressjs team invitation! Thank you.

[jonchurch]

I noticed when we tried to go live on youtube with this meeting, zoom was linking out to an already existing meeting. https://www.youtube.com/watch?v=kE1mY_k5oW4

What's weird is that this the Release Working Group meeting, and I think maybe zoom updated the title to be Express TSC Meeting?

Not sure what's going on here, but I think we should get someone to look into this.

[dougwilson]

Hi everyone, I have the video uploaded now at https://youtu.be/CWlOklAfiTY ; apologies for the delay, as there was a medical emergency; everyone's OK. But it's uploaded and the description updated 🎉

As for the streaming, that is definitely strange; perhaps it is stuck to stream to a certain youtube account / video source, and when I try it it errors because I have a different Google/YouTube account than what Wes had. Not sure, but ideally we'll get this resolved for streaming live, and it would also mean the video would be there right away for viewing.

[jonchurch]

I've heard that it's an issue Node is aware of, and not limited to us. @mhdawson might know more

Also, @dougwilson I'm glad everyone is okay!!

[mhdawson]

I had run into that problem earlier and I talked to @brianwarner to have a ticket opened with Zoom. So far I've not seen any response. @brianwarner can we update the ticket again to see if we can get a response ?

[brianwarner]

I haven't gotten any response on the ticket yet. I pinged it last week, and will do it again.

What's interesting here is that Express is on a different Zoom account than the Node meetings, but that account can stream just fine to other YouTube channels. I'm wondering if maybe the issue is specific to the Node YouTube channel?

[mhdawson]

I think I fixed it by making the "stuck" video private in Youtube studio. The build WG meeting then streamed ok so hopefully its fixed.