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 Security WorkGroup Meeting 2023-04-27 #961

Closed
mhdawson opened this issue Apr 24, 2023 · 4 comments · Fixed by #969
Closed

Node.js Security WorkGroup Meeting 2023-04-27 #961

mhdawson opened this issue Apr 24, 2023 · 4 comments · Fixed by #969
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Thu 27-Apr-2023 14:00 (02:00 PM):

Timezone Date/Time
US / Pacific Thu 27-Apr-2023 07:00 (07:00 AM)
US / Mountain Thu 27-Apr-2023 08:00 (08:00 AM)
US / Central Thu 27-Apr-2023 09:00 (09:00 AM)
US / Eastern Thu 27-Apr-2023 10:00 (10:00 AM)
EU / Western Thu 27-Apr-2023 15:00 (03:00 PM)
EU / Central Thu 27-Apr-2023 16:00 (04:00 PM)
EU / Eastern Thu 27-Apr-2023 17:00 (05:00 PM)
Moscow Thu 27-Apr-2023 17:00 (05:00 PM)
Chennai Thu 27-Apr-2023 19:30 (07:30 PM)
Hangzhou Thu 27-Apr-2023 22:00 (10:00 PM)
Tokyo Thu 27-Apr-2023 23:00 (11:00 PM)
Sydney Fri 28-Apr-2023 00:00 (12: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

  • Initiative for CII-Best-Practices for Nodejs Projects #953
  • Scorecard Review #937
  • Improve Node.js Scorecard #929
  • Permission Model - Roadmap #898
  • Improve SecurityWG Scorecard #884
  • Automate security release process #860
  • Assessment against best practices (OpenSSF Scorecards ...) #859
  • Discussion about policy-integrity integration on Windows #856
  • Automate updates of all dependencies #828

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

https://zoom.us/j/92309450775

  • link for participants: <>
  • For those who just want to watch We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
  • youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled
@mhdawson mhdawson self-assigned this Apr 24, 2023
@RafaelGSS
Copy link
Member

I will join, but I'm not sure I can chair this one (hotel wifi). @mhdawson or @UlisesGascon can chair this one?

@mhdawson
Copy link
Member Author

I plan to be there, but if @UlisesGascon can chair that would be my first choice.

@UlisesGascon
Copy link
Member

I am able to chair, no problem at all 🙂

@fraxken
Copy link
Member

fraxken commented Apr 26, 2023

I have an important meeting at the same time, I will try to join if I finish early :)

This was referenced Apr 27, 2023
UlisesGascon added a commit that referenced this issue Apr 30, 2023
Related: #961
-----------
Co-authored-by: RafaelGSS <rafael.nunu@hotmail.com>
RafaelGSS added a commit that referenced this issue Apr 30, 2023
Related: #961
-----------

Co-authored-by: RafaelGSS <rafael.nunu@hotmail.com>
patrickm68 added a commit to patrickm68/security-wg-process that referenced this issue Sep 14, 2023
Related: nodejs/security-wg#961
-----------

Co-authored-by: RafaelGSS <rafael.nunu@hotmail.com>
mattstern31 added a commit to mattstern31/security-wg-process that referenced this issue Nov 11, 2023
Related: nodejs/security-wg#961
-----------

Co-authored-by: RafaelGSS <rafael.nunu@hotmail.com>
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

Successfully merging a pull request may close this issue.

4 participants