Deep Dive Meeting - Wednesday, April 22, 2020, 2:00 PM EST Meeting

[darcyclarke]

Why?

In our ongoing efforts to better listen to & collaborate with the community, we've started an Open RFC deep dive call that helps to move a specific conversation and/or initiative forward.

When?

Wednesday, April 22, 2020, 2:00 PM EST

Cadence:
This meeting is scheduled to take place bi-weekly alternating with our regular Open RFC calls. 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

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.

Invited Attendees

• Anyone interested in the idea of staging/stage publishes (please review the PRs beforehand)

Agenda

1. Housekeeping
   1. Introduction(s)
   2. Code of Conduct Acknowledgement
   3. Outline Intentions & Desired Outcomes
   4. Announcements
2. Topic:
   • Resolutions/Overrides
3. References:
   • Legacy Overrides RFC
   • New Overrides RFC
   • Previous: Overrides Deep Dive - Agenda
   • Previous: Overrides Deep Dive - Video Recording
   • Previous: Overrides Deep Dive - Notes

How?

Join Zoom Meeting
https://npm.zoom.us/j/914742332

Meeting ID: 914 742 332

One tap mobile
+16465588656,,914742332# US (New York)
+16699006833,,914742332# US (San Jose)

Dial by your location
+1 646 558 8656 US (New York)
+1 669 900 6833 US (San Jose)
Meeting ID: 914 742 332
Find your local number: https://npm.zoom.us/u/abR8OFljr8

[wesleytodd]

One thing I would like to add to the agenda if we have time:

How could we enable centrally managed overrides? The use case here is for organizations which have products or libraries which want to widely distribute a set of overrides. Imagine you are at Netflix (conveniently I don't have to imagine this), and you are on a central team (also, I am not having to work hard to imagine this) and you see that a very popular library has a breaking change in a patch. To prevent every single project from having to simultaneously add the override, you would like to have it centrally managed so you can update in one place and have it apply throughout the whole org.

I have some ideas on how we could solve this, but I would like to hear others thoughts on if this feature is valuable to them or if maybe other approaches than centrally managed overrides could help solve this use case.

[darcyclarke]

@wesleytodd very interesting. Maybe this can be solved via config in .npmrc files which is often a shared resource among teams 🤔. Let's try to bring this up and hear your thoughts on the call for sure.

[darcyclarke]

Meeting Notes: https://hackmd.io/STxYjUHyQQ-VHSnCzmU0ww
Video Stream: https://youtu.be/QSPfjVjXqgY