-
Notifications
You must be signed in to change notification settings - Fork 166
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 to PPC machine for @jBarz #1032
Comments
Copy/paste error? |
Fixed |
No objection from me whatsoever, but it does seem odd to point to a closed issue as the reason to give access... |
Opps , that was a cut and paste issue on my front. Updating. |
@nodejs/build ping |
SGTM |
Will catch up with @jBarz this week to get started. |
@mhdawson Any news? |
I have an ansible script working (#1075) need to make some more minor changes. Will attempt to get it done early this week. |
Moving this to #1261 where other accesses are tracked |
test-osuosl-ubuntu14-ppc64_le-3
It is a new machine I've setup to test out concurrent support for 4.8 and 4.9 compilers as well as the new ansible scripts. It is not connected to the CI yet, but will be as we get through this work.
John Barboza works at IBM with me and need access to a PPCBE machines in order to help with the work to have concurrent versions of the compilers and switch between them base on which version we are building.
I think he meets the requirements for temporary access in: https://github.com/nodejs/build/blob/master/doc/process/special_access_to_build_resources.md based on this subset of the criteria:
Length and consistency of involvement with Node.js working groups and/or community.
Consequences to the individual in case of mis-bahaviour. For example, would they potentially lose their job if they were reported as mis-behaving to their employer ? Would being banned from involvement in the Node.js community negatively affect them personally in some other way
definitely have an impact
Are there collaborators who work with the individual and can vouch for them.
@nodejs/build can I get an approver ?
The text was updated successfully, but these errors were encountered: