Rich Trott

Hi, @Fishrock123! The procedure is detailed in https://github.com/nodejs/admin/blob/master/transfer-repo-into-the-org.md. Only thing I'm seeing missing in the repo is a code of conduct (which, if you wish, can just be a single...

The repo should get a code of conduct added before being transferred. Other than that, it seems ready.

Accounts that would be affected (unless we add them to another team or decide that we're not doing this): @ahmadnassri @allevo @amandeepmittal @aoberoi @aruneshchandra @AustinWinstanley @AyushG3112 @bcmarinacci @bdharrington7 @bentinata @bf4...

I'm going to add @WaleedAshraf back to `@nodejs/website` and remove them from the list. They've been active in reviewing a handful of PRs in the nodejs.org this year, and that's...

Affected people list part 2 (broken up into two lists because apparently there is a limit to how many names you can @-mention in a GitHub comment): @naskapal @Neil188 @nickmccurdy...

> being in the org allows me to stay informed. Can you explain that a bit more? What do you do to stay informed that you wouldn't be able to...

@nodejs/tsc (for awareness)

> I am +1 to removing anyone who isn't explicitly a member of a WG. I agree with @bnb and want to clarify that this applies not just to WGs...

I've added the `tsc-agenda` label in the hopes that we can arrive at a decision at or before the next meeting (in one week) to either do this or close...

@nodejs/tsc Can you give a 👍 reaction to this if you'd like us to move forward with this, and a 👎 if you have concerns/doubts and would want this to...