-
Notifications
You must be signed in to change notification settings - Fork 78
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.
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
email: add alias for crypto reporting #104
Conversation
Myles appears in the list twice. Would it be more maintainable if we replaced the listed-out TSC folks with What is the purpose of this email alias? Is it mentioned in the recent export doc or something? I thought we determined that all that stuff was not much of a TSC concern as much as a Foundation/Board concern. |
It is mentioned in the doc: https://github.com/nodejs/admin/blob/master/us-export-control.md which defines who will get emails. Myles is there because I copied the TSC list and then added the 2 other positions that should be copied. It might be easier to keep it that way than having to update when the TSC list updates (ie remember to remove him each time). I would have used [email protected] but I believe we figured out that recursion does not work in the lists and that for now we had to leave them expanded. |
[email protected] now forwards to [email protected] as well. |
@Trott can you take another look, would like to get alias in place since node.js version is already forwarding to it. |
PR-URL: #104 Reviewed-By: Rich Trott <[email protected]>
Landed as 7ea0495 |
PR-URL: nodejs/email#104 Reviewed-By: Rich Trott <[email protected]>
No description provided.