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

Open RFC Meeting - Wednesday, January 27, 2021, 2:00 PM EST #311

Closed
darcyclarke opened this issue Jan 27, 2021 · 3 comments
Closed

Open RFC Meeting - Wednesday, January 27, 2021, 2:00 PM EST #311

darcyclarke opened this issue Jan 27, 2021 · 3 comments

Comments

@darcyclarke
Copy link
Contributor

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, January 27, 2021, 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. File Path Resolution Review:
    1. Summary:
      • file: behaivour changed in v7 - no longer support installing depencies of packages that are not nested
    2. Questions:
      • Do we agree with how it's working today?
      • How would we change it?
    3. Related Items:
  3. Workspaces Review:
    1. Summary:
      • It's been brought up several times that the mental model we have today of "hoisting" dependencies should be re-examined as "sharing"; This aligns with some feedback/feature request we've already recieved to add no-hoist as a config to Workspaces. Reviewing & thinking critically about the behaivour of our existing strategy will help us lay a solid foundation/understanding before we start the next phase of work in this space.
    2. Questions:
      • Do we agree with how it's working today?
      • How would we change it?
    3. Related Items:

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
@darcyclarke darcyclarke pinned this issue Jan 27, 2021
@ljharb
Copy link
Contributor

ljharb commented Jan 27, 2021

TC39 is today, so I’ll be unable to attend. I’m very interested in the workspaces review, though.

@darcyclarke
Copy link
Contributor Author

@ljharb ya, we can definitely circle back on this (it's not going anywhere immediately) & we'll try to take great notes.

@darcyclarke darcyclarke unpinned this issue Jan 27, 2021
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

No branches or pull requests

2 participants