This is first part of several that are needed for #470. Should not land until those have been covered off:

• changes to the org management policy (this PR)
• Proposed charter for Package Maintenance team which delegates approval of the creation of
  new repos to that team, addition of members, along with some org owner capability. I believe this
  is what the package maintenance team wants, but need to work through the details.
• check if any docs in the moderation repo need to be updated.
• check that existing repos in pkgjs org have required licences, governance etc.
• Add current org owners as owners to the pkgjs org, adjust existing owners to reflect that is
  outlined in the charter for the Package Maintenance team.
• update onboarding docs for TSC (possibly CommComm as well) to add them as owners where
  appropriate.

I think you need to update the onboarding docs for TSC and CommComm members as they will become org owners.

@mcollina thanks, will add that to the list.

One thing I noticed (and don't have a good fix for) is that Node.js members won't be able to ping teams on the pkgjs org. Not sure if that's something we didn't consider or if it was intentional, and unfortunately I don't think there are any workarounds for it, but might be a good thing to add to a "considerations list" or something for folks thinking about spinning up the next separate org.

This is a good point. Does github have an issue tracker for things like this? Node/pkgjs is not the only place where I'm missing a sort of "umbrella org" / cross-org teams feature. At a certain point, esp. in the ecosystem of loooooots of small modules, a single org becomes too large to administer. I sure we're not the only ones experiencing this.

There's a private repo, but it's more for feedback on beta features instead of new features. Sending the suggestion via support might be a good idea.