Skip to content

Ongoing access to z/OS machines for @jbarz #1081

Closed

Description

@mhdawson

It would be helpful if @jBarz could have ongoing access to the z/OS machines. I need some help in maintaining them etc and he is the most knowledgeable team member available.

John Barboza works at IBM. I think he meets the requirements for temporary access as defined 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-behaviour. 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?

Activity

  1. joaocgreis commented on Jan 15, 2018

    @joaocgreis
    Member

    I approve.

  2. gibfahn commented on Jan 15, 2018

    @gibfahn
    Member

    SGTM

  3. gdams commented on Jan 15, 2018

    @gdams
    Member

    I approve

  4. maclover7 commented on Jan 15, 2018

    @maclover7
    Contributor

    SGTM

  5. jBarz commented on Jan 26, 2018

    @jBarz
    Contributor

    Could someone give me access to the machine? (148.100.36.133)
    Libuv tests are failing due to timeout so I need to investigate that.
    Let me know if i should provide my public key

  6. mhdawson commented on Jan 29, 2018

    @mhdawson
    MemberAuthor

    Added key for @jBarz to test-marist-zos13-s390x-1 and test-marist-zos13-s390x-2

  7. maclover7 commented on Jun 6, 2018

    @maclover7
    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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions