-
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 cleanup tracking #182
Comments
It's linked to https://github.com/nodejs-ci and is used by our Jenkins CI to authenticate to GitHub, including accessing the private repos. It got one mail when I invited it to the private libuv org/repo in May last year (Joao followed up with me). For completeness, the build email is linked to https://github.com/node-forward-build. I don't have the history as to why we have two GitHub accounts associated with the build WG. Details for both of the accounts are in the build secrets repo under |
I believe we can also remove crypto-report |
Audit zoom-nodejs. (Seems like a somewhat weird mix of people. Who is on there and why? What is the purpose of the email address?) Anybody who hosts zoom calls using the Node.js account should be on this list. Needed to get authentication tokens that are sometimes needed. |
Are we clear on this, @RafaelGSS ? Should we include it to the next meeting? |
Yes, we should probably remove that email address. |
No idea what that was for, didn't know it existed. Also seems like it was removed so you can check that as done: e8e43b2 |
Originally posted by @Trott in #181 (comment)
The text was updated successfully, but these errors were encountered: