Closed GeoffreyBooth closed 2 months ago
I am not sure if this is the right place to ask, but I was struggling to find the right repo for this by googling and then I realized it is in the package maintenance working group and the README of this repo seems to have nothing to do with corepack or version management....or at least, we are talking about developing new features or new tools here, not talking about how to keep dead/old packages alive?
we are talking about developing new features or new tools here, not talking about how to keep dead/old packages alive?
Yeah, in the chartering discussion we wondered if perhaps it would be good to rename this team or start a new one. There’s a defunct @nodejs/version-management team too. I think for now the consensus was to deal with the goals first and then possibly rename/redefine the team based on what goals end up getting approved.
Looks good from my perspective.
Should I link to this PR in the trip report of the summit, or this repo? (somewhat weird to link to the repo while the REAMD still talks about package maintenance, but I guess we can also update the blog post)
Or I can link to https://github.com/nodejs/package-maintenance/issues/591 which should provide sufficient background
I wouldn't worry too much about the name. This group has always been a place to discuss ancillary tooling including package manager related topics. With this pivot we do need updates to the README, but as @GeoffreyBooth said we discussed chartering first and decided to establish the goals before chartering and changing the makeup of this group.
:popcorn:
A draft of the goals discussed in https://github.com/nodejs/package-maintenance/issues/595.
cc @nodejs/package-maintenance @nodejs/tsc