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 protected] forwards to [email protected])
Each alias falls into one of four categories:
- Converted to a Working Group: These will be upgraded to LFX and are fine to continue using. They will1 be automatically updated as our GitHub Teams evolve
- 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.
- 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).
- 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.
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.
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.
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.
This proposal moves our
@iojs.orgmailing aliases into the Linux Foundation's LFX Project Control Center under the@nodejs.orgalias, which gives us managed committees and mailing lists with support for surveys and voting.(For purposes of this document,
→should be interpreted as[email protected]forwards to[email protected])Each alias falls into one of four categories:
@iojs.orgcounterpart, which will eventually stop working.Two general principles apply throughout:
*@iojs.orgaliases will not be touched for now, but should be gradually phased out after the migration to@nodejs.orgon LFX is complete.*@iojs.orgaliases will redirect to*@nodejs.orgonce 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.
[email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected][email protected]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 tocontinue using.
[email protected]forwards to[email protected][email protected]→[email protected][email protected]→[email protected]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.
[email protected]forwards to[email protected][email protected]→[email protected][email protected]→[email protected][email protected]→[email protected][email protected]→[email protected][email protected]→[email protected][email protected]→[email protected][email protected]→[email protected][email protected]→[email protected][email protected]→[email protected].[email protected]→[email protected]2[email protected]→[email protected]+[email protected][email protected]→[email protected]4. Deprecated
These aliases will not be upgraded to LFX. They remain reachable only via
their
@iojs.orgcounterpart, which will eventually stop working. If any arestill in use, please let me know.
[email protected]Personal account; no longer needed as a project alias.
[email protected]No longer needed.
[email protected]The associated HackerOne account has been closed, as far as I'm aware.
Footnotes
In the future ↩
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. ↩