-
Notifications
You must be signed in to change notification settings - Fork 166
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
Node.js Build WorkGroup Meeting 2020-03-03 #2198
Comments
Even if it's just for awareness and there's no action taken or discussion, I wouldn't mind having nodejs/commit-queue#1 on the agenda. |
@jkleinsc & @ckerr, @davidstanke. I'm hoping you've already seen this but just in case an FYI. Hoping we'll see you in the meeting. Sorry for not thinking to add this notification earlier. |
👍 Planning on being there. |
Hey, I'm afraid I'm distracted these days... dealing with coronavirus
impact on various events I'm supporting. I'm hopeful I can dive back in
soon. Thanks for the reminder tho!
…On Tue, Mar 3, 2020 at 3:15 PM John Kleinschmidt ***@***.***> wrote:
👍 Planning on being there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2198?email_source=notifications&email_token=AAQQ3D3ULUL3H2JFPQOLLETRFVQNFA5CNFSM4K4FBZG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENU7LOQ#issuecomment-594146746>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQQ3DZIOQ5RDEQPJEMN5OLRFVQNFANCNFSM4K4FBZGQ>
.
|
PR for minutes: #2200 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Time
UTC Tue 03-Mar-2020 21:00 (09:00 PM):
Or in your local time:
Links
Agenda
Extracted from build-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/build
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
build-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
The text was updated successfully, but these errors were encountered: