Chapter Committees / Chairs -- We need Chapter Committees to review their chapters in three 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<https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?folder=1_LOwR_QeX_bwIe_eptiy0OxWaOvPQ8W8#gid=0> (including an un-numbered chapter for partitioned communication). This will let us track what has been done / what still needs to be done. 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/151 1b. "Uniform style for Fortran code" https://github.com/mpi-forum/mpi-standard/pull/145 Deadline: Jan 7, 2020 (Yes, that's an early deadline, but we need time to merge these PRs and fix conflicts with the second 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 the (non-Pythonized) head of the mpi-4.x branch. To be clear: this review does not include Embiggening. It is more-or-less the "MPI-3.1" style of function bindings. See this wiki page for instructions<https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing-initial-review>. For additional information, also see the Pythonization slides presented at the Forum last week<https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2ZODzdtDpI/edit#slide=id.g5d01a902fe_0_69>. If you have any questions or problems, let us know in the Embiggening WG. If you just want to compare the rendered PDF: * Here's a PDF from the head of the mpi-4.x branch<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8ad059.pdf> (i.e., old/original LaTeX) * Here's a PDF from the head of the Pythonization branch<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-d8ad059-pythonized-NOT-embiggened.pdf> with no Embiggening (i.e,. new/Python-rendered LaTeX) Deadline: 21 Jan, 2020 This gives 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. THIRD SET After Pythonization comes Embiggening. We need Chapter Committees to review their chapters to ensure that API parameters were embiggened properly. You can do this by finding all "POLY" kinds in the Pythonized LaTeX bindings, and you can see 2xC bindings and 2xF08 bindings in the rendered PDF in your chapter. If you have any questions or problems, let us know in the Embiggening WG. Also check that the existing MPI-3.1 "_x" functions -- and their corresponding non-"_x" versions -- are all rendered correctly. If you just want to compare the rendered PDF: * Here's a PDF from the head of the mpi-4.x branch<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8ad059.pdf> (i.e., old/original LaTeX) * Here's a PDF from the head of the Pythonization branch<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-d8ad059-pythonized-and-EMBIGGENED.pdf> with Embiggening enabled (i.e,. new/Python-rendered LaTeX) Deadline: 21 Jan, 2020 You can probably review the second and third sets in a single pass through the text. -- Jeff Squyres jsquy...@cisco.com<mailto:jsquy...@cisco.com>
_______________________________________________ mpi-forum mailing list mpi-forum@lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpi-forum
