Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

remove [email protected] alias #238

Merged
merged 1 commit into from
Feb 2, 2024
Merged

remove [email protected] alias #238

merged 1 commit into from
Feb 2, 2024

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Jan 31, 2024

@richardlau
Copy link
Member

I don't remember ever receiving anything on this alias, so +1 if it's redundant. Am also open to redirecting to a foundation owned alias, if one exists.

There are references to this alias in the TSC onboarding/offboarding docs.

@richardlau
Copy link
Member

One other thing, when this was set up there was also a corresponding alias [email protected] which forwarded to this one ([email protected]) #104 (comment). I'm not sure if that alias still exists (it's managed by the Linux Foundation and not the Build WG) but if it does this PR will affect it (as it would be forwarding to a non-existent alias).

According to the (now deleted by nodejs/admin#617) us-export-control.md document, it was the [email protected] address which was used.

@mhdawson
Copy link
Member

Lets remove this and ask @bensternthal to make sure that [email protected] no longer exists or if needed forwards to somebody at the Foundation.

mhdawson
mhdawson approved these changes Jan 31, 2024
View reviewed changes
Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bensternthal
Copy link

[email protected] bounces, so I can confirm this is not an active email address.

richardlau added a commit to nodejs/TSC that referenced this pull request Feb 1, 2024
@richardlau
doc: remove references to crypto-exports list
89fa3d8 
The `crypto-exports` mailing list is no longer used and is being removed.

Refs: nodejs/email#238
Refs: nodejs/admin#617
@richardlau richardlau mentioned this pull request Feb 1, 2024
Merged
@richardlau
Copy link
Member

There are references to this alias in the TSC onboarding/offboarding docs.

PR to remove these references: nodejs/TSC#1499

richardlau added a commit to nodejs/TSC that referenced this pull request Feb 1, 2024
@richardlau
doc: remove references to crypto-export list
49d28e3 
The `crypto-export` mailing list is no longer used and is being removed.

Refs: nodejs/email#238
Refs: nodejs/admin#617
@richardlau richardlau merged commit 4e1dfc3 into main Feb 2, 2024
@richardlau richardlau deleted the rm-crypto-export branch February 2, 2024 13:24
@richardlau
Copy link
Member

Deployed.

aduh95 pushed a commit to nodejs/TSC that referenced this pull request Feb 2, 2024
@richardlau
doc: remove references to crypto-export list (#1499)
52fffee 
The `crypto-export` mailing list is no longer used and is being removed.

Refs: nodejs/email#238
Refs: nodejs/admin#617
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mhdawson mhdawson mhdawson approved these changes

@richardlau richardlau richardlau approved these changes

@UlisesGascon UlisesGascon UlisesGascon approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@aduh95 @richardlau @mhdawson @bensternthal @UlisesGascon