-
Notifications
You must be signed in to change notification settings - Fork 134
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
Coordinating nodejs security audit report finalization and publication #1546
Comments
Plan is to covery this in the private section of the TSC meeting on May 8 |
Hello Michael and node TSC. I am terribly sorry for missing this meeting. The reason is I made a mistake and got my time zones mixed up (I'm on the west coast for the next few days and the calendar didn't update). Is it possible to participate in next week's TSC meeting? Sorry about that again! I know the group's time is valuable and didn't mean to keep you waiting. |
We'll plan to have you in next weeks TSC meeting. See you then. |
Removing from the agenda until we get the report. |
The report has been shared through email, and discussed a few times in the TSC meeting. I'm going to go ahead and close this issue. Please let me know if that was not the right thing to do. |
The objective is to collaborate with the nodejs TSC to close out the report finalization and publication per: nodejs/security-wg#1159. We will review the report and discuss anything needed.
The text was updated successfully, but these errors were encountered: