<font size=2 face="sans-serif">I want to clarify that I did object that
the way we were handling votes at this last meeting was inconsistent with
previous meetings, but those people who spoke up simply indicated that
I was mistaken. I regret that I did not push the issue further, but
there did not appear to me to be an intention to change how things were
done. It appeared to me that as a group we were simply wrong about our
understanding of the process. </font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif">Dave</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Jeff Hammond <jhammond@alcf.anl.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Main MPI Forum mailing
list <mpi-forum@lists.mpi-forum.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">05/30/2012 08:32 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [Mpi-forum]
Voting results</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">mpi-forum-bounces@lists.mpi-forum.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>On Wed, May 30, 2012 at 7:57 PM, George Bosilca <bosilca@eecs.utk.edu>
wrote:<br>
> In general, the term "simple majority" is biased by our
origins. In US it simply means over 1/2 of the valid votes cast (so everything
except the absentees). Everywhere else, and this includes some other english
speaking countries, a simple majority is the greatest number of parts,
in other words the choice that got more votes than any other.<br>
<br>
Indeed, there are only two countries - none outside of North American<br>
- that use the first definition<br>
[</font></tt><a href=http://en.wikipedia.org/wiki/Simple_majority><tt><font size=2>http://en.wikipedia.org/wiki/Simple_majority</font></tt></a><tt><font size=2>].<br>
<br>
> I can hardly believe I'm the only one with this understanding of the
simple majority term. Moreover, I remember live discussion where we clearly
stated that there __are__ differences between the "abstain" and
the "no"vote, and that one must carefully choose her vote. While
these discussions were not in the context of first of second voting, they
were at least in the context of readings (which is similarly important
as it decide the original fate of a ticket). Maintaining several possible
interpretations, and changing the counting before a remote vote doesn't
make the process more transparent.<br>
<br>
I agree completely. If abstain=no then there is no point in having
both.<br>
<br>
> Another valid issue raised during this meeting was about the blessing
from the user community. Interestingly enough for a standard targeted toward
a user community, such an issue was never brought forward. I think users
should be an important factor in our decisions, as important as their contributions
to the ongoing discussions. And yes the forum should grant them a significant
period of time between the moment when we vote a ticket and the moment
when this ticket gets into the standard. Our users will clearly take advantage
of such a grace period to thoughtfully evaluate the proposal and raise
any issues they might have encountered. We should have done this from day
one!<br>
<br>
No users asked for C++ bindings to be deprecated and a number<br>
protested quite vigorously. Many users have asked for active messages<br>
and the Forum is has made no progress on this. Even something as<br>
simple as MPI_Iwin_create, which was requested by multiple users and<br>
had a very valid use case, was shot down in the RMA working group<br>
because it was too hard for Brian to implement. The notion that users<br>
are a high priority to the Forum is rather farcical as far as I'm<br>
concerned. I wish this was not the case.<br>
<br>
Jeff<br>
<br>
> On May 31, 2012, at 06:10 , Bronis R. de Supinski wrote:<br>
><br>
>><br>
>> All:<br>
>><br>
>> Hmm. Quite the controversy. However, the rules as enforced<br>
>> in Japan are consistent with my understanding of what they<br>
>> have always been. More importantly, they are consistent<br>
>> with the wording in the bylaws. Here is what Jeff quoted:<br>
>><br>
>> a simple majority is defined as a simple majority<br>
>> of those present and eligible to vote.<br>
>><br>
>> Those who abstained were present and eligible to vote.<br>
>> They did not vote yes. The effect is that they voted<br>
>> "no" by this definition. If they did not want their<br>
>> vote effectively to be "no" then they should have left<br>
>> the room. I recall several instances in which someone<br>
>> was out of the room (perhaps even momentarily for a bio<br>
>> break) and Jeff recorded their vote as "not present".<br>
>> See the definition above -- they then do not count as<br>
>> present so they do not figure into the required "yes"
count.<br>
>><br>
>> As I stated, my understanding of the rules is consistent<br>
>> with the interpretation used in Japan. I would object to<br>
>> any other interpretation since the by-laws are actually<br>
>> clear on this point. I agree that the by-laws should be<br>
>> clear in general; while I think they are clear, I would<br>
>> not object to a clarifying statement being added to the<br>
>> effect that "abstentions are effectively negative votes."<br>
>> I think we have many other issues that should be made<br>
>> concrete in the by-laws and this is the least important.<br>
>> What is required to pass a first reading is probably the<br>
>> most obvious issue.<br>
>><br>
>> Bronis<br>
>><br>
>><br>
>><br>
>><br>
>> On Wed, 30 May 2012, Fab Tillier wrote:<br>
>><br>
>>> Jeff Squyres wrote on Wed, 30 May 2012 at 12:12:26<br>
>>><br>
>>>> On May 30, 2012, at 2:57 PM, Jeff Hammond wrote:<br>
>>>><br>
>>>>>> The fact that some votes were still recorded as
'abstain' is an indication<br>
>>>>>> that this bylaw change was half baked.<br>
>>>>><br>
>>>>> Especially when the meeting is attended by so few
people due to the<br>
>>>>> location. It seems like a weasel tactic to pick
a remote location to<br>
>>>>> change the by-laws with a single vote.<br>
>>>><br>
>>>><br>
>>>> To be clear, the process document states:<br>
>>>><br>
>>>> For the purposes of voting, a simple majority
is defined as a simple<br>
>>>> majority of those present and eligible to
vote.<br>
>>>> In the context of the document, the phrase "simple
majority" is used to<br>
>>>> describe what is needed for ballots to pass; this sentence
is attempting to<br>
>>>> define that phrase. So even though the above sentence
looks like a circular<br>
>>>> definition, I think it's really an open-ended definition
(e.g., a google search<br>
>>>> for "simple majority definition" turns up both
definitions).<br>
>>>><br>
>>>> I was not there and don't know *exactly* what happened,
so I'll refrain from<br>
>>>> commenting further.<br>
>>><br>
>>> If the bylaws are vague, we should clarify them. We
should not however reinterpret them at each meeting, and should all agree
on a proper interpretation and stick to it, such that ambiguity is removed
going forward. Allowing our bylaws to be vague enough to afford a
re-interpretation at each meeting does nobody any good.<br>
>>><br>
>>> -Fab<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> mpi-forum mailing list<br>
>>> mpi-forum@lists.mpi-forum.org<br>
>>> </font></tt><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum"><tt><font size=2>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum</font></tt></a><tt><font size=2><br>
>>><br>
>> _______________________________________________<br>
>> mpi-forum mailing list<br>
>> mpi-forum@lists.mpi-forum.org<br>
>> </font></tt><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum"><tt><font size=2>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum</font></tt></a><tt><font size=2><br>
><br>
><br>
> _______________________________________________<br>
> mpi-forum mailing list<br>
> mpi-forum@lists.mpi-forum.org<br>
> </font></tt><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum"><tt><font size=2>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum</font></tt></a><tt><font size=2><br>
<br>
<br>
<br>
-- <br>
Jeff Hammond<br>
Argonne Leadership Computing Facility<br>
University of Chicago Computation Institute<br>
jhammond@alcf.anl.gov / (630) 252-5381<br>
</font></tt><a href=http://www.linkedin.com/in/jeffhammond><tt><font size=2>http://www.linkedin.com/in/jeffhammond</font></tt></a><tt><font size=2><br>
</font></tt><a href=https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond><tt><font size=2>https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond</font></tt></a><tt><font size=2><br>
<br>
_______________________________________________<br>
mpi-forum mailing list<br>
mpi-forum@lists.mpi-forum.org<br>
</font></tt><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum"><tt><font size=2>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum</font></tt></a><tt><font size=2><br>
<br>
</font></tt>
<br>