Skip to content
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 Foundation Security WorkGroup Meeting 2020-01-27 #625

Closed
mhdawson opened this issue Jan 22, 2020 · 5 comments
Closed

Node.js Foundation Security WorkGroup Meeting 2020-01-27 #625

mhdawson opened this issue Jan 22, 2020 · 5 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Jan 22, 2020

Time

UTC Mon 27-Jan-2020 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Mon 27-Jan-2020 08:00 (08:00 AM)
US / Mountain Mon 27-Jan-2020 09:00 (09:00 AM)
US / Central Mon 27-Jan-2020 10:00 (10:00 AM)
US / Eastern Mon 27-Jan-2020 11:00 (11:00 AM)
London Mon 27-Jan-2020 16:00 (04:00 PM)
Amsterdam Mon 27-Jan-2020 17:00 (05:00 PM)
Moscow Mon 27-Jan-2020 19:00 (07:00 PM)
Chennai Mon 27-Jan-2020 21:30 (09:30 PM)
Hangzhou Tue 28-Jan-2020 00:00 (12:00 AM)
Tokyo Tue 28-Jan-2020 01:00 (01:00 AM)
Sydney Tue 28-Jan-2020 03:00 (03:00 AM)

Or in your local time:

Links

Agenda

Extracted from security-wg-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/security-wg

  • Nominating Daniel Ruf to the Ecosystem Triage team #614
  • Triage Buckets and Prioritization #604
  • Nominate Thomas Watson as WG member #581
  • Reaching out to other projects of the OpenJS Foundation #511
  • Introducing Audit Hooks to Node.js #626

Invited

  • Security wg team: @nodejs/security-wg

Observers/Guests

Notes

The agenda comes from issues labelled with security-wg-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

@mhdawson mhdawson self-assigned this Jan 22, 2020
@vdeturckheim
Copy link
Member

It seems that this meeting conflicts with the N-API right?

@sam-github
Copy link
Contributor

Yes, I'd never noticed that, did one move? I propose we move this one an hour later.

@vdeturckheim
Copy link
Member

@sam-github LGTM

@mhdawson
Copy link
Member Author

mhdawson commented Jan 28, 2020

@sam-github +1 from me as well (although I mostly have conflicts, Sam can keep me up to date)

@lirantal
Copy link
Member

lirantal commented Feb 9, 2020

@mhdawson can we make sure the next meeting doesn't conflict? :-)

@lirantal lirantal closed this as completed Feb 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants