It’s not a giant surprise. Check out the ICANN pages, and I doubt there is any mention, anywhere, of SOIs outside of the Nominating Committee (people who want to run for offices). This is a relatively new thing and people are surprised. It’s also a trivial thing, so if we were able to communicate it well, most people would just do it. This is the blocker, apparently: if we were able to communicate it well From: UA-EAI <ua-eai-bounces@icann.org> On Behalf Of Harish Chowdhary via UA-EAI Sent: Thursday, May 16, 2024 8:30 AM To: Mark W. Datysgeld <mark@governanceprimer.com> Cc: ua-eaI@ICANN.ORG Subject: [EXTERNAL] Re: [UA-EAI] ACTION REQUIRED by May 15, 2024 For Continuation of Your UASG Membership Yes Mark, Absolutely. Harish On Thu, 16 May, 2024, 20:38 Mark W. Datysgeld via UA-EAI, <ua-eai@icann.org<mailto:ua-eai@icann.org>> wrote: It's not even in question whether we need this, yes. People can argue about the implementation, but the core action itself should not even be a question to anybody who is mildly engaged in the project. --- Mark W. Datysgeld from Governance Primer ________________________________ From: Arnt Gulbrandsen via UA-EAI <ua-eai@icann.org<mailto:ua-eai@icann.org>> Sent: Thursday, May 16, 2024 10:20 To: Cc: ua-eai@icann.org<mailto:ua-eai@icann.org> Subject: Re: [UA-EAI] ACTION REQUIRED by May 15, 2024 For Continuation of Your UASG Membership Jim, Anil, others: Speaking as a UA enthusiast only: with postings like https://domainincite.com/29648-icann-79-anonymous-trolls-and-undercover-lawy... and comments like some I heard at the public meeting in Hamburg last year, the problem is now urgent. The trolls must go, now, one way or another. Slow explanation, advocacy and persuasion won’t do, there’s urgency now. Although I work at ICANN, I haven’t attended any meetings about any of this and am happy to leave policy issues to my colleagues. I work with tech, not policy, I know nothing and do not speak for ICANN. But as an UA enthusiast, I know the date of the Public Forum in June, and I think we need a good story to tell in case there are ugly questions. The story needs to use a lot of past tense. Sorry about the 50%. Arnt From: UA-EAI <ua-eai-bounces@icann.org<mailto:ua-eai-bounces@icann.org>> on behalf of Jim DeLaHunt via UA-EAI <ua-eai@icann.org<mailto:ua-eai@icann.org>> Reply-To: Jim DeLaHunt <list+uasg@jdlh.com<mailto:list%2Buasg@jdlh.com>> Date: Wednesday, 15 May 2024 at 21:18 To: anil Jain <asdj1990@gmail.com<mailto:asdj1990@gmail.com>> Cc: "ua-eai@icann.org<mailto:ua-eai@icann.org>" <ua-eai@icann.org<mailto:ua-eai@icann.org>> Subject: Re: [UA-EAI] ACTION REQUIRED by May 15, 2024 For Continuation of Your UASG Membership Anil: Respectfully, if less than 50% of existing UASG members have submitted their SOI, maybe it is a sign that the process of introducing the SOIs is lacking. In that case, another 15 days might not fix the problem. It might be better to go back and do the parts of the process which should have preceded the SOI mandate: 1. Explain the situation and the problems which require action. (For instance, if ICANN is demanding certain actions, say that. If trolls on UA-Discuss are a problem, say that.) 2. Propose the SOIs as a solution to the problem, and advocate for why they will be effective. 3. Listen to responses, especially critiques of the proposal, and improve the proposal based on responses. 4. Build a consensus among UASG members that the SOI mandate is the best solution, or at least that it is necessary if not "best". All of this should take place where the UASG members are accessible. That is, on the UA-Discuss list, and in working group meetings. (Some discussion has happened at ICANN in-person meetings, but only a few UASG members participate in those, so they do not provide enough coverage.) It seems to me that you as UASG Chair, along with the vice chairs and other administrators, are ideally placed to take leadership in correcting UASG's course in the process. Best regards, —Jim DeLaHunt On 2024-05-15 07:39, anil Jain via UA-EAI wrote: Seda, I request to extend SOI by another 15 days if less than 50% members have submitted their SOI. Thanks Anil Sent from my iPhone On 21 Mar 2024, at 3:46 PM, Seda Akbulut via UA-EAI <ua-eai@icann.org><mailto:ua-eai@icann.org> wrote: Dear UASG members, We hope this email finds you well. As part of ICANN’s ongoing efforts to enhance transparency and accountability within the multistakeholder ecosystem, we are reaching out to verify your continued interest in receiving information from the UASG. To retain access to UASG mailing lists, you must submit your Statement of Interest (SOI) by 15 May, 2024. This practice is consistent with other groups of the ICANN community (e.g., see SOIs for GNSO<https://community.icann.org/display/gnsosoi/New+SOIs>, or click “New SOIs” on the left menu here<https://community.icann.org/display/gnsosoi>.) The SOI form is available at https://app.smartsheet.com/b/form/725e244f1369423182ea1bf932df6962 [app.smartsheet.com]<https://urldefense.com/v3/__https:/app.smartsheet.com/b/form/725e244f1369423...>. If you are unable to complete your SOI by 15 May 2024 deadline, you will be unsubscribed from all UASG email lists. However, you can resubscribe at a later time by submitting your SOI. ICANN will publicly publish the received SOIs at https://uasg.tech/member-area/ [uasg.tech]<https://urldefense.com/v3/__https:/uasg.tech/member-area/__;!!PtGJab4!5X8BOa...>. We sincerely appreciate your cooperation and understanding in this matter. Your participation is instrumental in building a more transparent and robust community. If you have any questions or concerns, please don't hesitate to reach out to us at info@uasg.tech<mailto:info@uasg.tech>. Thank you for your continued support, and we look forward to your valuable contributions. Best regards, UASG Leadership Team _______________________________________________ UA-EAI mailing list UA-EAI@icann.org<mailto:UA-EAI@icann.org> https://mm.icann.org/mailman/listinfo/ua-eai _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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. _______________________________________________ UA-EAI mailing list UA-EAI@icann.org<mailto:UA-EAI@icann.org> https://mm.icann.org/mailman/listinfo/ua-eai _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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. -- --Jim DeLaHunt, jdlh@jdlh.com<mailto:jdlh@jdlh.com> http://blog.jdlh.com/ [blog.jdlh.com]<https://urldefense.com/v3/__http:/blog.jdlh.com/__;!!PtGJab4!5X8BOa2ikoEUb2V...> (http://jdlh.com/ [jdlh.com]<https://urldefense.com/v3/__http:/jdlh.com/__;!!PtGJab4!5X8BOa2ikoEUb2VkuTUW...>) multilingual websites consultant, Vancouver, Canada _______________________________________________ UA-EAI mailing list UA-EAI@icann.org<mailto:UA-EAI@icann.org> https://mm.icann.org/mailman/listinfo/ua-eai _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.