<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>( If transparency / impartiality is an issue, use the last digit of the day's published Dow index closing number. If 0..4, Alice wins the tie; if 5..9, Bob wins. )<br><br>.mpg</div><div><br>On Jul 7, 2014, at 3:19 PM, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
Hi Frank and others,<br>
<br>
It is tough for a CRO to have to select a "random" process
retrospectively. Hence I think we should make it easier by defining
the process up front.<br>
<br>
A "random tie breaker" will typically favour one person over
another, or even if it is a coin flip, then the looser would be
right to feel cheated that they lost to a coin flip. I think it
better to give a tie breaker vote to a person, preferably someone
with respect in the community. Typically this will be the chair of a
committee, and not one of the nominees. It could be allocated to a
board member who has served 1 year out of their 2 year term.<br>
<br>
We could give the tie breaker person a 0.5 vote instead of a 1.5
vote in order to avoid specific accusations.<br>
<br>
On re-thinking, a 0.5 vote works for selecting 1 candidate from many
options, but can still result in a tied vote when selecting many
from many. Ie, there might be 2 candidates, each with 24.5 votes. As
such a tie breaker vote should be a ranked vote. (0.1, 0.2, 0.3,
...)<br>
<br>
We have learned from experience that a revote can result in a second
tie, as well as using up precious time, so I suggest avoiding a
solution which involves a revote.<br>
<br>
So I suggest:<br>
1. A ranked tie breaker vote be allocated to a person, that person
being the CRO, but am happy to consider it being allocated to
someone else.<br>
2. The person with the tie breaker vote doesn't have a vote, except
in the case of a tie.<br>
3. To avoid misfeelings in the community and pressure upon the tie
breaker, the results of the tie breaker's decision should not be
made public, and should not be in a position to be deduced. (This
probably means that we won't publish that there was a tie in the
first place).<br>
<br>
<div class="moz-cite-prefix">On 8/07/2014 2:32 am, Frank Warmerdam
wrote:<br>
</div>
<blockquote cite="mid:CA+YzLBeJM2xqQCX8eNrX8YNEZE7ngyK3z1K=5wHrRD8WxtGC8A@mail.gmail.com" type="cite">
<div dir="ltr">Cameron,
<div><br>
</div>
<div>I'm not clear why the old technique of a random tie breaker
is a problem? </div>
<div><br>
</div>
<div>Best regards,</div>
<div>Frank</div>
<div><br>
</div>
</div>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Mon, Jul 7, 2014 at 2:13 AM, Cameron
Shorter <span dir="ltr"><<a moz-do-not-send="true" href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> OSGeo Board,<br>
I propose the Board Election Procedure be changed to the
following, at:<br>
<a moz-do-not-send="true" href="http://wiki.osgeo.org/wiki/Board_Election_Procedure_2014" target="_blank">http://wiki.osgeo.org/wiki/Board_Election_Procedure_2014</a><br>
<br>
The non-trivial change I've made is to add a tie-breaker
process:<br>
<i>In case of a tied vote for board member positions, the
CRO's vote will count as 1.5 times a normal vote, in
order to resolve the tie break.</i><br>
<br>
+1 for the change, Cameron<br>
<br>
If the board agrees to this change, I'll move the text
across to: <br>
<a moz-do-not-send="true" href="http://wiki.osgeo.org/wiki/Board_Election_Procedure" target="_blank">http://wiki.osgeo.org/wiki/Board_Election_Procedure</a><br>
<br>
Jorge, can you please unlock this page so I can edit it
too.<span class="HOEnZb"><font color="#888888"><br>
<pre cols="72">--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P <a moz-do-not-send="true" href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>, W <a moz-do-not-send="true" href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>, F <a moz-do-not-send="true" href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a></pre>
</font></span></div>
<br>
_______________________________________________<br>
Board mailing list<br>
<a moz-do-not-send="true" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a><br>
<a moz-do-not-send="true" href="http://lists.osgeo.org/mailman/listinfo/board" target="_blank">http://lists.osgeo.org/mailman/listinfo/board</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
---------------------------------------+--------------------------------------<br>
I set the clouds in motion - turn up | Frank Warmerdam, <a moz-do-not-send="true" href="mailto:warmerdam@pobox.com" target="_blank">warmerdam@pobox.com</a><br>
light and sound - activate the windows | <a moz-do-not-send="true" href="http://pobox.com/%7Ewarmerdam" target="_blank">http://pobox.com/~warmerdam</a><br>
and watch the world go round - Rush | Geospatial Software
Developer<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P +61 2 9009 5000, W <a class="moz-txt-link-abbreviated" href="http://www.lisasoft.com">www.lisasoft.com</a>, F +61 2 9009 5099</pre>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Board mailing list</span><br><span><a href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a></span><br><span><a href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a></span></div></blockquote></body></html>