<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 all,<div class=""><br class=""></div><div class="">I just wanted remind folks that if you have an editor change that has been assigned to you, please try to finish those as soon as possible. Most are very short and can probably be done quickly. We have 12 that are already done (plus a few more I hope to do this afternoon). We’ll discuss these during the Virtual Meeting on <a href="https://time.is/1000AM_15_April_2020_in_Chicago" class="">Wednesday at 10:00am US Central time</a>.</div><div class=""><br class=""></div><div class="">I’m keeping track of the status of all of these issues here: <a href="https://github.com/mpi-forum/mpi-issues/projects/1" class="">https://github.com/mpi-forum/mpi-issues/projects/1</a></div><div class=""><br class=""></div><div class="">The issues we still need to discuss are in the <b class="">“To Be Classified”</b> column. We’ll talk about those (time permitting) on Wednesday after the Sessions discussion.</div><div class=""><br class=""></div><div class="">The issues that have been scoped and assigned to someone are in the<b class=""> “Awaiting Implementation”</b> column. If you have something in that column, you can go ahead and work on it and create a pull request. When you do that, I’ll see it and update the board. Please make sure that when you do, you reference the original issue in the PR description saying:</div><div class=""><br class=""></div><div class="">Fixes mpi-forum/mpi-issues#1234</div><div class=""><br class=""></div><div class="">This is the best way to make sure the automatic links are created. If you try to do the links manually by doing something like using Markdown to make the links [like this](<a href="https://github.com/mpi-forum/mpi-issues/issues/1234" class="">https://github.com/mpi-forum/mpi-issues/issues/1234</a>), then the link doesn’t work properly.</div><div class=""><br class=""></div><div class="">The issues that have open pull requests implementing them and are ready for discussion are in <b class="">“Awaiting Informal Reading”</b>. My plan is to clear out this column each Wednesday during the virtual meeting. If you have something in this column, please plan to attend the call on Wednesday to read your PR. For this week so far, that includes:</div><div class=""><br class=""></div><div class="">* Guillaume</div><div class="">* George</div><div class="">* Thomas</div><div class="">* Wesley / Aurelien</div><div class="">* Joseph</div><div class=""><br class=""></div><div class="">The last column, <b class="">“Finished Informal Reading"</b> is for the issues that have already been implemented and read. So far, that includes things that were done by the Pythonization branch, but I’ll move things over there as we work through the issues.</div><div class=""><br class=""></div><div class="">Thanks to all for helping to clear this backlog. If you’re willing to contribute by helping with one of these issues, there are a number of issues assigned to the document editor (Bill) (<a href="https://github.com/mpi-forum/mpi-issues/projects/1?card_filter_query=assignee:wgropp" class="">https://github.com/mpi-forum/mpi-issues/projects/1?card_filter_query=assignee%3Awgropp</a>) that could be picked up by anyone. Some probably require his expertise, but I’d be happy to point you toward some easy ones. You can also talk to the chapter committee chair of your favorite chapter and I’m sure they’d be happy to share the workload.</div><div class=""><br class=""></div><div class=""><div class="">Thanks and talk to you Wednesday,</div><div class="">Wes</div></div></body></html>