-
Notifications
You must be signed in to change notification settings - Fork 167
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
Access for @miladfarca to IBM machines #1706
Comments
👍 |
@nodejs/build would be good if a few more build wg members chimed in on @refack's suggestion. |
+1 |
1 similar comment
+1 |
Going to move forward with adding Milad's keys |
@mhdawson Since this is a permanent access grant, this can be closed, no? |
I'm ok with closing it if that is what people think is best. Even closed it is a record of the ok to give him access, maybe just a bit harder to find since you need to look for closed issues. Normally I'd expect people look at the open issues since that is what we use for temporary access. |
I like to keep these open as a reminder to clean up the keys eventually. |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
@nodejs/build Since it is permanent access any objections to closing this issue? |
@miladfarca is going to be helping more with the IBM platforms and we've asked a few times for access already and gotten approval. See: #1702 and #1686.
I'd like him to help setup the new machines outlined in: #1705 so I'd like the ok to give him access to those machines as well. We are also working to get an additional set of s390 machines with a newer os as well so I'll ask in advance if we can get the ok to give him access to those as well.
Of note, @gdams has left IBM so getting @miladfarca access will help me move these efforts along.
The text was updated successfully, but these errors were encountered: