<div dir="ltr">Hello, <div><br></div><div>Apologies for stepping in late in this discussion but I would perhaps rephrase the following sentence: <span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:14.6667px"><i>our members thought ICANN should genuinely explore reducing sessions at each meeting and a qualitative evaluation of the benefits of face-to-face meetings in general so that we fully understand what we are potentially going to lose.
</i>Maybe we can frame it as a last resource kinda of exercise since our groups were already affected a couple of years ago with recommendations from staff to take less meetings during the F2F and prioritizing online interaction. The reason why im bringing this story into the conversation is that im concerned that we come to a point where community funding will only be faciliated to groups w/ a x number of meetings or if we get our space in meetings shortened even further. In the last 3-4 years we have had already faced limitations in what sorts of rooms and facilities can be offered to us and it would be important to think about that before sending the msg <a class="gmail_plusreply" id="plusReplyChip-0" href="mailto:mesumbeslin@gmail.com" tabindex="-1">@Tomslin Samme-Nlar</a> crafted.
<i>
best, </i></span></div><div><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:14.6667px"><i>B
</i>
</span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 24, 2024 at 4:58 PM Johan Helsingius via NCSG-PC <<a href="mailto:ncsg-pc@lists.ncsg.is">ncsg-pc@lists.ncsg.is</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">Excellent! Thanks, Tomslin!!<br>
<br>
Julf<br>
<br>
<br>
On 24/07/2024 15:54, Tomslin Samme-Nlar wrote:<br>
> Hi PC,<br>
> <br>
> This is the response I have put together based on the conversation we <br>
> had last week and comments of the document. I wil be sending this to Greg:<br>
> <br>
> Foundational questions:<br>
> <br>
> <br>
> 1.<br>
> <br>
> If you or your group could change one thing about how we meet that<br>
> will facilitate efficiency in how we deliver ICANN’s mission while<br>
> remaining sustainable into the future, what would that be? -<br>
> <br>
> *NCSG Response:* One thing we could try to develop a bit more and think <br>
> thoroughly is to focus resources on groups/individuals within ICANN that <br>
> actually contribute substantially. I'm aware that creating criteria and <br>
> metrics for what "substantial participation" may mean, but the idea here <br>
> would be pushing the community towards a proper stimuli environment, <br>
> rewarding work effectively done and discouraging people from resting <br>
> passively on past laurels (and this should apply not only to <br>
> individuals, but to community bodies as a whole.)<br>
> <br>
> <br>
> <br>
> Other NCSG Comments:<br>
> <br>
> <br>
> We think that reviewing the ICANN Meeting Strategy <br>
> (<a href="https://meetings.icann.org/en/future-meeting-strategy" rel="noreferrer" target="_blank">https://meetings.icann.org/en/future-meeting-strategy</a> <br>
> <<a href="https://meetings.icann.org/en/future-meeting-strategy" rel="noreferrer" target="_blank">https://meetings.icann.org/en/future-meeting-strategy</a>>) after ten years <br>
> (considering how many important things happened in this period) is a <br>
> good idea, even if we end up concluding that we should maintain the <br>
> status quo.<br>
> <br>
> <br>
> In addition, our members thought ICANN should genuinely explore reducing <br>
> sessions at each meeting and a qualitative evaluation of the benefits of <br>
> face-to-face meetings in general so that we fully understand what we are <br>
> potentially going to lose.<br>
> <br>
> <br>
> At the same time, we think session/travel reduction should not be done <br>
> in a blanket way across the board, since all community groups do not <br>
> have access to equal level of funding outside ICANN. However, our <br>
> members think the timing of the changes is poor, considering the <br>
> upcoming new gTLD round and WSIS concerns. The last time we went into a <br>
> round of new gTLDs, it was a London meeting where 6,000 people. It was <br>
> apparently the biggest meeting ICANN had ever, ever hosted <br>
> because there was massive interest, concern, and questions about <br>
> the new gTLD program. If ICANN cut’s back now, we will lose the very <br>
> thing that we are trying to do, which is to get many more people <br>
> involved in and interested in new gTLDs. Newcomers through the <br>
> applicant support program, through the outreach and marketing are <br>
> going to come in and they will have a million questions about ICANN. <br>
> So ICANN needs those education and outreach sessions and we need them <br>
> sometimes face to face so people can actually ask the dumb question in <br>
> the hallway.<br>
> <br>
> <br>
> In addition, NCSG members would like to know what is going on <br>
> financially with ICANN.<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> On Thu, 11 Jul 2024 at 08:59, Tomslin Samme-Nlar <<a href="mailto:mesumbeslin@gmail.com" target="_blank">mesumbeslin@gmail.com</a> <br>
> <mailto:<a href="mailto:mesumbeslin@gmail.com" target="_blank">mesumbeslin@gmail.com</a>>> wrote:<br>
> <br>
> Hi team,<br>
> <br>
> In our SOAC leadership meeting with Sally in Kigali, she mentioned 2<br>
> areas where the community needs to have a dialogue on; (1) "How We<br>
> Meet" and (2) "How We Work". Below and attached is a discussion<br>
> paper from ICANN's Policy & Advice Development staff team to<br>
> facilitate the discussion on dialogue #1 "How We Meet.<br>
> <br>
> Things will move fast since we have to send our feedback (if any) to<br>
> <a href="mailto:gnso-chairs@icann.org" target="_blank">gnso-chairs@icann.org</a> <mailto:<a href="mailto:gnso-chairs@icann.org" target="_blank">gnso-chairs@icann.org</a>> by 24 July<br>
> 2024. As a result, I have added this topic as an agenda item to our<br>
> monthly policy meeting which is on Monday 15 July at 11:30 UTC (See<br>
> Andrea's email/reminder for joining details and full agenda). Come<br>
> with some ideas please. I have also created this Google Doc<br>
> <<a href="https://docs.google.com/document/d/1rQ3_P-xlb48qcy4iY4prOis4Y4O1O2a_geBfrYMuQ4Y/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1rQ3_P-xlb48qcy4iY4prOis4Y4O1O2a_geBfrYMuQ4Y/edit?usp=sharing</a>> to solicit feedback from everyone, even if you can't make the meeting.<br>
> <br>
> In the paper, you will notice a number of suggestions such as:<br>
> <br>
> 1. Evaluate the full cycle of in-person and hybrid community<br>
> meetings, including standalone SOAC Leadership and Strategic<br>
> Planning meetings, targeted group meetings (such as the<br>
> Contracted Parties Summit, the At Large Summit, and the<br>
> High-Level Governmental Meeting) and similar, cost-intensive,<br>
> travel-dependent Meetings<br>
> 2. Review the planning by ICANN Org and the community for all<br>
> in-person/hybrid meetings (including ICANN Public Meetings) by<br>
> adopting an annualized, regular approach of planning for a full<br>
> meeting cycle (either by a calendar year or a fiscal year)<br>
> 3. Review of the current allocation of Funded Travelers to each<br>
> ICANN Public Meeting<br>
> 4. Reduce the number of sessions at ICANN Public Meetings, which<br>
> could result in a reduction in the cost of travel (i.e.,<br>
> accommodation) and venue-related costs (e.g., room and equipment<br>
> rentals, contractors)<br>
> 5. Reduce or eliminate informational and training sessions at ICANN<br>
> Public Meetings<br>
> 6. Reduce or eliminate ICANN-hosted or ICANN-sponsored social and<br>
> outreach events at, or associated with, an ICANN Public Meeting<br>
> 7. Move at least one (1) upcoming ICANN Public Meeting to a Virtual<br>
> Meeting<br>
> 8. Review the current state of ICANN Public Meetings, with a view<br>
> toward updating the ten-year-old ICANN Meetings Strategy (dating<br>
> from 2014) to match current and expected future needs and budget<br>
> constraints<br>
> <br>
> Talk to you all on Monday.<br>
> <br>
> Warmly,<br>
> Tomslin<br>
> <br>
> <br>
> <br>
> <br>
> *From:* Mary Wong via soac-chairs <<a href="mailto:soac-chairs@icann.org" target="_blank">soac-chairs@icann.org</a><br>
> <mailto:<a href="mailto:soac-chairs@icann.org" target="_blank">soac-chairs@icann.org</a>>><br>
> *Sent:* Sunday, July 7, 2024 11:58 PM<br>
> *To:* <a href="mailto:soac-chairs@icann.org" target="_blank">soac-chairs@icann.org</a> <mailto:<a href="mailto:soac-chairs@icann.org" target="_blank">soac-chairs@icann.org</a>><br>
> *Cc:* <a href="mailto:team-leaders@icann.org" target="_blank">team-leaders@icann.org</a> <mailto:<a href="mailto:team-leaders@icann.org" target="_blank">team-leaders@icann.org</a>><br>
> *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community<br>
> Dialogue on "How We Meet": Initial Ideas & Meeting Request____<br>
> <br>
> __ __<br>
> <br>
> *CAUTION*: This email originated from outside of the organization.<br>
> Do not click links or open attachments unless you can confirm the<br>
> sender and know the content is safe.____<br>
> <br>
> __ __<br>
> <br>
> Dear SOAC leaders,____<br>
> <br>
> __ __<br>
> <br>
> An action item from your informal meeting with Sally in Kigali was<br>
> for the Policy team to facilitate a dialogue with you about “How We<br>
> Meet”, viz., how our in-person and hybrid meetings can be optimized<br>
> to ensure that resources (including financial, staff and community<br>
> time) continue to be allocated appropriately to ensure the community<br>
> can do its work effectively and efficiently, while staying within<br>
> budgetary constraints. As a starting point for this dialogue, we<br>
> have drafted the attached discussion paper with some initial ideas<br>
> for your community’s consideration and to invite your suggestions<br>
> for further discussion. ____<br>
> <br>
> __ __<br>
> <br>
> To capitalize on the momentum of recent conversations and to<br>
> facilitate a constructive and substantive dialogue, we’d like to<br>
> suggest the following cadence of meetings, structured around a few<br>
> foundational questions: ____<br>
> <br>
> * Late/end-July: first call with SOAC Chairs and Vice-Chairs to<br>
> share feedback on agreed strategic questions ____<br>
> * Mid/late August (following collation of ideas and input): second<br>
> call to discuss and agree on concrete ideas for implementation<br>
> or further exploration____<br>
> * End-August/early September (if agreed is needed): third call to<br>
> review agreed way forward, including any next steps for<br>
> additional (longer term) ideas to be discussed further ____<br>
> <br>
> __ __<br>
> <br>
> The sort of strategic, foundational questions we were thinking might<br>
> be helpful for focusing the dialogue include:____<br>
> <br>
> o If you or your group could change one thing about how we<br>
> meet that will facilitate efficiency in how we deliver<br>
> ICANN’s mission while remaining sustainable into the future,<br>
> what would that be? ____<br>
> o What other key changes do we need to make to continue to<br>
> ensure we can meet these goals?____<br>
> <br>
> __ __<br>
> <br>
> Thank you for your support and willingness to collaborate with us in<br>
> seeking to improve and optimize how we meet. Assuming you are<br>
> comfortable with the proposed approach, I’ll make sure to come back<br>
> to you with some suggested dates for the calls. Please let me know<br>
> if your group have any questions or would like any additional<br>
> information that can assist with your internal discussions about<br>
> this topic. Thank you!____<br>
> <br>
> __ __<br>
> <br>
> Cheers____<br>
> <br>
> Mary ____<br>
> <br>
> __ __<br>
> <br>
> __ __<br>
> <br>
> __ __<br>
> <br>
> _______________________________________________<br>
> Gnso-chairs mailing list -- <a href="mailto:gnso-chairs@icann.org" target="_blank">gnso-chairs@icann.org</a><br>
> <mailto:<a href="mailto:gnso-chairs@icann.org" target="_blank">gnso-chairs@icann.org</a>><br>
> To unsubscribe send an email to <a href="mailto:gnso-chairs-leave@icann.org" target="_blank">gnso-chairs-leave@icann.org</a><br>
> <mailto:<a href="mailto:gnso-chairs-leave@icann.org" target="_blank">gnso-chairs-leave@icann.org</a>><br>
> _______________________________________________<br>
> By submitting your personal data, you consent to the processing of<br>
> your 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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a><br>
> <<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>>) and the website Terms of<br>
> Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a><br>
> <<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<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>
> NCSG-PC mailing list<br>
> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
> <a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b><i>Bruna Martins dos Santos <br></i></b><div dir="ltr" style="color:rgb(34,34,34)"><br></div><div style="color:rgb(34,34,34)">Global Campaigns Manager | <a href="http://digitalaction.co" target="_blank">Digital Action</a></div><p style="color:rgb(34,34,34);margin:0cm 0cm 0.0001pt"><span style="font-family:arial,sans-serif"><font color="#000000"><span style="font-size:11px"></span></font></span></p><p style="margin:0cm 0cm 0.0001pt"><font size="2" style="color:rgb(34,34,34)"><span style="font-family:arial,sans-serif"><font color="#000000">German Chancellor Fellow 21' (</font></span></font><font color="#000000" face="arial, sans-serif">Bundeskanzler-Stipendiatin</font><span style="color:rgb(0,0,0);font-family:arial,sans-serif">) | <a href="https://www.humboldt-foundation.de/" target="_blank">Alexander von Humboldt Foundation</a></span></p><p style="color:rgb(34,34,34);margin:0cm 0cm 0.0001pt"><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000">Member | <a href="https://direitosnarede.org.br/" target="_blank">Coalizão Direitos na Rede</a> </font></span></font><span style="color:rgb(0,0,0);font-family:arial,sans-serif"><br></span><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000">Co-Coordinator</font></span></font><span style="color:rgb(0,0,0);font-family:arial,sans-serif"> | <a href="https://igcaucus.org/" target="_blank">Internet Governance Caucus </a><br></span><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000"><br></font></span></font></p><div style="color:rgb(34,34,34)"><span style="font-family:arial,sans-serif"><font size="1" color="#000000"><font size="2">Twitter: <a href="https://twitter.com/boomartins" target="_blank"><font color="#1155cc">@</font>boomartins</a> // </font></font></span><span style="color:rgb(32,33,36)">Skype: bruna.martinsantos</span></div></div><div><font size="1">Email: <a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a></font></div></div></div></div></div></div></div>