[MPIWG Fortran] DRAFT: Chapter Committees ACTION NEEDED

[Jeff Squyres (jsquyres)]

This is a DRAFT of what I'd like to send to the Forum to get all Chapter Committees to review the document-wide stuff that we need reviewed.  Please send comments / suggestions to me.  Thanks!

-----------------------------------------

We need Chapter Committees to review their chapters in 2 sets of upcoming document-wide changes that are slated to be merged "soon".

After you complete a review, please put an "X" in the corresponding row/column for your chapter and the specified PR in this Google spreadsheet.  This will let us track what has been done / what still needs to be done:

  https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?folder=1_LOwR_QeX_bwIe_eptiy0OxWaOvPQ8W8#gid=0

==> FIRST SET

Bill Gropp (the MPI Standard document Editor) has two PRs with "ticket 0" changes.  However, the changes are pervasive and touch a LOT of the document.  We therefore need Chapter Committees to review their chapters in the following two PRs:

1a. "Ticket 0 changes for MPI-4.x"
    https://github.com/mpi-forum/mpi-standard/pull/145
1b. "Uniform style for Fortran code"
    https://github.com/mpi-forum/mpi-standard/pull/151

**** BILL: what deadline do you want to set?

==> SECOND SET

The Pythonization group has Pythonized the bindings in the entire document.  We've completed a first correctness pass over the work, but we need more eyes to compare the end result of our work to (at least) the MPI-3.1 document -- or, better yet, to the head of the mpi-4.x branch.

See this wiki page for instructions: https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing-initial-review

Also please see the Pythonization slides presented at the Forum this week: https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2ZODzdtDpI/edit#slide=id.g5d01a902fe_0_69

The Pythonization group needs your reviews BY *** 21 JAN 2020 *** to give us time to finalize everything before the T-2 week deadline for the Portland Forum meeting.

NOTE: At the ABQ Forum meeting, I asked you to commit/PR your approvals.json file that resulted from running the tool.  This is no longer necessary -- please just mark the google spreadsheet as described above.

-- 
Jeff Squyres
jsquyres at cisco.com