-
Notifications
You must be signed in to change notification settings - Fork 15
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-03-13 Express TC Meeting #214
Comments
Ok, well I got the bot running, but it made next weeks issue not tomorrows lol. I can figure out what new bug there is in the I thought we had said we would do every other week in the original issue but the calendar has it every week. I think that might be a good thing to get started, but it deviates from what we had originally said. Are we alright with that? |
The issue body's date and times are accurate now for Wednesday March 13th, for anyone seeing this. |
I thought this was going to be at the same time as last week's meeting, but it's now showing 2pm PT. Maybe that's due to the shift to DST? Unfortunately, I have a conflict at that time for the first half-hour. I will join asap and I'd ask that #211 be discussed in the last half of the meeting, when I join, if possible. Thanks. |
I also thought we were going to alternate times. I will update the agenda to also have a "discuss meeting schedule" thing again. We can wait until you are on the call to do that @crandmck. |
I will be able to attend 🙋♂️ |
Too bad the times were wrong. But I forgive you Wes |
The meeting cut us off. I have no idea why but I can't rejoin with the same link? |
@bensternthal is this a features of the settings we use for these meetings? |
Aw missed yall. Livesite responsibilities kept me away today |
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
The text was updated successfully, but these errors were encountered: