[GRASS-PSC] [GRASS GIS Elections 2020] Brief summary and reflections for the next election

[Huidae Cho]

On Thu, Jan 28, 2021 at 12:29 PM Hernán De Angelis <
variablestarlight at gmail.com> wrote:

>
>
> Den tors 28 jan. 2021 18:23Huidae Cho <grass4u at gmail.com> skrev:
>
>>
>>
>> On Thu, Jan 28, 2021 at 12:10 PM Chief Return Officer (CRO) - GRASS GIS
>> election 2020 <variablestarlight at gmail.com> wrote:
>>
>>>
>>> On 2021-01-28 17:44, Michael Barton wrote:
>>>
>>> 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 😉
>>>
>>>
>>>
>>> Michael
>>>
>>> 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.
>>>
>>> https://ballotpedia.org/Ranked-choice_voting_(RCV)
>>>
>>>
>>> Hernán,
>>
>> I'm not familiar with RCV either, but does it mean we only count the
>> first preference, like one voter chooses only one candidate or non-first
>> preferences don't matter at all (then why more than one preference per
>> voter)? I'd like to learn more about RCV for multiple selections.
>>
>
> I have no idea either. Just noted that I got it as a suggestion.
>
> I am actually fairly satisfied with the method we run this time, 'choose
> your 9 member PSC'.
>
> H.
>

Totally agreed. Ranking 9 choices when voting doesn't sound fun to a
candidate like me. ;-)

Huidae


>
>
>>
>>>
>>>
>>> ______________________________
>>>
>>> C. Michael Barton
>>> Director, Center for Social Dynamics & Complexity
>>> Director, Network for Computational Modeling in Social & Ecological
>>> Sciences
>>> Associate Director, School of Complex Adaptive Systems
>>> Professor, School of Human Evolution & Social Change
>>> Arizona State University
>>> Tempe, AZ  85287-2402
>>> USA
>>>
>>> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
>>> fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
>>> www: http://shesc.asu.edu,
>>>
>>> https://complexity.asu.edu,
>>>
>>> http://www.public.asu.edu/~cmbarton
>>>
>>>
>>>
>>> *From: *grass-psc <grass-psc-bounces at lists.osgeo.org>
>>> <grass-psc-bounces at lists.osgeo.org> on behalf of Chief Return Officer
>>> (CRO) - GRASS GIS election 2020 <variablestarlight at gmail.com>
>>> <variablestarlight at gmail.com>
>>> *Date: *Thursday, January 28, 2021 at 7:10 AM
>>> *To: *GRASS-PSC <grass-psc at lists.osgeo.org> <grass-psc at lists.osgeo.org>
>>> *Subject: *Re: [GRASS-PSC] [GRASS GIS Elections 2020] Brief summary and
>>> reflections for the next election
>>>
>>> On 2021-01-28 15:04, Huidae Cho wrote:
>>> > Hernán and all,
>>> >
>>> > First of all, many thanks to Hernán for organizing the election. I
>>> > think it was very smooth.
>>>
>>> Thank you, Huidae.
>>>
>>>
>>> > I believe the most challenging and important task in any election is
>>> > to prepare a tidy voters registry. At the moment, we have multiple
>>> > lists of contributors in different repositories. It would be much
>>> > easier to avoid human errors if we combined them into a single list,
>>> > maybe in the core or web repository. Also, for identifying
>>> > individuals, we can create a unique ID for each contributor based on
>>> > their name (e.g., first initial + middle initial + last name) when
>>> > they first join the community to avoid using email addresses (or even
>>> > github IDs for a potential migration to another platform in the
>>> > future), which can change any time. Last, as for sending an email to
>>> > someone who has been away from the community for a while, we could
>>> > utilize mailing archives to check if they have been active in the
>>> > community in the past couple of years. We can discuss further in the
>>> > first meeting.
>>> >
>>> +1 for unique IDs, wheter related to GitHub or not, they are very useful.
>>> _______________________________________________
>>> grass-psc mailing list
>>> grass-psc at lists.osgeo.org
>>>
>>> https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!KXrZWIFoWdrJ9ppoLTtFVzl4zj_ToU6_OuiH5eLhFvwl0X2zFFxCkpCM0RgKoEYZN3_bikw$
>>> <https://urldefense.com/v3/__https:/lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!KXrZWIFoWdrJ9ppoLTtFVzl4zj_ToU6_OuiH5eLhFvwl0X2zFFxCkpCM0RgKoEYZN3_bikw$>
>>>
>>> _______________________________________________
>>> grass-psc mailing list
>>> grass-psc at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-psc
>>>
>>
>>
>> --
>> Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
>> GRASS GIS Developer
>> https://idea.isnew.info
>>
> _______________________________________________
> grass-psc mailing list
> grass-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>


-- 
Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
GRASS GIS Developer
https://idea.isnew.info
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-psc/attachments/20210128/aa6fb5aa/attachment.html>