[Mpi-forum] June MPI Forum Meeting in Aachen

[Dan Holmes]

Hi Martin,

Please schedule Point-to-point WG time so we can discuss and progress the two active topics:

* Allocating receive and freeing send (ARECV and FSEND) - still in design phase

* INFO query - lengthy discussion on git issue #63 <https://github.com/mpi-forum/mpi-issues/issues/63> comments - needs confirmation of resolution

I would also like to progress issue #63 formally, if possible. It has had a reading at the last meeting. The discussion via git comments seems to have resolved the objections raised at the March meeting, which clears the way for the issue to progress as is, without any text/semantic changes.

So, please schedule a 1st vote for issue #63 (pull request #27).
https://github.com/mpi-forum/mpi-issues/issues/63 <https://github.com/mpi-forum/mpi-issues/issues/63>
https://github.com/mpi-forum/mpi-standard/pull/27 <https://github.com/mpi-forum/mpi-standard/pull/27>
Draft standard PDF, as read at previous meeting:
https://github.com/mpi-forum/mpi-standard/files/772368/mpi-report.pdf <https://github.com/mpi-forum/mpi-standard/files/772368/mpi-report.pdf>
(Replacement text is highlighted, see pages 251, 252. For removed/replaced text, see git diff from pull request.)

If the WG time uncovers continued strong objections, then we may decide during the meeting to withdraw/postpone the vote.

Cheers,
Dan.

> On 13 May 2017, at 11:02, Martin Schulz <schulzm at llnl.gov> wrote:
> 
> Hi all,
> 
> The June forum meeting is coming closer - June 14-16 in Aachen, Germany. The logistics page for the meeting is at:
> 
> http://mpi-forum.org/meetings/2017/06/logistics <http://mpi-forum.org/meetings/2017/06/logistics>
> 
> Please register as soon as you can. If you are unsure whether you can travel but are hoping to, or if your approval process hasn’t gotten to the point where you can register, please let me know directly. It would be really helpful to get a mostly correct head count as well as an idea on whether we’ll hit quota sooner than later.
> 
> I started a draft of  the agenda at:
> 
> http://mpi-forum.org/meetings/2017/06/agenda <http://mpi-forum.org/meetings/2017/06/agenda>
> 
> Currently, I am planning on 1.5 days of WGs followed by 1.5 days of plenaries. Based on demand, though, I may move this around and extend the WGs to two full days, which would also move the voting block to later in the day.
> 
> Also, please note that the two week mark for announcing readings, erratas and ballots is on May 30th - hence, please send me this information before this date. However, also here earlier is better - no need to wait until May 30th!
> 
> Further, WG chairs: please send me all requests for WG times (how long and possible conflicts).
> 
> Finally, the June meeting is traditionally the meeting where we make decisions about the locations for next year. With the meeting being outside the US this time, which typically influences the attendance significantly, I wanted to bring this up ahead of time via email. If you have any suggestions or particular dislikes, or if you are willing to host a forum meeting at your site, please let me know and I will incorporate this in the discussion in Aachen. As for dates - if we stick with the normal rhythm, this would get us to:
> 	Spring meeting: 3/5 to 3/8
> 	Summer meeting: 6/4-6/7
> 	Fall meeting: with EuroMPI - trying to get further information 
> 	Winter meeting: 12/3-12/6
> If these dates cause any major conflicts, please let me know as well.
> 
> Thanks!
> 
> Martin
> 
> 
> _______________________________________________
> mpi-forum mailing list
> mpi-forum at lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20170515/29860c86/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20170515/29860c86/attachment.ksh>