Working Group Guidelines

Guidelines for Managing Working Groups

Introduction

Working groups are set up as their own GitHub organizations. This makes things simpler to manage so that working groups can self organize without going through a single administrator. It also allows them to have their own working copy of the MPI Standard source to be able to work on new ideas internally before exposing them to the entire MPI Forum.

Setup

Most working groups already have an organization set up for them. The list of current working groups can be found on the main wiki page. If your working group does not have an organization yet, you are welcome to set one up yourself. Recommended steps for doing this are:

• Create a new GitHub Organization.
  • Use the open-source (free) version.
• Create a fork of the mpi-forum/mpi-standard repository into the working group organization.
  • This does not count as a private repository for the organization so it won't cost anything.
• Create a new public repository called -issues to organize the working group's internal issues and wiki

Access Management

How you decide to give access to your working group's organization is up to you. The simplest model is to just add each person who would like to participate in the working group to the list of members. You can do this under the "People" tab on the Organization's main page. See the screenshot below for the correct tab.

Then click the "Invite member" button:

Then enter their GitHub username/email/etc. to find the right person. If they don't have an account already, they will have to create one first.

Workflow

Just as working groups are welcome self-organize, how each working group decides on its workflow is also free to be changed. A suggested model is to be similar to the main MPI Forum organization:

• The source of the MPI Standard should be in a fork of mpi-forum/mpi-standard. This repository must be kept private to comply with the MPI Forum rules.
• Another public repository can keep track of the business of the working group (internal issues/wiki/etc.)

While a working group is working on issues that are not ready for the full MPI Forum, it should create branches on it's own fork of the source (mpiwg-/mpi-standard). When the text is ready, it should get an issue on the main MPI Forum issues repository mpi-forum/mpi-issues and create a pull request from the working group's fork of mpi-standard back to the main repository mpi-forum/mpi-standard. From this point, the Issue Workflow should be followed.