<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 2021-01-28 17:44, Michael Barton
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:BYAPR06MB5831095D00B3C5583A4F52338ABA9@BYAPR06MB5831.namprd06.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:"Lucida Grande";
panose-1:2 11 6 0 4 5 2 2 2 4;}@font-face
{font-family:"Lucida Sans";
panose-1:2 11 6 2 3 5 4 2 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoNormal">I agree with Huidae. Pretty much
simultaneously with the GRASS PSC elections, CoMSES.Net held
executive board election. We also ran into glitches with this
remote voting and eventually had to rerun the election. So the
GRASS one went very well. Thanks. Having a way to work out a
list of eligible voters is important but I’m sure that GRASS
expertise can solve it. Perhaps we can then propose this to US
states who are wrestling with the same question and often
proposing really bad solutions
<span style="font-family:"Apple Color Emoji"">😉</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Michael</p>
</div>
</blockquote>
<p>I got a suggestion, by Rich Shepard, about "ranked choice voting
(RCV?)". I have no experience with it but possibly something the
PSC may want to have a look at.</p>
<p><a class="moz-txt-link-freetext" href="https://ballotpedia.org/Ranked-choice_voting_(RCV)">https://ballotpedia.org/Ranked-choice_voting_(RCV)</a></p>
<p><br>
</p>
<p>/H.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:BYAPR06MB5831095D00B3C5583A4F52338ABA9@BYAPR06MB5831.namprd06.prod.outlook.com">
<div class="WordSection1">
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:Helvetica;color:black">______________________________</span><span
style="font-size:10.0pt;font-family:"Lucida
Grande",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Lucida
Sans",sans-serif;color:#5E5E5E">C. Michael Barton <br>
Director, Center for Social Dynamics & Complexity<br>
Director, Network for Computational Modeling in
Social & Ecological Sciences<br>
Associate Director, School of Complex Adaptive Systems<br>
Professor, School of Human Evolution & Social Change<br>
Arizona State University<br>
Tempe, AZ 85287-2402<br>
USA<br>
<br>
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)<br>
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)<br>
www: <a href="http://shesc.asu.edu"
moz-do-not-send="true"><span style="color:#0563C1">http://shesc.asu.edu</span></a>, <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Lucida
Sans",sans-serif;color:#5E5E5E"><a
href="https://complexity.asu.edu" moz-do-not-send="true"><span
style="color:#0563C1">https://complexity.asu.edu</span></a>, <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Lucida
Sans",sans-serif;color:#5E5E5E"><a
href="http://www.public.asu.edu/~cmbarton"
moz-do-not-send="true"><span style="color:#0563C1">http://www.public.asu.edu/~cmbarton</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span
style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">grass-psc
<a class="moz-txt-link-rfc2396E" href="mailto:grass-psc-bounces@lists.osgeo.org"><grass-psc-bounces@lists.osgeo.org></a> on behalf of
Chief Return Officer (CRO) - GRASS GIS election 2020
<a class="moz-txt-link-rfc2396E" href="mailto:variablestarlight@gmail.com"><variablestarlight@gmail.com></a><br>
<b>Date: </b>Thursday, January 28, 2021 at 7:10 AM<br>
<b>To: </b>GRASS-PSC <a class="moz-txt-link-rfc2396E" href="mailto:grass-psc@lists.osgeo.org"><grass-psc@lists.osgeo.org></a><br>
<b>Subject: </b>Re: [GRASS-PSC] [GRASS GIS Elections
2020] Brief summary and reflections for the next election<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">On 2021-01-28 15:04, Huidae Cho wrote:<br>
> Hernán and all,<br>
><br>
> First of all, many thanks to Hernán for organizing the
election. I <br>
> think it was very smooth.<br>
<br>
Thank you, Huidae.<br>
<br>
<br>
> I believe the most challenging and important task in
any election is <br>
> to prepare a tidy voters registry. At the moment, we
have multiple <br>
> lists of contributors in different repositories. It
would be much <br>
> easier to avoid human errors if we combined them into a
single list, <br>
> maybe in the core or web repository. Also, for
identifying <br>
> individuals, we can create a unique ID for each
contributor based on <br>
> their name (e.g., first initial + middle initial + last
name) when <br>
> they first join the community to avoid using email
addresses (or even <br>
> github IDs for a potential migration to another
platform in the <br>
> future), which can change any time. Last, as for
sending an email to <br>
> someone who has been away from the community for a
while, we could <br>
> utilize mailing archives to check if they have been
active in the <br>
> community in the past couple of years. We can discuss
further in the <br>
> first meeting.<br>
><br>
+1 for unique IDs, wheter related to GitHub or not, they are
very useful.<br>
_______________________________________________<br>
grass-psc mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:grass-psc@lists.osgeo.org">grass-psc@lists.osgeo.org</a><br>
<a
href="https://urldefense.com/v3/__https:/lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!KXrZWIFoWdrJ9ppoLTtFVzl4zj_ToU6_OuiH5eLhFvwl0X2zFFxCkpCM0RgKoEYZN3_bikw$"
moz-do-not-send="true">https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!KXrZWIFoWdrJ9ppoLTtFVzl4zj_ToU6_OuiH5eLhFvwl0X2zFFxCkpCM0RgKoEYZN3_bikw$</a>
<o:p></o:p></p>
</div>
</div>
</blockquote>
</body>
</html>