<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
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!
<div class=""><br class="">
</div>
<div class="">(Last week, I accidentally sent this to the wrong WG -- I am [finally] re-sending it to the large count WG for proofing before I sent this out to the entire Forum mailing list / chapter chairs)<br class="">
<br class="">
-----------------------------------------<br class="">
<br class="">
We need Chapter Committees to review their chapters in 2 sets of upcoming document-wide changes that are slated to be merged "soon".<br class="">
<br class="">
After you complete a review, please put an "X" in the corresponding row/column for your chapter and the specified PR <a href="https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?folder=1_LOwR_QeX_bwIe_eptiy0OxWaOvPQ8W8#gid=0" class="">in
this Google spreadsheet</a>. This will let us track what has been done / what still needs to be done:<br class="">
<br class="">
</div>
<div class=""><span style="font-size: 36px;" class=""><b class=""><u class=""><font color="#ffff02" class="">FIRST SET</font><br class="">
</u></b></span><br class="">
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:<br class="">
<br class="">
1a. "Ticket 0 changes for MPI-4.x"<br class="">
<a href="https://github.com/mpi-forum/mpi-standard/pull/145" class="">https://github.com/mpi-forum/mpi-standard/pull/145</a><br class="">
1b. "Uniform style for Fortran code"<br class="">
https://github.com/mpi-forum/mpi-standard/pull/151<br class="">
<br class="">
<font color="#ff0000" class="">Deadline: Jan 7, 2020</font></div>
<div class=""> (Yes, that's an early deadline, but we need time to merge this and fix conflicts with the second set)</div>
<div class=""><br class="">
<b class=""><u style="font-size: 36px;" class=""><font color="#ffff02" class="">SECOND SET</font><br class="">
</u></b><br class="">
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.<br class="">
<br class="">
See this wiki page for instructions: <a href="https://github.com/mpiwg-large-count/large-count-" class="">https://github.com/mpiwg-large-count/large-count-</a>issues/wiki/pythonizing-initial-review<br class="">
<br class="">
Also please <a href="https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2ZODzdtDpI/edit#slide=id.g5d01a902fe_0_69" class="">see the Pythonization slides presented at the Forum last week</a>.</div>
<div class=""><br class="">
<font color="#ff0000" class="">Deadline: 21 Jan, 2020<br class="">
</font> This gives us time to finalize everything before the T-2 week deadline for the Portland Forum meeting.</div>
<div class=""><br class="">
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.<br class="">
<div class=""><br class="">
-- <br class="">
Jeff Squyres<br class="">
<a href="mailto:jsquyres@cisco.com" class="">jsquyres@cisco.com</a></div>
<br class="">
</div>
</body>
</html>