<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 16Nov 2022, at 5:11 PM, Wes Bland <<a href="mailto:wesley@wesbland.com" class="">wesley@wesbland.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">The rules say you need to get four IMOVE (voting) orgs to support creating a WG at a meeting:<div class=""><br class=""></div><div class="">> Working groups can be established at MPI Forum meetings once at least four IMOVE organizations indicate support for that proposed Working Group.</div><div class=""><br class=""></div><div class="">So feel free to propose it at the December meeting and have some folks lined up to give it a thumbs up. Of course, in the meantime, folks are free to start getting together and discussing the topic. The old mailing list from 2008 is <a href="https://lists.mpi-forum.org/mailman/listinfo/mpi3-abi" class="">still around</a>, but I’d recommend you not use it since it uses our old naming scheme. Once the group is official, I’ll make the new list and GitHub org.</div></div></div></blockquote><div><br class=""></div><div>Thanks, I’ll rally the votes.</div><div><br class=""></div><div>Interested parties should ping me on Slack to be added to #wg-abi.<div class=""><br class=""></div><div class="">Somebody was optimistic enough to create <a href="https://github.com/mpiwg-abi/" class="">https://github.com/mpiwg-abi/</a> this morning but it’s a mystery who 😉</div><div class=""><br class=""></div><div class="">Jeff</div></div><br class=""><blockquote type="cite" class=""><div class=""><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class="">Thanks,</div><div class="">Wes</div></div><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Nov 16, 2022, at 1:54 AM, Jeff Hammond via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org" class="">mpi-forum@lists.mpi-forum.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">I don't know what we do to create new working groups with the post-COVID rules, but I would like to create and chair a WG focused on ABI standardization.</div><div class=""><br class=""></div><div class="">There is strong support for this effort in many user communities, including developers and maintainers of Spack, mpi4py, Julia MPI (MPI.jl), Rust MPI (rsmpi), PETSc and NVHPC SDK, to name a few. There are even a few implementers who have expressed support, but I won't name them for their own protection.</div><div class=""><br class=""></div><div class="">The problem is so exasperating for our users that there are at least two different projects devoted to mitigating ABI problems (not including shims built in to the aforementioned MPI wrappers):</div><div class=""><br class=""></div><div class=""><a href="https://github.com/cea-hpc/wi4mpi" class="">https://github.com/cea-hpc/wi4mpi</a><br class=""></div><div class=""><a href="https://github.com/eschnett/MPItrampoline" class="">https://github.com/eschnett/MPItrampoline</a><br class=""></div><div class=""><br class=""></div><div class="">I've written about this a bit already, for those who are interested. More material will be forthcoming once I have time for more experiments.</div><div class=""><br class=""></div><div class=""><a href="https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI.md" class="">https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI.md</a><br class=""></div><div class=""><a href="https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_2.md" class="">https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_2.md</a><br class=""></div><div class=""><a href="https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_3.md" class="">https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_3.md</a><br class=""></div><a href="https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_4.md" class="">https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_4.md</a><br clear="all" class=""><div class=""><br class=""></div><div class="">I understand this is a controversial topic, particularly for implementers. I hope that we can proceed objectively.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""><br class="">Jeff</div><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Jeff Hammond<br class=""><a href="mailto:jeff.science@gmail.com" target="_blank" class="">jeff.science@gmail.com</a><br class=""><a href="http://jeffhammond.github.io/" target="_blank" class="">http://jeffhammond.github.io/</a></div></div>
_______________________________________________<br class="">mpi-forum mailing list<br class=""><a href="mailto:mpi-forum@lists.mpi-forum.org" class="">mpi-forum@lists.mpi-forum.org</a><br class="">https://lists.mpi-forum.org/mailman/listinfo/mpi-forum<br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>