WIP - doc: allow multiple orgs and add pkgjs org

[mhdawson]

Refs: https://github.com/nodejs/admin/issues/470

Signed-off-by: Michael Dawson [email protected]

[mhdawson]

This is first part of several that are needed for https://github.com/nodejs/admin/issues/470. Should not land until those have been covered off:

• [ ] changes to the org management policy (this PR)
• [x] 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.
• [X] check if any docs in the moderation repo need to be updated. - PR for updates - https://github.com/nodejs/moderation/pull/531
• [x] check that existing repos in pkgjs org have required licences, governance etc.
• [x] 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.
• [x] update onboarding docs for TSC (possibly CommComm as well) to add them as owners where appropriate.

[mcollina]

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

[mhdawson]

@mcollina thanks, will add that to the list.

[mmarchini]

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.

[dominykas]

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.

[mmarchini]

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.

[bnb]

@mhdawson do we want to continue with this?

[mhdawson]

@bnb yes, since we already have the second org :)

[mhdawson]

@nodejs/tsc any objections to this. If not I'll rebase and submit another PR to update the on/offboarding docs

@bnb would you be able to check over the moderation docs to see if they need any changes?

[mmarchini]

should we move the checklist from https://github.com/nodejs/admin/pull/484#issuecomment-604486043 to a new issue to make sure it doesn't get lost?

[bnb]

@mhdawson making "Node.js GitHub Organization" be "Node.js GitHub Organizations" in every instance should cover it.

[mhdawson]

@bnb

making "Node.js GitHub Organization" be "Node.js GitHub Organizations" in every instance should cover it.

Is that something you'd like to do or should I submit a PR to do that?

[bnb]

@mhdawson i'm happy to do it in a separate PR, just wasn't sure if you wanted to do it in this one.

[mhdawson]

@bnb I was thinking the docs might be in the moderation repo, if its in this repo then probably makes sense to add to this PR. Since you just looked was it just this doc ? - https://github.com/nodejs/admin/blob/main/Moderation-Policy.md

[mhdawson]

@bnb added the updates to the Moderation-Policy.md and one small PR to the docs in the moderation repo - https://github.com/nodejs/moderation/pull/531 once that lands I think this PR can land.

[Trott]

@mhdawson If this is still needed, can you resolve the conflict?

[bnb]

IMO it is still needed. https://github.com/nodejs/moderation/pull/531 has also landed, which should theoretically unblock :)

[mhdawson]

@Trott, I rebased and will now land.