<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Thank you Chaals , Jim, MO and everyone .</div>
<div> </div>
<div>Jim +1</div>
<div> </div>
<div>change when needed. dont make us learn new proceses which are used once in two years. I ok for what has worked for us till now. </div>
<div> </div>
<div>more importantly, people in leadership should tell what they have done to execute UA implementation in the there own organisation-helped-moviated others. When they nominate they must mention this. We need people who are UA practitioners like people from Microsoft, Gmail, XgenPlus, Apple, Postfix and others. </div>
<div> </div>
<div>Best</div>
<div> </div>
<div>Mike</div>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Sent:</b> Monday, February 08, 2021 at 11:47 AM<br/>
<b>From:</b> "Charles 'chaals' (McCathie) Nevile" <chaals@yandex.ru><br/>
<b>To:</b> ua-discuss@icann.org<br/>
<b>Subject:</b> Re: [UA-discuss] UASG 2021 Elections - Process and Timeline</div>
<div name="quoted-content">Thank you Mo, Jim.<br/>
<br/>
I have a preference for Meek STV rather than Scottish STV, but I support<br/>
all the suggestions Jim made - in particular his "curious option" to<br/>
include allowing a vote for "only 2 vice-chairs".<br/>
<br/>
cheers<br/>
<br/>
Chaals<br/>
<br/>
On Sun, 07 Feb 2021 19:41:19 +1100, Jim DeLaHunt <list+uasg@jdlh.com><br/>
wrote:<br/>
<br/>
><br/>
> Mo:<br/>
> Thank you for sending this out. It's good that we have a clearly<br/>
> stated election process, and that the process be clear before we<br/>
> add the specific candidates and opinions about which candidates to<br/>
> choose.<br/>
><br/>
><br/>
> I have some suggestions about the elections process as stated in<br/>
> the document you sent, 2021 UASG Election Process and Timeline<br/>
> 2021-02-04.pdf , section "2021 UASG Election Process".<br/>
> 1. The process does not state that how many Chairs and how many<br/>
> Vice-Chairs are to be elected. Yes, the "UASG Structure" above<br/>
> says that these numbers are "1" and "2-3" respectively. Still,<br/>
> for clarity it seems good to state what the purpose of the<br/>
> process is. I suggest adding an item before old #1, reading<br/>
> something like, "The election will elect one Chair and [2-3<br/>
> Vice-Chairs]".<br/>
><br/>
> 2. The process does not state what kind of votes are cast and<br/>
> what method is used to count votes. I support using the same<br/>
> methods as last year, as described in<br/>
> <<a href="https://uasg.tech/wp-content/uploads/2019/02/Call-for-Nominations.pdf" target="_blank">https://uasg.tech/wp-content/uploads/2019/02/Call-for-Nominations.pdf</a>>,<br/>
> namely preferential ballots, counted with Instant Runoff Voting<br/>
> for the single Chair, and Scottish STV for the 2-3 Vice-Chairs.<br/>
> These methods are among the best ways to elect single and<br/>
> multiple winners for a group like UASG. I suggest adding between<br/>
> old #5 and #6, something like: "For the single Chair position,<br/>
> voters will cast preferential ballots ranking their choices, and<br/>
> the counting method will be Instant Runoff Voting<br/>
> <<a href="https://www.opavote.com/methods/instant-runoff-voting" target="_blank">https://www.opavote.com/methods/instant-runoff-voting</a>>",<br/>
> and "For the 2-3 Vice-Chair positions, voters will cast<br/>
> preferential ballots ranking their choices among all candidates,<br/>
> and the counting method used will be Scottish STV<br/>
> <<a href="https://www.opavote.com/methods/single-transferable-vote#scottish-stv" target="_blank">https://www.opavote.com/methods/single-transferable-vote#scottish-stv</a>>."<br/>
><br/>
> 3. The process does not define how we will decide whether to<br/>
> elect 2 or 3 Vice-Chairs. There are several rules which we could<br/>
> use. We should state what rule we will follow. I suggest adding<br/>
> it as part of the entry for the Vice-Chair method above. Some<br/>
> rules we could use:<br/>
><br/>
> 1. If there are 1, 2, or 3 candidates for Vice-Chair, they will<br/>
> all be elected by acclamation and they will not be voted on.<br/>
> 2. If there are more than 3 candidates for Vice-Chair, they<br/>
> shall be voted on and 3 shall be elected.<br/>
><br/>
> 3. If there are more than 3 candidates for Vice-Chair, they<br/>
> shall be voted on, and an option "Only 2 Vice-Chairs" shall be<br/>
> added to the ballot. Voters may rank "Only 2 Vice-Chairs" the<br/>
> same way as any other candidate. The top two candidates shall<br/>
> be elected. If the option "Only 2 Vice-Chairs" is among the<br/>
> top three finishers, there shall only be two Vice-Chairs,<br/>
> otherwise, there shall be three Vice-Chairs, and the<br/>
> third-place candidate shall also be elected. [Note: this<br/>
> curious option means that voters who think some candidates are<br/>
> unsatisfactory, and a Vice-Chair seat should be left empty<br/>
> rather than be filled by those candidates, may rank "Only 2<br/>
> Vice-Chairs" above the unsatisfactory candidates, and the<br/>
> counting will respect their wish to the extent possible.]<br/>
><br/>
> 4. I have no problem with the diversity intent of rule # 4, but I<br/>
> think it is a mistake to enforce this at the nomination stage.<br/>
> Suppose there are two candidates in one organization, "M. Good"<br/>
> and "M. Bad". Rule #4 says that M. Bad can prevent voters from<br/>
> supporting M. Good by submitting their own self-nomination<br/>
> first! Instead I suggest that we implement the rule at the<br/>
> vote-counting stage of the Vice-Chair election. As soon as a<br/>
> candidate is elected during the counting process, we disqualify<br/>
> all other candidates from the same organization or company, and<br/>
> continue (or restart) the counting process. This lets voters,<br/>
> not nominators, choose whether to support "M. Good" or "M. Bad".<br/>
> There is no need for this diversity rule in the Chair election,<br/>
> because only one Chair is elected. I suggest a rule about<br/>
> eliminating Vice-Chair candidates during vote-counting be added,<br/>
> and old rule #4 be deleted.<br/>
><br/>
> 5. Rule #1 does not clearly say that sock-puppets are forbidden.<br/>
> It should. By saying "the subscribers… are… the electorate", it<br/>
> implies that email addresses, not natural people, are the<br/>
> electorate. I suggest rewording it to say, "The electorate<br/>
> consists of the natural persons subscribed to the UA-Discuss<br/>
> mailing list on [the date of record for the electorate]. Each<br/>
> person may cast at most one ballot. Sock puppets are forbidden."<br/>
> 6. Rule #8 addresses sock puppets as well. Move it to<br/>
> right after<br/>
> rule #1.<br/>
><br/>
> 7. Rule #1 (and the Election Timeline below) are not clear about<br/>
> the time at which the UASG-Discuss subscriber list creates the<br/>
> electorate. Rule #1 says "the date of announcing the election".<br/>
> But the Election Timeline puts the label "Announcing the<br/>
> starting of the elections" onto a 10-day period. I suggest<br/>
> adding a separate entry to the timeline, labelled something like<br/>
> "Date and time of record for the electorate". Make it a specific<br/>
> UTC time; dates (interpreted with time zones) can span 48 hours.<br/>
> 8. Rule #6 says the election process will be managed by a<br/>
> specialised elections service provider. Who? Why not just say<br/>
> Opavote? And it says, "the final results will be audited and<br/>
> confirmed." How? By whom?<br/>
><br/>
> 9. I suggest adding a sentence to Rule #6. "A detailed report of<br/>
> the vote counting steps, along with anonymised raw ballot data,<br/>
> shall be published, for transparency and for community<br/>
> auditing." Opavote provides reports and ballot data as a normal<br/>
> part of its service.<br/>
><br/>
> Also, a few comments about the Election Timeline:<br/>
><br/>
><br/>
> 1. Dates without times or time zones are ambiguous in a global<br/>
> community. I suggest saying "all dates are UTC", or adding UTC<br/>
> times to each date.<br/>
><br/>
> 2. The voting period should have times and time zones added;<br/>
> dates alone are too ambiguous. If the election starts at 00:00 5<br/>
> March UTC and ends at 23:59 15 March UTC, that is 11 days, not<br/>
> 10. If it starts on 5 March anywhere in the world, and ends on<br/>
> 15 March anywhere in the world, that is 12 days (00:00 5 March<br/>
> UTC-13:00 to 23:59 15 March UTC+12:00). Only if the election<br/>
> period is defined as a specific time and time zone can it be<br/>
> unambiguously 10 days. The voting period in days should match<br/>
> the duration between start and end times.<br/>
><br/>
> 3. Suggest adding a timeline entry, "Date and time of record for<br/>
> the electorate". I would recommend it being the same time as the<br/>
> self-nomination period begins, or when the list of candidates is<br/>
> announced. There's a risk of a candidate packing the UA-Discuss<br/>
> with their supporters. The choice of date and time of record can<br/>
> encourage or discourage this.<br/>
><br/>
> I hope this is helpful. Can you tell I am interested in electoral<br/>
> process?<br/>
><br/>
> Best regards,<br/>
><br/>
> —Jim DeLaHunt, Vancouver, Canada<br/>
><br/>
> On 2021-02-04 12:37, Mohamed Elbashir<br/>
> wrote:<br/>
><br/>
><br/>
>><br/>
>> Dear UA<br/>
>> Community,<br/>
>><br/>
>><br/>
>> Find<br/>
>> attached the UASG 2021 elections process and timeline,<br/>
>> it will be published on the UASG.tech website.<br/>
>><br/>
>><br/>
>><br/>
>> Thank<br/>
>> you!<br/>
>><br/>
>><br/>
>><br/>
>> Best<br/>
>> Regards,<br/>
>><br/>
>><br/>
>> Mohamed<br/>
>> (Mo) Elbashir<br/>
>><br/>
>><br/>
>> Universal<br/>
>> Acceptance (UA) Program Manager<br/>
>><br/>
>><br/>
>> The<br/>
>> Internet Corporation for Assigned Names and Numbers<br/>
>> (ICANN)<br/>
>> One World, One<br/>
>> Internet<br/>
>><br/>
>><br/>
>> [id:image001.png@01D356F4.3F3911B0]<br/>
>><br/>
>><br/>
>><br/>
>> _______________________________________________<br/>
>> UA-discuss mailing list<br/>
>> UA-discuss@icann.org<br/>
>> <a href="https://mm.icann.org/mailman/listinfo/ua-discuss" target="_blank">https://mm.icann.org/mailman/listinfo/ua-discuss</a><br/>
>> _______________________________________________<br/>
>> By submitting your personal data, you consent to the processing of your<br/>
>> personal data for purposes of subscribing to this >>mailing list<br/>
>> accordance with the ICANN Privacy Policy<br/>
>> (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service<br/>
>> >>(<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link<br/>
>> above to change your membership status or configuration, >>including<br/>
>> unsubscribing, setting digest-style delivery or disabling delivery<br/>
>> altogether (e.g., for a vacation), and so on.<br/>
>><br/>
>><br/>
><br/>
> --. --Jim DeLaHunt, jdlh@jdlh.com <a href="http://blog.jdlh.com/" target="_blank">http://blog.jdlh.com/</a><br/>
> (<a href="http://jdlh.com/" target="_blank">http://jdlh.com/</a>)<br/>
> multilingual websites consultant<br/>
><br/>
> 2201-1000 Beach Ave, Vancouver BC V6E 4M2, Canada<br/>
> Canada mobile +1-604-376-8953<br/>
><br/>
><br/>
<br/>
<br/>
<br/>
--<br/>
Using Opera's mail client: <a href="http://www.opera.com/mail/" target="_blank">http://www.opera.com/mail/</a><br/>
_______________________________________________<br/>
UA-discuss mailing list<br/>
UA-discuss@icann.org<br/>
<a href="https://mm.icann.org/mailman/listinfo/ua-discuss" target="_blank">https://mm.icann.org/mailman/listinfo/ua-discuss</a><br/>
_______________________________________________<br/>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div>
</div>
</div>
</div></div></body></html>