Darcy Clarke

I'll throw it over the coals when I get a second tonight @pamelafox-coursera. Thanks though!

@dominykas yes, your example is correct. > How would that interact with other related commands, e.g. npm ci? This is a good question. IMO, your example shouldn't effect `ci`'s behavior...

### Actions - [ ] needs command & config audit (ie. documenting which commands call other commands & what config should or shouldn't be shared with them: ex. `npm install`...

👍🏻 removing Agenda flag as we're all in favor of this & have queued this up for `v9` (we'll land this as accepted) - https://github.com/npm/statusboard/issues/443

Leaving this on the agenda for today, @nlf would be great if you could speak bit to your diagram/approach discussed here in the call but understand if you can't make...

### Actions - [ ] @nlf / @ruyadorno to make an RFC for these changes

I'm in favor of _fixing_ `overrides` (that's right, I think it's a bug this isn't already supported). Supporting direct dependency `overrides` + references gives you what you want ([ref](https://github.com/npm/rfcs/blob/55ee796c1d4f0fbfc97b8d83b7496cdf5b39033b/accepted/0000-shared-version-specs.md#overrides)). We...

Removing `Agenda` label as we've discussed this & will fix the current `overrides` implementation to help support this usecase as described in earlier comments.

It sounds like you might be trying to reference multiple packages of the same name across different registries(?) If that is indeed the case, you should likely be defining the...

@bnb added the `"Agenda"` label to the RFC. We'll ensure there's some dedicated time to discuss this in the Open RFC call Wednesday (will likely stay on the Agenda for...