<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
The document at <br><br> http://meetings.mpi-forum.org/MPI_3.0_main_page.php<br><br>in the voting rules section is the document with the voting rules that was circulated on the list several months ago, and reflects the feedback received.<br><br>A May final vote on MPI 3.0 in May would mean that first readings must be completed by the end of the Oct meeting, with 1st and 2nd votes the first two meeting of 2012. The final vote is a chapter by chapter vote - single vote - with the meeting before that reading being devoted to the final reading. What appears on the list is a summary of things we have talked about over the last several meetings.<br><br>As I have said before, the time-lines and rules we put together are supposed to help us. If they get in the way, they should be changed.<br><br>Rich<br><br><div>> From: bwbarre@sandia.gov<br>> To: mpi-forum@lists.mpi-forum.org<br>> Date: Thu, 21 Jul 2011 14:28:18 +0000<br>> Subject: Re: [Mpi-forum] 2012 tentative meeting agenda<br>> <br>> I think the concern in the room was that "Final vote" seemed to imply that<br>> we were cutting things rather thin. If we need two votes for voting in<br>> MPI-3, that would mean March is the first, and September is the last<br>> opportunity for a first reading.<br>> <br>> The lack of a clear, written process available on the public web page<br>> makes it difficult to know what "final vote" means in this context.<br>> <br>> Brian<br>> <br>> On 7/21/11 7:01 AM, "Underwood, Keith D" <keith.d.underwood@intel.com><br>> wrote:<br>> <br>> >The plan we discussed at a couple of the meetings for MPI-3.0 was kind of<br>> >a feature based / date based hybrid. Basically, it was ³gate on these<br>> >features within reason². There were two motivations for the ³within<br>> >reason² clause. The first motivation was that we were all tired of<br>> >traveling every 8 weeks and wanted to slow down the meeting schedule just<br>> >a little after the 3.0 release. The second motivation was that it felt<br>> >like we should have 3.0 done at some point if we wanted to maintain some<br>> >general credibility. May was discussed as a target because all of the<br>> >likely gates thought they could be done by then.<br>> > <br>> >Keith<br>> > <br>> >From: mpi-forum-bounces@lists.mpi-forum.org<br>> >[mailto:mpi-forum-bounces@lists.mpi-forum.org] On Behalf Of RICHARD GRAHAM<br>> >Sent: Thursday, July 21, 2011 4:34 AM<br>> >To: mpi-forum@lists.mpi-forum.org<br>> >Subject: Re: [Mpi-forum] 2012 tentative meeting agenda<br>> ><br>> ><br>> > <br>> >Thanks !!!<br>> ><br>> >If there are further conflicts with the proposed dates:<br>> ><br>> > Jan 9-11: San Jose, CA<br>> > March 5-7: Chicago, IL<br>> > May 7-9: San Jose, CA Final MPI 3.0 vote<br>> > July 16-19: Chicago, IL<br>> > Sept: In conjunction with EuroMPI<br>> > Dec 3-6: San Jose, CA<br>> ><br>> >Please send e-mail to the list by 7/29/2011. There seemed to be a desire<br>> >to have a date cutoff for MPI-3.0, which is why the May meeting was<br>> >chosen (actually discussed) at the previous meeting. This is really up<br>> >to us as to whether to push this data back to include the three top<br>> >priority features.<br>> ><br>> >Also, seemed like meeting in Portland are a no-go, so will continue at<br>> >our current locations.<br>> ><br>> >Rich<br>> >> From: jsquyres@cisco.com<br>> >> Date: Wed, 20 Jul 2011 21:36:53 -0500<br>> >> To: mpi-forum@lists.mpi-forum.org<br>> >> Subject: Re: [Mpi-forum] 2012 tentative meeting agenda<br>> >> <br>> >> Rich / those who didn't attend the Chicago meeting --<br>> >> <br>> >> Here's the feedback from the Chicago attendees on the dates for<br>> >>meetings next year:<br>> >> <br>> >> 2012<br>> >> ----<br>> >> Jan 9-11: San Jose, CA<br>> >> <br>> >> --> Non-US based attendees need the Jan meeting dates fixed<br>> >> ASAP to buy plane tickets.<br>> >> <br>> >> March 5-7: Chicago, IL<br>> >> May 7-9: San Jose, CA Final MPI 3.0 vote<br>> >> <br>> >> --> There was significant confusion about this notation<br>> >> ("Final MPI 3.0 vote").<br>> >> <br>> >> 1. Is this the final vote for the entirety of MPI-3,<br>> >> meaning that all chapter/ticket 2nd votes must be complete<br>> >> by the March?<br>> >> <br>> >> 2. Everyone thought we were "gating"<br>> >> MPI-3.0 on RMA, Fault Tolerance (stabilization), MPIT,<br>> >> and Neighborhood Collectives. RMA and NC look very good<br>> >> (passed 1st vote), MPIT needs a little more work, and<br>> >> FT needs (potentially) a lot more work. Is this notation<br>> >> just an assumption/hope that FT will be ready for its<br>> >> final official reading in October?<br>> >> <br>> >> July 16-19: Chicago, IL<br>> >> Sept: In conjunction with EuroMPI<br>> >> Dec 3-6: San Jose, CA<br>> >> <br>> >> No one saw any immediate conflicts with these dates or locations. I<br>> >>urged everyone to double check their calendars and email this list ASAP<br>> >>if they find anything.<br>> >> <br>> >> <br>> >> <br>> >> On Jun 8, 2011, at 10:05 AM, Graham, Richard L. wrote:<br>> >> <br>> >> > At the last meeting we had general agreement to continue the current<br>> >>pace of meetings until MPI 3.0 is finalized, and then go down to 4<br>> >>meetings a year, but longer meetings. The time frame we have set for MPI<br>> >>3.0 means that the first 3 meetings in 2012 will continue at the current<br>> >>pace, and then we will cut back to quarterly. Here is a first suggestion<br>> >>for meeting dates please send any conflicts that you are aware of.<br>> >>Also, there has been a push to move the west coast meetings to Portland,<br>> >>OR are people OK with that ?<br>> >> > <br>> >> > Thanks,<br>> >> > Rich<br>> >> > <br>> >> > Jan 9-11: Portland, OR<br>> >> > March 5-7: Chicago, IL<br>> >> > April 30 May 2: Portland, OR Final MPI 3.0 vote<br>> >> > June 25-28: Chicago, IL<br>> >> > Sept: In conjunction with EuroMPI<br>> >> > Dec 3-6: Portland, OR<br>> >> > _______________________________________________<br>> >> > mpi-forum mailing list<br>> >> > mpi-forum@lists.mpi-forum.org<br>> >> > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum<br>> >> <br>> >> <br>> >> -- <br>> >> Jeff Squyres<br>> >> jsquyres@cisco.com<br>> >> For corporate legal information go to:<br>> >> http://www.cisco.com/web/about/doing_business/legal/cri/<br>> >> <br>> >> <br>> >> _______________________________________________<br>> >> mpi-forum mailing list<br>> >> mpi-forum@lists.mpi-forum.org<br>> >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum<br>> ><br>> ><br>> ><br>> ><br>> >_______________________________________________<br>> >mpi-forum mailing list<br>> >mpi-forum@lists.mpi-forum.org<br>> >http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum<br>> <br>> <br>> -- <br>> Brian W. Barrett<br>> Dept. 1423: Scalable System Software<br>> Sandia National Laboratories<br>> <br>> <br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> mpi-forum mailing list<br>> mpi-forum@lists.mpi-forum.org<br>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum<br></div> </div></body>
</html>