Move to LFX

This proposal moves our @iojs.org mailing aliases into the Linux Foundation's LFX Project Control Center under the @nodejs.org alias, which gives us managed committees and mailing lists with support for surveys and voting.

(For purposes of this document, → should be interpreted as email@domain.tld forwards to email@domain.tld)

Each alias falls into one of four categories:

1. Converted to a Working Group: These will be upgraded to LFX and are fine to continue using. They will[^1] be automatically updated as our GitHub Teams evolve
2. Supported: These aliases that remain in active use, and for the most part redirect to an alias defined in (1). These will be upgraded to LFX and are fine to continue using.
3. Maintenance: These aliases are kept only for legacy or operational reasons. These will be upgraded to LFX, but only so existing integrations keep working; new usage is discouraged, and users should move to an alias defined in (1).
4. Deprecated: aliases that will not be upgraded to LFX. They remain reachable only through their @iojs.org counterpart, which will eventually stop working.

Two general principles apply throughout:

• LF-controlled aliases will be replaced by this proposal.
• *@iojs.org aliases will not be touched for now, but should be gradually phased out after the migration to @nodejs.org on LFX is complete.
• *@iojs.org aliases will redirect to *@nodejs.org once this migration is complete.

---

1. Converted to a Working Group

I've created the following committees in LFX, with this proposed mapping.
These will be upgraded to LFX and are fine to continue using.

• Technical Steering Committee: tsc@nodejs.org
• Moderation Team: moderation@nodejs.org
• Discord Moderation Team: moderation-discord@nodejs.org
• Build Working Group: build@nodejs.org
• Website & Infrastructure Working Group: web@nodejs.org
• Jenkins Administrators: ci@nodejs.org
• Security Triage Team: security-triage@nodejs.org
• Release Working Group: release@nodejs.org
• Undici Maintainers: undici@nodejs.org

---

2. Supported

These externally-facing aliases remain in active use. They will be upgraded
to LFX and forward to the relevant working-group alias (with an exception of security@); they are fine to
continue using.

• report@nodejs.org forwards to moderation@nodejs.org
• report-discord@nodejs.org → moderation-discord@nodejs.org
• security@nodejs.org → nodejs-79566c66a30b0312@forwarding.hackerone.com

---

3. Maintenance

These aliases will be upgraded to LFX, but only for legacy reasons. They will keep working for the time being so existing integrations don't break, but new usage is discouraged.

Note: They are not mapped 1:1 with their previous mappings.

• admin@nodejs.org forwards to build-infra@nodejs.org
• accounts@nodejs.org → build-infra@nodejs.org
• nodejs-pypi@nodejs.org → build-infra@nodejs.org
• nodejs-vercel@nodejs.org → web@nodejs.org
• nodejs-crowdin@nodejs.org → web@nodejs.org
• cve-request@nodejs.org → security-triage@nodejs.org
• cve-mitre-contact@nodejs.org → security-triage@nodejs.org
• cna-discussion-list@nodejs.org → security-triage@nodejs.org
• ci-alert@nodejs.org → ci@nodejs.org
• release-validation-alert@nodejs.org → build-infra@nodejs.org.
• zoom-nodejs@nodejs.org → tsc@nodejs.org[^2]
• wiby-bot@nodejs.org → bjohansebas@gmail.com + hello+wibybot@dominykas.com
• github-bot@nodejs.org → tsc@nodejs.org

---

4. Deprecated

These aliases will not be upgraded to LFX. They remain reachable only via
their @iojs.org counterpart, which will eventually stop working. If any are
still in use, please let me know.

• rvagg@iojs.org
  Personal account; no longer needed as a project alias.
• nodejs-lfx-bounty@iojs.org
  No longer needed.
• security-ecosystem@iojs.org
  The associated HackerOne account has been closed, as far as I'm aware.

[^1]: In the future
[^2]: We are in the process of moving away from Zoom meetings created using this email, and as such, this email will forward to TSC for legacy reasons, but will be deprecated in the near future.

Start by locating the repository's email alias configuration and compare it with the proposed LFX mappings in this issue. Confirm each working-group, supported, maintenance, and deprecated alias has the intended destination or status; done means the migration is represented accurately and existing integrations remain covered.