-
Notifications
You must be signed in to change notification settings - Fork 239
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
Open RFC Meeting - Wednesday, September 22, 2021, 2:00 PM EST #461
Labels
Comments
|
Doh, I missed it. I'm considering switching from calling npm to using arborist under the hood. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why?
In our ongoing efforts to better listen to & collaborate with the community, we've started an Open RFC call that helps to move conversations & initiatives forward.
When?
Wednesday, September 22, 2021, 2:00 PM EST
Cadence:
This meeting is scheduled to take place weekly. Previous meeting agendas and notes can be found here
Add to your Calendar:
You follow this & find other npm events by using our public events calendar
https://calendar.google.com/calendar/embed?src=npmjs.com_oonluqt8oftrt0vmgrfbg6q6go%40group.calendar.google.com
https://calendar.google.com/calendar/ical/npmjs.com_oonluqt8oftrt0vmgrfbg6q6go%40group.calendar.google.com/public/basic.ics
What?
All discussions surrounding RFCs are covered by the npm Code of Conduct. Please keep conversations constructive, civil & be mindful of when others are speaking. As is tradition, "raise your hand" when requesting to comment on a topic or request to comment asynchronously within the chat. The npm team may, at its own discretion, moderate, mute &/or remove a person from an Open RFC call for any reason.
Agenda
How?
Join Zoom Meeting
https://github.zoom.us/j/94543839461?pwd=S0lwYytLd2tlMVBxTlJGbE5QQlhGUT09
Watch the livestream
https://www.youtube.com/channel/UCK71Wk0I45SLTSXQA23GdIw/videos
Invitees
Please use the following emoji reactions to indicate your availability.
The text was updated successfully, but these errors were encountered: