<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="">Hi folks,<div class=""><br class=""></div><div class="">** Look at the numbered list for your action items before 2020-02-18! **<br class=""><div class=""><br class=""></div><div class="">Since we moved from Subversion to GitHub, there’s been a back and forth on whether the MPI Standard Source code should be open source or closed source. As you know (since most of you have access to it, we decided to keep the standard closed for a few reasons (avoiding rogue copies of the Standard was a big one), but recently, the scales have tipped back toward open sourcing and after talking to Bill and Martin some more, we think it’s finally time to open up the MPI Standard repository. Specifically, these are the issues that get addressed by moving to a public repository:</div><div class=""><br class=""></div><div class="">* Participation to the forum has a barrier to entry (i.e. me)</div><div class="">* Our current automated testing system is broken and will not be fixed</div><div class="">* We rely on special dispensation from GitHub for free, private repositories</div><div class=""><br class=""></div><div class="">I’ll be discussing this in more detail in Portland, but I want to make folks aware that this is coming now because it will have some impact on people who are actively working on text proposals. The mitigations here should be pretty straightforward and I have both slides (for a high level) and a wiki page (for details) on what’s happening and what you need to do about it.</div><div class=""><br class=""></div><div class="">The short version for the purpose of this email and <b class="">your action item leading up the forum next week is to do two thing</b>s:</div></div><div class=""><br class=""></div><div class="">1. Back up your branches.</div><div class="">2. Make a note for each of your open pull requests on where the are and what issues they’re attached to.</div><div class=""><br class=""></div><div class="">Detailed notes and the slides I’ll present in Portland on how to do this are here: <a href="https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository" class="">https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository</a></div><div class=""><br class=""></div><div class="">The plan is for me to flip this switch <b class="">DURING THE FEBRUARY MEETING!</b> This should not disrupt any readings for the meeting itself as none of the pull requests will actually be deleted, but they will all become stale and we’ll need to re-open new ones. The main benefit of doing this during the meeting is that if/when anyone has trouble, I’ll be there in person to provide live help to anyone else that’s there (sorry, Marc-Andre, you’ll need to follow my slides remotely 😀).</div><div class=""><br class=""></div><div class="">Please email me if you have questions or concerns. If there’s enough demand, I’d even be willing to do a short Virtual Meeting on this on Wednesday.</div><div class=""><br class=""></div><div class=""><div class="">Thanks,</div><div class="">Wesley</div></div></body></html>