-
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, August 19, 2020, 2:00 PM EST #207
Comments
👍
…On Tue, 18 Aug 2020 at 15:46, Darcy Clarke ***@***.***> wrote:
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, August 19, 2020, 2:00 PM EST
*Cadence:*
This meeting is scheduled to take place *bi-weekly*. Previous meeting
agendas and notes can be found here
<https://github.com/npm/rfcs/issues?q=is%3Aissue+sort%3Aupdated-desc+is%3Aclosed+label%3Ameeting>
*Add to your Calendar:*
You follow this & find other *npm* events by using our *public events
calendar*
- gCal:
https://calendar.google.com/calendar/embed?src=npmjs.com_oonluqt8oftrt0vmgrfbg6q6go%40group.calendar.google.com
- iCal:
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
<https://www.npmjs.com/policies/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
1. *Housekeeping*
1. Introduction(s)
2. Code of Conduct Acknowledgement
3. Outline Intentions & Desired Outcomes
4. Announcements
2. *PR*: #1674 Rfc 0027 npm audit app id
<npm/cli#1674> - @doddi
<https://github.com/doddi>
3. *PR*: #1586 [Feature] Security Pipeline
<npm/cli#1586> - @jskoll
<https://github.com/jskoll>
4. *Issue*: #190 [RRFC] npm run-series && npm run-parallel
<#190> - @MylesBorins
<https://github.com/MylesBorins>
5. *PR*: #185 RFC: Add ability to skip script hooks
<#185> - @lumaxis
<https://github.com/lumaxis>
6. *PR*: #183 RFC21: bring back subset of npm_package_* environs
<#183> - @isaacs
<https://github.com/isaacs>
7. *PR*: #182 RFC: npm audit licenses
<#182> - @bnb <https://github.com/bnb>
8. *PR*: #165 RFC for parent package.json
<#165> - @Christian24
<https://github.com/Christian24>
9. *PR*: #129 RFC: overrides <#129> -
@isaacs <https://github.com/isaacs>
10. *PR*: #126 RFC: Adding types information to the Package JSON in
the registry <#126> - @orta
<https://github.com/orta>
11. *PR*: #18 npm audit and audit-resolve.json
<#18> - @naugtur
<https://github.com/naugtur>
How?
*Join Zoom Meeting*
https://npm.zoom.us/j/584504445
*Dial by your location*
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
*Meeting ID:* 584 504 445
Find your local number: https://zoom.us/u/abR8OFljr8
*Watch the livestream*
https://www.youtube.com/channel/UCK71Wk0I45SLTSXQA23GdIw/videos
Invitees
Please use the following emoji reactions to indicate your availability.
- 👍 - Attending
- 👎 - Not attending
- 😕 - Not sure
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#207>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB7VH5XBWL5RYFIZJDPGN3SBKH5HANCNFSM4QDS2MSA>
.
|
Sorry, zoom really needs a low data mode where I can just do audio only. Good conversations, my only addition to the "is platform support needed" on the parent Anyway, hope you all have a good week, see you next call. |
Updated RFC 0027 (npm audit metadata) to reflect meeting discussion
#138
…On Wed, 19 Aug 2020 at 21:21, Wes Todd ***@***.***> wrote:
Sorry, zoom really needs a low data mode where I can just do audio only.
Good conversations, my only addition to the "is platform support needed" on
the parent package.json RFC is that I think the scope of tooling like
Mikeal (and I think Snowpack is similar) is different. I think those
experiments are great, but they require some larger buy in. The hope for
this RCF in my opinion is that it helps enable what folks are doing today
to be done more easily.
Anyway, hope you all have a good week, see you next call.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#207 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB7VH5D2FOL2RRLBLPPVEDSBQX37ANCNFSM4QDS2MSA>
.
|
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, August 19, 2020, 2:00 PM EST
Cadence:
This meeting is scheduled to take place bi-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://npm.zoom.us/j/584504445
Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
Meeting ID: 584 504 445
Find your local number: https://zoom.us/u/abR8OFljr8
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: