Mainframe Open Education Project
  • Welcome: Learn & Contribute to MOE
    • MOE Vision, Mission and Content Phases
    • Who Can Contribute?
    • Contributor Log In
    • Earn A Contributor Badge
    • MOE Management System
    • MOE Events
    • Project Support
    • Legal Disclaimer, Copyright and License
    • Code of Conduct
    • Project Governance
    • Why MOE
  • Introduction: What is Enterprise Computing?
  • Chapter 1: What is a Mainframe Today?
    • Role of the Mainframe Today
      • Mainframe and the Cloud
      • Enterprise Computing
      • Hybrid Cloud
    • Who Uses the Mainframe and Why
    • Mainframe versus Server
    • Mainframe Basic Architecture & Components
    • How the Mainframe Works
    • Mainframe Security Myths
    • Mainframe Evolution
    • Mainframe Modernization
    • Video: ITs Best Kept Secret
    • Get Ready: Talk Like a Mainframer
    • Looking Back: The First 50 Years of Mainframe
  • Chapter 2: Foundational Technology
    • Brief Introduction to z/OS
    • TSO/E, ISPF, and UNIX System Services (USS): Interactive facilities of z/OS
    • Data Sets and How They Work
    • Job Control Language and System Display and Search Facility
      • Understanding the JCL(Job Control Language)
        • Understanding the JOB Statement
        • Understanding the EXEC Statement
        • Understanding the DD Statement
        • Creating a Physical Sequential (PS)
        • Understanding Libraries in JCL
        • Understanding Instream Procedures, Cataloged Procedures, and Symbolic Parameters in JCL
      • Utilities
        • IEBCOMPR
        • IEBGENER
          • Copying Between Sequential Datasets and PDS Members Using IEBGENER
          • Generate PDS member while copying
          • Copying a UNIX File to a PS File
        • IEBCOPY
          • IEBCOPY selective copy using select statements
          • IEBCOPY Exclude members while copying
          • IEBCOPY renaming member while copying
      • GDG
        • GDG parameters
        • GDG base
        • GDG Generation
          • Referencing GDG Generations Using Relative Numbers
        • Alter and Delete GDG
    • Enterprise Software Development and Implementation
    • Programming languages for Mainframe
    • Modern Application Management
    • Video: System Overview
    • Video: MVS Using Dynamic Allocations
    • Article: Red Hat OpenShift 4.7 on IBM Z Is a Game Changer for Container Orchestration and Managemen
    • IBM z16
  • Chapter 3: Roles in Mainframe
    • Roles and Categories
      • Category Definitions
  • Chapter 4: Deeper Dive in Role Chosen
    • IT Operations and System Support and Services
    • IT Business/Software Product Application Development and Support
    • IT Software Engineers
    • IT Architects
  • Chapter 5: Career Path Opportunities
    • Learning Programs
    • Job Opportunities
    • Career Event Calendar
    • Open to Hire
  • Mainframe Events and Conferences 2024
  • My Mainframe Journey: From Student to Professional
  • Backlog on Topics
  • Additional Community Resources
    • Communities
    • Courses, Tutorials, Manuals
    • Education Programs
    • IBM Mainframe Timeshare Services
  • Digital Certificate Badges
    • z/OS Mainframe Practitioner
  • Reviewer List
  • Modern Mainframe
    • What is a modern mainframe environment?
    • z/OSMF
      • What is z/OSMF?
      • Why it is important in a mainframe shop
      • z/OSMF Learning Materials
    • Zowe
Powered by GitBook
On this page
  • Overview
  • Project Roles
  • Editor
  • Reviewer
  • Leads
  • Release Process
  • Conflict Resolution and Voting
  • Communication

Was this helpful?

  1. Welcome: Learn & Contribute to MOE

Project Governance

Learn more about the governance of Mainframe Open Education.

PreviousCode of ConductNextWhy MOE

Last updated 1 month ago

Was this helpful?

Overview

This project aims to be governed in a transparent, accessible way for the benefit of the community. All participation in this project is open and not bound to corporate affiliation. Participants are bound to the .

Project Roles

Editor

The Editor role is the starting role for anyone participating in the project and wishing to contribute education assets.

Process for becoming a Editor

  • Ensure your contribution is inline with the project's guidelines

  • Submit your contribution as a Change Request

  • Have your submission approved by a Reviewer

Reviewer

The Reviewer role enables the contributor to approve Change Requests, but also comes with the responsibility of being a responsible leader in the community.

The current list of active Reviewer can be seen at the .

Process for becoming a Reviewer

  • Show your experience with the project through contributions and engagement on the community channels.

  • Voted to become a Reviewer by the majority of the currently active Reviewer.

Reviewer responsibilities

  • Monitor Slack

  • Triage Discussions

  • Make sure that ongoing Change Requests are moving forward at the right pace or closing them

Emeritus status

If a Reviewer is no longer interested or cannot perform the duties listed above, they should volunteer to be moved to emeritus status. In extreme cases, this can also occur by a vote of the Reviewers per the voting process below.

Leads

The MOE Project Lead is designated to the Technical Steering Committee. They are the primary point of contact for the project and representative to the Open Mainframe Project's Technical Advisory Council. The Lead(s) will be responsible for the overall project health and direction, coordination of activities, and working with other projects and committees as needed for the continued growth of the project.

Release Process

Project releases will occur as soon as a Reviewer approves a Change Request. Any changes will be live thereafter.

Conflict Resolution and Voting

In general, we prefer that Issues, Discussions and Reviewer membership are amicably worked out between the persons involved.

If a dispute cannot be decided independently, the Reviewers can be called in to decide an issue. If the Reviewers themselves cannot decide an issue, the issue will be resolved by voting. The voting process is a simple majority in which each committer receives one vote.

Communication

  • Keep all communication on open channels

  • Be respectful of time and language differences between the community members

  • Ensure tools are able to be used by community members regardless of their region

This project, just like all of open source, is a global community. In addition to the , this project will:

If you have concerns about communication challenges for this project, .

Code of Conduct
Reviewer List
Code of Conduct
please contact a Reviewer