Add Charter

[aduh95]

Not sure if we actually need that, or if this is the right approach. The idea would be to delegate the discussions from TSC meetings to a different group.

[wesleytodd]

For folks seeing such a large diff and wondering what changed, this is the section to focus on. The rest is marked as changed but really isnt. Additionally, the parts above about the repo's is because the goal here is to subsume the corepack team into the PMWG.

[wesleytodd]

Goals of this change:

1. Give discussions around package managers of all varieties a place to have dedicated discussions around how they interop with Node.js (both the technical and the non-technical)
2. Avoid Node.js Core PRs being the only avenue for having active discussion on these topics (avoid battle pr's deps: remove corepack node#51981 and build: enable yarn and pnpm Corepack binaries by default node#51886 for example)
3. Help give more resources to @GeoffreyBooth's work to help define Node.js policy around this stuff
4. Make it unambiguous where to seek consensus for future discussions before raising related topics to Node.js core or TSC

[GeoffreyBooth]

I’m not sure whether whatever potential new tool we make would necessarily ship bundled in the distribution; and of course we might unbundle Corepack. We should still be responsible for these things regardless, though, so I think a better way to put it is that we’re responsible for anything under https://github.com/nodejs.

Suggested change

	* Management of the "version management tools" shipped with the Node.js distribution (see below).
	* Management of the “version management tools” maintained within the Node.js GitHub org.

[wesleytodd]

Ah interesting point. Hm, yeah I think this is a good goal of this change but npm is not maintained within this org, so that feels at odds right?

[GeoffreyBooth]

Suggested change

	* Maintaining the relationship[^note] with any tools included in the Node.js default distribution with the express purpose of the following:
	* Maintaining the relationship[^note] with any tools included or referenced by Node.js-managed software with the express purpose of the following:

[GeoffreyBooth]

Suggested change

	* Contribution policy for all of the additional software included in the Node.js distribution as qualified above.
	* Contribution policy for all of the additional software within the Node.js GitHub organization as qualified above.

[wesleytodd]

Hm interesting change. I think I understand why but would you mind explaining the goal of this wording over the other?

[GeoffreyBooth]

In the collab summit meeting meeting on 2024-04-03 we discussed trying to agree on goals first, and getting those approved by both this team and then the TSC, and then chartering this team to work out the implementation details to achieve those goals.