-
Notifications
You must be signed in to change notification settings - Fork 18
2025-03-12 Express Working Session #344
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
Comments
Had a conflict come up, will miss |
I will love to include (for visibility / small discussion): |
cc @RobinTail if you'd like to attend, the meet's in 15 mins if i'm not wrong |
I think in the end there was no meeting. Things happened at the last minute, and several members couldn't attend. If you're not on Slack, please join; that's where we communicate with the other members. |
@bjohansebas me and robin attended and had a small chat but no problem, we’ll try and make it to the next meet How can we join the slack server? |
Here you can join: |
Cc @RobinTail |
Btw, it's in the channel called 'express', given that several OpenJS projects are there. |
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
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: