Open RFC Meeting - Wednesday, April 29, 2020, 2:00 PM EST

[darcyclarke]

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, April 29, 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

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

1. Housekeeping
   1. Introduction(s)
   2. Code of Conduct Acknowledgement
   3. Outline Intentions & Desired Outcomes
   4. Announcements
2. PR: #117 RFC: npm workspaces - Running Commands
3. PR: #129 RFC: overrides
4. Issue: [RRFC] opt out of optional meta-dependency
5. PR: #133 RFC: Remove --depth from npm outdated
6. PR: #121 Added proposal for package version syntax

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

[ruyadorno]

hi @kael-shipman, we're going to be talking about #121 today and it would be awesome if you could join the meeting 😊

[kael-shipman]

Oh no! I'm very interested, but I've already got a meeting at that time that I can't miss :(. There's a chance that I could join a half hour or 45 minutes in if you'd be willing to save mine for last, but unfortunately there are no guarantees, since my meeting is booked for the whole hour. Thank you for doing this, though, and thanks for letting me know!

[ruyadorno]

no worries 👍 but yeah, def try to join later if you can 😄 we'll make sure it's the last item on the list!

[darcyclarke]

Notes: https://hackmd.io/urLMaymHRQ2Z94oEYTmBbg?both
Recording: https://www.youtube.com/watch?v=GUhY5oJxWrQ&feature=youtu.be

[kael-shipman]

Sorry all, my meeting ran long, not short, so couldn't make it :(. I've got the May 13th one in my calendar, though, so hopefully I'll be able to contribute then. Thanks again for conducting these input sessions.

[kael-shipman]

Another quick note (cc @darcyclarke , whom it appears is one of the main coordinators of this forum):

It seems like an overwhelming majority of the discussion around these RFCs falls into the "developer experience" category. I just watched a little bit of the recording of today's meeting and there was a lot to say about the addition of an --all parameter and some possible alternatives, for example.

If we take a cue from industry, where there is now full adoption of the concept of user experience professionals whose primary tools are user interviews and surveys, it would make a ton of sense to me to use a platform like Tricider in conjunction with a mailing list to gather feedback from the millions of devs around the world who use npm every day. The vote of the developer community would be by no means binding, but it would certainly inform the discussions in these meetings in a very considerable way.

Plenty more thoughts to roll around if anyone's interested.