-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
2024-04-29 Express TC Meeting #232
Comments
Unfortunately, I won't be able to attend this meeting |
It would be awesome if we could automate docs for routine minor version releases. I'm imagining a GH action or workflow that would create a PR similar to expressjs/expressjs.com#1492 for any new release. Not sure how much work that would be, or if there is some reason not to do it....? |
I will like to include #233 in the agenda! |
Also I will like to mention #227 in the announcement section :) |
Also, lets make a public update about the audit (expressjs/security-wg#6) (TBC) and discuss about the OSSF Scorecard details and priorities (see cc: @inigomarquinez @carpasse) |
Adding also expressjs/expressjs.com#1500 to the agenda :) |
expressjs/express#5623 for agenda, mostly a last call for dissent |
Updated the Agenda w/ ad hoc items from TC in comments here |
Lets also see if we have time for this one: jshttp/fresh#38 |
We cannot get the stream started because of the LFX dashboard doesn't have the meeting in there. But we will upload after. |
Date/Time
Or in your local time:
Agenda
Announcements / Updates:
Extracted from tc agenda labelled issues and pull requests from expressjs/discussions prior to the meeting.
Ad Hoc Added in comments:
Invited
This meeting is open for anyone who wants to attend. Reminder to follow our Code of Conduct.
@expressjs/express-tc
@expressjs/triagers
@expressjs/security-wg
Links
Joining the meeting
The text was updated successfully, but these errors were encountered: