Closed github-actions[bot] closed 6 months ago
Some items in the agenda were duplicated, so I made a manual clean up. Should be check the automation tool that generates the list?
I would add two points
I would love to talk about Express releases too (for reference: https://github.com/expressjs/express/pull/5513) not just process documentation 🙂
Love to see these notes, thank you for sharing! I spent many years as a W3C standards contributor at Microsoft, and I currently run an org building many apps on Express. Would be happy to help if you're growing the TC.
Added the zoom link: https://zoom-lfx.platform.linuxfoundation.org/meeting/95266714809?password=f37cff1b-cb3a-4a21-9425-210e4714c72e
Sorry for the delay getting this all sorted. We will get better at this going forward.
@jdhiro You are always welcome to join. These meetings, while primary for the TC are open to everyone from the project/community. Especially for folks interested in becoming more involved!
Gist link to the minutes Raw content of minutes:
2024-03-04 Express TC Meeting Minutes
attendance: Wes Todd, Blake Embrey, Rand Mckinney, Jean Burellier, Ulises Gascon, Jon Church
Agenda:
Agenda items are currently pulled from issues tagged
top-priority
in the Discussions repoAnnouncements
4.18.3
released less than a week ago, has over 2 Million downloads so far.Recurring Meeting cadence
https://github.com/expressjs/discussions/issues/195
- There was has been discussion about the cadence being changed, and the attendance policy.
- Jonchurch brought up whether or not the existing TC is okay with the cadence and expectations, as it is a change from the less often meetings before.
Discussion:
- Is the expectation that the full TC attends every meeting?
- Rand agrees that its fair to have an inactivity policy, so long as it is not draconian.
- We don't need to lock on an inactivity policy right now, as we don't really intend to kick people out in the near term for being inactive while we are still figuring out cadence
Express LTS Strategy
https://github.com/expressjs/discussions/issues/196
- Jean says releasing Express v5 should be a prio
- What Node version do we want to support?
- Today v5 is Node v4 minimum supported
- Here is the Migration guide currently on the website for express 5 https://expressjs.com/en/guide/migrating-5.html
- There is an Express LTS issue with discussion about an LTS strategy https://github.com/expressjs/discussions/issues/196
- Wes sees v5 as a stepping stone, and suggests that we write an LTS policy doc, include that v5 is a unique case.
- jean suggests using v14 as the lowest support level for v5
- Ulisses, how long do we want to support v4?
- He would like to see it supported for years to come
- Wes says he'd like to see "no less than a year, ideally 2 years", talking about security patches.
- Jean says, 1 year of maintenance, 2 years of security updates
- Ulises says maybe consider sponsorship from companies who require longer support for security
Decision:
- Support Node 14 for Express 5
- Jean will open a PR with the LTS strategy discussed
Github Project
Wes created a Github Project to try out using it as a means to track work happening.
Security Update
- OpenJS Foundation has offered a Security Audit, the kickoff meeting happened already
- There are a lot of questions about what working with them entails, and they are flexible to work how the team wants to
- Wes suggests handing it off to the Security Working Group
- Security WG was created in https://github.com/expressjs/discussions/issues/165
- There will be a public part, streamed meetings. And a private component for WG members, so reports can be triaged in private before a fix is released.
Decision:
- Hand off the Audit to the Security WG.
Misc
Rand before he had to leave brought up that there is a lot of Documentation work which needs to be done. We're hoping to leverage the community to swarm on docs, once we know what needs to happen.
Action items agreed to include @sheplu opening a PR with LTS policy doc
@wesleytodd are you planning to upload the recording manually to youtube? We can close this issue once we do that.
Yes, and I will post a link and close this when I do.
@UlisesGascon do you have a link you can share to the spreadsheet you mentioned during the meeting?
@UlisesGascon do you have a link you can share to the spreadsheet you mentioned during the meeting?
Yep, this one.
I was also thinking that maybe we can land the meeting minutes as a markdown file in this repo? Example from Node.js TSC, it will give us the opportunity to better index, and also to modify the notes if needed with a PR :)
Recording: https://youtu.be/gojW4byXIog
Date/Time
Or in your local time:
Agenda
Extracted from top priority labelled issues and pull requests from expressjs/discussions prior to the meeting.
Invited
@expressjs/express-tc
Links
Joining the meeting