Skip to content
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

Closed
mhdawson opened this issue Dec 6, 2017 · 10 comments
Closed

Access to PPC machine for @jBarz #1032

mhdawson opened this issue Dec 6, 2017 · 10 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Dec 6, 2017

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.

  • He has contributed the z/OS port for libuv over the last year.

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

  • He works at IBM in the Node.js Runtime technologies group. Being banned would
    definitely have an impact

Are there collaborators who work with the individual and can vouch for them.

  • I'll vouch for him

@nodejs/build can I get an approver ?

@richardlau
Copy link
Member

ohn Barboza Gireesh

Copy/paste error?

@mhdawson
Copy link
Member Author

mhdawson commented Dec 6, 2017

Fixed

@Trott
Copy link
Member

Trott commented Dec 6, 2017

No objection from me whatsoever, but it does seem odd to point to a closed issue as the reason to give access...

@mhdawson
Copy link
Member Author

mhdawson commented Dec 6, 2017

Opps , that was a cut and paste issue on my front. Updating.

@mhdawson
Copy link
Member Author

@nodejs/build ping

@Trott
Copy link
Member

Trott commented Dec 14, 2017

SGTM

@mhdawson
Copy link
Member Author

mhdawson commented Jan 3, 2018

Will catch up with @jBarz this week to get started.

@seishun
Copy link
Contributor

seishun commented Jan 14, 2018

@mhdawson Any news?

@jBarz
Copy link
Contributor

jBarz commented Jan 14, 2018

I have an ansible script working (#1075) need to make some more minor changes. Will attempt to get it done early this week.

@maclover7
Copy link
Contributor

Moving this to #1261 where other accesses are tracked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants