-
Notifications
You must be signed in to change notification settings - Fork 137
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
doc: remove section on export control #617
Conversation
Signed-off-by: Michael Dawson <[email protected]>
@jorydotcom, @brianwarner FYI. |
@nodejs/tsc, @nodejs/community-committee would be good to get some reviews so that this can land. |
Care to elaborate? It might help folks get peace of mind to approve the PR. |
@mmarchini I don't have the details @brianwarner might, but at this point the doc we have is long out of date so wanted to remove it. |
Happy to review pending @mmarchini's request for context |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@brianwarner, @jorydotcom people have asked that at least one of you sign off on this before they are comfortable that we remove it. |
Yep, looks fine, this is replaced by https://openjsf.org/export. |
k, we have 2 TSC and 2 CommComm approvals now so I'm going to land. |
The `crypto-exports` mailing list is no longer used and is being removed. Refs: nodejs/email#238 Refs: nodejs/admin#617
The `crypto-export` mailing list is no longer used and is being removed. Refs: nodejs/email#238 Refs: nodejs/admin#617
The `crypto-export` mailing list is no longer used and is being removed. Refs: nodejs/email#238 Refs: nodejs/admin#617
Signed-off-by: Michael Dawson [email protected]
This is long out of date and I've been told that the OpenJS foundation has new/different processes for handling this through the Linux Foundation.