Skip to content

Access to z/OS machines for @ miladfarca #1686

Closed

Description

@mhdawson

Milad Farazmand works at IBM with me and need access to the z/OS machines in order to investigate: #1685,

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:

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?

Activity

  1. refack commented on Feb 11, 2019

    @refack
    Contributor

    +1

  2. mhdawson commented on Feb 11, 2019

    @mhdawson
    MemberAuthor

    @refack I'm travelling this week. Once we have enough approvals could you help get Milad's key onto the machine?

  3. Trott commented on Feb 11, 2019

    @Trott
    Member

    +1 SGTM

  4. refack commented on Feb 11, 2019

    @refack
    Contributor

    @miladfarca I've added your GitHub public keys to https://ci.nodejs.org/computer/test-marist-zos13-s390x-2/
    (a.k.a. Unix1@test-marist-zos13-s390x-2)

    Please stop the jenkins service while doing testing, and restart when finished.
    Note: the CI runs as the iojs user, so either su as it, or make sure file permissions are intact when done.

    Happy debugging 🎏

  5. self-assigned this
    on Feb 11, 2019
  6. mhdawson commented on Feb 13, 2019

    @mhdawson
    MemberAuthor

    @refack thanks again for helping with this:)

  7. targos commented on Apr 17, 2023

    @targos
    Member

    Do we need to keep this open?

  8. miladfarca commented on Apr 21, 2023

    @miladfarca
    Contributor

    We should be able to close it.

  9. richardlau commented on Oct 9, 2024

    @richardlau
    Member

    z/OS VMs in question no longer exist -- they were shut down as they needed updating to be able to continue to build libuv and the host machine was being updated to a newer version of z/OS.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions