[mpiwg-persistence] FW: [Mpi-forum] MPI Chapter committee signoffs needed

[Skjellum, Anthony]

FYI ,we will review this tomorrow @ 10am eastern time meeting.
Tony



Anthony Skjellum, PhD

Professor of Computer Science and Chair of Excellence

Director, SimCenter

University of Tennessee at Chattanooga (UTC)

tony-skjellum at utc.edu  [or skjellum at gmail.com]

cell: 205-807-4968


________________________________
From: mpi-forum <mpi-forum-bounces at lists.mpi-forum.org> on behalf of William Gropp via mpi-forum <mpi-forum at lists.mpi-forum.org>
Sent: Tuesday, March 24, 2020 11:37 AM
To: mpi-forum at lists.mpi-forum.org <mpi-forum at lists.mpi-forum.org>
Cc: William Gropp <wgropp at illinois.edu>
Subject: [EXT]: [Mpi-forum] MPI Chapter committee signoffs needed

External Email
To everyone in the MPI Forum, but especially the chairs of the MPI Chapter Committees,

There are a number of updates that the Forum agreed to apply to the MPI standard that need to be reviewed and signed off by the chapter committees. The next group of these are the Fortran style changes, restricted to *not* include the change in lettercase for the Fortran keywords. As some of these had to be disentangled from commits that both fixed style issues and lettercase, these need to be reviewed again.  They were posted quite a while back, but only a few reviews were received. In retrospect, I needed to set up a separate column in the signoff spreadsheet, which I’ve now done. You will find that in Column E, labeled “Editor Fortran style updates (revised)”; the spreadsheet is in the same place:

https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?usp=sharing

Please do the following (if you are a chapter chair):

1) If everything is fine with the changes, enter YES in the column and row for your chapter(s).
2) If you find a problem that needs to be changed (not something that you want to add), then:
    a) Enter NO
    b) Enter a comment on the PR page ( https://github.com/mpi-forum/mpi-standard/pull/145 ) about the issue
    c) If I am able to make the correction, change your entry to YES

3) ANY OTHER ENTRY WILL BE CONSIDERED A NO. This is the same interpretation used for the other reviews - and using this sheet to communicate changes has already slowed down the process of applying these edits.

If you are on a chapter committee, please help your chapter chair.  Others are welcome to review and communicate issues either on the PR page or with the appropriate chapter chair.

I’d like to apply the Fortran style changes as soon as possible, and certainly within a week (April 1st, an appropriate day).

Thanks for your help!

Bill

William Gropp
Director and Chief Scientist, NCSA
Thomas M. Siebel Chair in Computer Science
University of Illinois Urbana-Champaign






This message is not from a UTC.EDU address. Caution should be used in clicking links and downloading attachments from unknown senders or unexpected email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-persistence/attachments/20200324/700b604f/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-persistence/attachments/20200324/700b604f/attachment.txt>