Hi all,
After some break, we’ll have an MPI Forum Virtual Meeting tomorrow at the usual time – 10am CT – and using the usual link, which is on github at the usual place.
As mentioned before, the goal tomorrow is get an overview of the state in the various working groups and chapter committees in our progress to MPI 4.1. We will use this to build a todo/gating issues list during the September meeting and with that plan a (hopefully) concrete timeline for MPI 4.1.
However, this means that we need your input on two things:
The status of the open items on the github boards (see Wesley’s email from July 6th)
Any open issues from the WGs that should be considered for MPI 4.1 (or which ones can be postponed to MPI 5.0)
(keep in mind, though, MPI 4.1 was not supposed to include major items or additions, just cleanup and minor urgent changes)
Therefore, I would like to ask all of to review these items above (especially if you are tagged on one of the items on the github boards). Also, it would be really helpful, if each WG lead would be able to join us tomorrow or have a representative, so we can discuss the open issues.
For reference, here are the links to the boards:
* https://github.com/mpi-forum/mpi-issues/projects/3 (GitHub’s old project boards version)
* https://github.com/orgs/mpi-forum/projects/1/views/2 (GitHub’s new project boards version)
Thanks and hopefully see/hear you all tomorrow,
Martin
--
Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems
Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching
Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ)
Email: schulzm(a)in.tum.de
This conflicts with the Fortran WG5 meeting, although I guess I’m on the only affected person, since Bill Long doesn’t appear to have any outstanding issues with MPI right now.
https://github.com/mpi-forum/mpi-issues/issues/17 <https://github.com/mpi-forum/mpi-issues/issues/17> is a good one for 4.1, since it is merely a clarification. I took care of some of the work, but have no time to work on the LaTeX changes to implement it.
I’ve asked the RMA WG to make forward progress on https://github.com/mpi-forum/mpi-issues/issues/23 <https://github.com/mpi-forum/mpi-issues/issues/23>, which is one of a handful of issues that are reasonable to do in 4.1.
While I like to be active in the discussion, I no longer have the ability to work on the LaTeX document, particularly since everything about it has changed since I last edited it, and because I no longer use LaTeX regularly (sob #CorporateLife).
Jeff
> On 6Jul 2022, at 6:00 PM, Wes Bland via mpi-forum <mpi-forum(a)lists.mpi-forum.org> wrote:
>
> Hi all,
>
> We’re going to discuss this at a virtual meeting on July 20th, but as there is some potential pre-work for the owners of these issues, I wanted to give people a preview so they could get started early.
>
> As discussed during the run up to MPI 4.0, we intend MPI 4.1 to be a (relatively) quick update to the MPI Standard to fix more minor issues with unclear semantics, terms, general formatting, etc. This release is not intended to include a large number of new features (though there will of course be some).
>
> During MPI 4.0, we started using the GitHub Projects features to keep track of how our work was progressing and to understand what our targets were. We also made boards for MPI 4.1 and MPI 5.0. I’d like to draw your attention to the MPI 4.1 project board for the discussion in a few weeks. Both of the boards show the same data. They just use different layouts. Feel free to look at whichever you like best.
>
> * https://github.com/mpi-forum/mpi-issues/projects/3 <https://github.com/mpi-forum/mpi-issues/projects/3> (GitHub’s old project boards version)
> * https://github.com/orgs/mpi-forum/projects/1/views/2 <https://github.com/orgs/mpi-forum/projects/1/views/2> (GitHub’s new project boards version)
>
> I want to point out that we currently have 148 open issues marked for MPI 4.1, which means there is a lot of work that we hope to have done in the next year or so in order to release MPI 4.1. Each of these items has an owner that should be responsible for moving the issue forward. To find out which issues belong to you, take a look here <https://github.com/orgs/mpi-forum/projects/1/views/2?query=is:open+sort:upd…>. If there is something with your name on it, that means there is something in your chapter that needs work. Please take a look so we can prioritize our work for MPI 4.1. Please also plan to attend the virtual meeting on July 20th to participate in the discussion.
>
> If you no longer plan to actively participate in the MPI Forum, please let Martin and I know so we can help make sure that someone else can pick up this work. We’re not out to shame people here, but holding on to an issue and never working on it prevents someone else from doing the work (I’m guilty of this myself here).
>
> Thanks to everyone for contributing! Being involved in the MPI Forum is a volunteer position, and all of the work that each of you do is greatly appreciated to help the MPI community.
>
> Thanks,
> Wes
> _______________________________________________
> mpi-forum mailing list
> mpi-forum(a)lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum
Hi all,
We’re going to discuss this at a virtual meeting on July 20th, but as there is some potential pre-work for the owners of these issues, I wanted to give people a preview so they could get started early.
As discussed during the run up to MPI 4.0, we intend MPI 4.1 to be a (relatively) quick update to the MPI Standard to fix more minor issues with unclear semantics, terms, general formatting, etc. This release is not intended to include a large number of new features (though there will of course be some).
During MPI 4.0, we started using the GitHub Projects features to keep track of how our work was progressing and to understand what our targets were. We also made boards for MPI 4.1 and MPI 5.0. I’d like to draw your attention to the MPI 4.1 project board for the discussion in a few weeks. Both of the boards show the same data. They just use different layouts. Feel free to look at whichever you like best.
* https://github.com/mpi-forum/mpi-issues/projects/3 <https://github.com/mpi-forum/mpi-issues/projects/3> (GitHub’s old project boards version)
* https://github.com/orgs/mpi-forum/projects/1/views/2 <https://github.com/orgs/mpi-forum/projects/1/views/2> (GitHub’s new project boards version)
I want to point out that we currently have 148 open issues marked for MPI 4.1, which means there is a lot of work that we hope to have done in the next year or so in order to release MPI 4.1. Each of these items has an owner that should be responsible for moving the issue forward. To find out which issues belong to you, take a look here <https://github.com/orgs/mpi-forum/projects/1/views/2?query=is:open+sort:upd…>. If there is something with your name on it, that means there is something in your chapter that needs work. Please take a look so we can prioritize our work for MPI 4.1. Please also plan to attend the virtual meeting on July 20th to participate in the discussion.
If you no longer plan to actively participate in the MPI Forum, please let Martin and I know so we can help make sure that someone else can pick up this work. We’re not out to shame people here, but holding on to an issue and never working on it prevents someone else from doing the work (I’m guilty of this myself here).
Thanks to everyone for contributing! Being involved in the MPI Forum is a volunteer position, and all of the work that each of you do is greatly appreciated to help the MPI community.
Thanks,
Wes
