<div dir="ltr">About this subject, I'd like to make some comments at a personal level.<div><br></div><div>- I did not see that the voting was appended to the posted document. I only paid attention to the first page with the results.</div><div>- I got to know that something went wrong when reading further comments on the thread.</div><div>- Yes, it's a really bad look and should have never happened.</div><div>- I made the conscious decision to not look into the document after the fact (just the idea of it gives me cancer)</div><div><br></div><div>Why am I mentioning this?</div><div><br></div><div>Because I don't care who voted for whom and no one should either.</div><div>It is incumbent upon us to make sure that the expected rules of the process are observed and respected and this no matter the circumstances.</div><div><br></div><div><b>If we have the right to vote, we also have the responsibility to protect the voting mechanism and anything revolving around it.</b></div><div>Taking advantage of looking into who voted to whom is akin to breaking the Chatham House Rule.</div><div><br></div><div>For as much as I am concerned, I am elected to help all NPOC, not only those who voted for me. I am not interested in knowing, I am interested in getting things done.</div><div><br></div><div>Obviously I hope that this situation does not happen again (and this should be a ticket to fix with the new chairs) and as far as I am concerned, I am moving page and looking forward to work on Comms.</div><div><br></div><div>Best,</div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div></div><div>Jean F. Queralt</div><div>Founder & CEO - <a href="http://www.TheIOFoundation.org" target="_blank">The IO Foundation</a></div><div><a href="http://TIOF.Click/BookJFQ" target="_blank">Book a meeting</a> (30 minutes)<br></div></div></div></div><br></div><img src="https://app.dragapp.com/V1.18/emailTracking/track-email?uId=amZxdWVyYWx0QHRoZWlvZm91bmRhdGlvbi5vcmcsMTY4NjA3MzM2NTYzNA==&emailTemplateId=&emailFollowupId=" width="0px" height="0px"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 5 Jun 2023 at 22:21, Johan Helsingius via Npoc-discuss <<a href="mailto:npoc-discuss@icann.org">npoc-discuss@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 04/06/2023 23:22, Glenn McKnight via Npoc-discuss wrote:<br>
> I don't know if the election reporting is a normal protocol for NPOC <br>
> or its a simple error to reveal how everyone votes. Regardless we have <br>
> a serious situation that needs to be addressed asap as it will clearly <br>
> be escalated and ignoring it isn't a good option. A reelection seems <br>
> logical but not sure if it would generate any change in the results. <br>
<br>
Definitely not normal - it was an administrative double error.<br>
<br>
Unfortunately a re-election won't rectify the situation. The results of<br>
the election are not dependent on the publishing of who voted for whom,<br>
and the damage in terms of violating confidentiality has already<br>
happened and can't be undone.<br>
<br>
All we can do is ensure it won't happen again.<br>
<br>
Julf<br>
_______________________________________________<br>
Npoc-discuss mailing list<br>
<a href="mailto:Npoc-discuss@icann.org" target="_blank">Npoc-discuss@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/npoc-discuss" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/npoc-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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" 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.</blockquote></div>
<br>
<div><i><font size="2" color="#808080"><b>DISCLAIMER</b></font></i></div><div><i><font size="2" color="#808080">The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.</font></i></div>