<div dir="auto">For this call NCSG Chair would normally put out a call for the entire leadership :)</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Johan Helsingius <<a href="mailto:julf@julf.com">julf@julf.com</a>> schrieb am Sa. 4. Nov. 2023 um 16:38:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">I was assuming that it is a PC call, as the PC does decide on<br>
appointments. If the chair or EC has made the decision in the past,<br>
I don't see any reason to change the procedure.<br>
<br>
Unfortunately we are in the middle of the process of electing/<br>
reappointing EC members.<br>
<br>
Julf<br>
<br>
<br>
On 04/11/2023 12:26, Tomslin Samme-Nlar wrote:<br>
> Hi Bruna,<br>
> <br>
> I appreciate the comments.<br>
> <br>
> My proposal was based on Julf's explicit recommendation that PC takes <br>
> the slot (see my earlier question to Julf). But like I mentioned to Julf <br>
> in my question, the PC has not before been asked to make such a <br>
> decision, so I am more than happy for Julf to make the call.<br>
> <br>
> Warmly,<br>
> Tomslin<br>
> <br>
> On Sat, 4 Nov 2023, 21:13 Bruna Martins dos Santos, <br>
> <<a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a> <mailto:<a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a>>> wrote:<br>
> <br>
> Hey all,<br>
> <br>
> I’m going to open a disagreement here because I don’t think it is<br>
> fair to exclude wider NCSG leadership - aka NCSG EC members - from<br>
> this opportunity.<br>
> <br>
> I have taken part of the Leadership Training before and as the name<br>
> says it’s something that trains upcoming or incoming leadership from<br>
> communities. It’s not a policy exclusive program that would justify<br>
> using the slots exclusively for PC members.<br>
> <br>
> I understand that we need to bring in more people to the PC<br>
> leadership role but I wouldn’t use this training as an opportunity<br>
> for doing so. And would not like for us to take the chance of<br>
> attending this training away from current NCSG EC members if any of<br>
> them would also like to attend. Plus here I truly believe it’s a<br>
> decision that Julf should make instead of PC.<br>
> <br>
> Apologies for disagreeing w/ the suggested approach.<br>
> <br>
> Kind regards,<br>
> Bruna<br>
> <br>
> Wisdom Donkor <<a href="mailto:wisdom.dk@gmail.com" target="_blank">wisdom.dk@gmail.com</a> <mailto:<a href="mailto:wisdom.dk@gmail.com" target="_blank">wisdom.dk@gmail.com</a>>><br>
> schrieb am Sa. 4. Nov. 2023 um 07:13:<br>
> <br>
> No objection from me<br>
> <br>
> On Sat, 4 Nov 2023, 4:55 am Tomslin Samme-Nlar,<br>
> <<a href="mailto:mesumbeslin@gmail.com" target="_blank">mesumbeslin@gmail.com</a> <mailto:<a href="mailto:mesumbeslin@gmail.com" target="_blank">mesumbeslin@gmail.com</a>>> wrote:<br>
> <br>
> Hi Juan, all,<br>
> <br>
> I gave this a bit of further thought. I realised in the<br>
> past, it was pretty straightforward because the criteria was<br>
> simply NCSG leadership to attend.<br>
> <br>
> In the same way, to avoid an unnecessary very complex<br>
> process, I recommend we limit the criteria to Policy<br>
> Committee leadership. Another reason for limiting it to<br>
> leadership is for it to act as incentive to encourage<br>
> members who would otherwise not be interested in PC<br>
> leadership to consider it.<br>
> <br>
> NCSG charter allows for a chair and 2 vice-chairs in PC<br>
> leadership. We currently have only one vice-chair because no<br>
> one else was interested.<br>
> <br>
> Following my proposal above, in terms of eligibility for<br>
> this LP seat, only myself and the vice-chair, Peter Akinremi<br>
> are eligible. As current chair, I naturally would love for<br>
> vice-chairs to be confident enough to become chair, despite<br>
> the fact that there hasn't been any precedent of this. NCSG<br>
> struggled to have someone volunteer to be PC chair after<br>
> Rafik. That is not something I'd like to see repeating. So,<br>
> my proposal is for the current vice-chair (Akinremi Peter)<br>
> to take this LP seat that has been offered to the PC.<br>
> <br>
> Can members let me know if they object to this proposal.<br>
> <br>
> Warmly,<br>
> Tomslin<br>
> <br>
> <br>
> On Sat, 4 Nov 2023, 01:18 Juan Manuel Rojas via NCSG-PC,<br>
> <<a href="mailto:ncsg-pc@lists.ncsg.is" target="_blank">ncsg-pc@lists.ncsg.is</a> <mailto:<a href="mailto:ncsg-pc@lists.ncsg.is" target="_blank">ncsg-pc@lists.ncsg.is</a>>> wrote:<br>
> <br>
> Dear Tomslin and all,<br>
> I'd like to suggest Wisdom Donkor as a candidate to be<br>
> on the LP 2024, if he hadn't the chance before.<br>
> <br>
> *JUAN MANUEL ROJAS P.*<br>
> Director - MINKA DIGITAL Colombia<br>
> NPOC Chair - NCSG/GNSO<br>
> Master IT candidate, UNAD<br>
> Registered Linux User No.*533108.*<br>
> <a href="http://www.jmanurojas.com" rel="noreferrer" target="_blank">http://www.jmanurojas.com</a> <<a href="http://www.jmanurojas.com" rel="noreferrer" target="_blank">http://www.jmanurojas.com</a>><br>
> <br>
> /Cel. +57 301 743 56 00<br>
> Instagram/Twitter: @JmanuRojas<br>
> <<a href="http://www.twitter.com/jmanurojas" rel="noreferrer" target="_blank">http://www.twitter.com/jmanurojas</a>>/<br>
> <br>
> -----BEGIN GEEK CODE BLOCK-----<br>
> Version: 3.1<br>
> GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O<br>
> M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G<br>
> e+++(+++)>+++ h+ r++ y+<br>
> ------END GEEK CODE BLOCK------<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> El jueves, 2 de noviembre de 2023, 08:39:12 a. m. GMT-5,<br>
> Akinremi Peter Taiwo <<a href="mailto:compsoftnet@gmail.com" target="_blank">compsoftnet@gmail.com</a><br>
> <mailto:<a href="mailto:compsoftnet@gmail.com" target="_blank">compsoftnet@gmail.com</a>>> escribió:<br>
> <br>
> <br>
> For me, I would suggest you attend as the current policy<br>
> chair except we can get the new PC chair elected before<br>
> the deadline.<br>
> <br>
> Regards<br>
> <br>
> On Wed, 1 Nov 2023, 1:43 pm Tomslin Samme-Nlar,<br>
> <<a href="mailto:mesumbeslin@gmail.com" target="_blank">mesumbeslin@gmail.com</a> <mailto:<a href="mailto:mesumbeslin@gmail.com" target="_blank">mesumbeslin@gmail.com</a>>><br>
> wrote:<br>
> <br>
> Hi team,<br>
> <br>
> The PC has been asked to select someone to attend<br>
> the above program from PC leadership. I was hoping<br>
> we'd elect a new PC leadership before making<br>
> the decision but unfortunately the deadline to<br>
> submit a name for this is Wednesday, 15 November<br>
> 2023. How do you all suggest we go about this?<br>
> <br>
> Warmly,<br>
> Tomslin<br>
> <br>
> On Thu, 12 Oct 2023, 03:29 Tomslin Samme-Nlar,<br>
> <<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>
> I get it now. Makes sense.<br>
> <br>
> Warmly,<br>
> Tomslin<br>
> <br>
> On Thu, 12 Oct 2023, 02:40 Johan Helsingius,<br>
> <<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a> <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>>> wrote:<br>
> <br>
> Typically it would be the incoming NCSG<br>
> chair, but when a chair gets<br>
> re-elected, someone else in our (future)<br>
> leadership should get<br>
> to do it - PC chair, for example.<br>
> <br>
> Julf<br>
> <br>
> <br>
> On 09/10/2023 22:03, Tomslin Samme-Nlar wrote:<br>
> > Hi Julf,<br>
> ><br>
> > Is your expectation that someone from the<br>
> PC will be selected? Since I<br>
> > don't believe the PC has made a selection<br>
> for this before.<br>
> ><br>
> > Warmly,<br>
> > Tomslin<br>
> > @LinkedIn:<br>
> <a href="https://www.linkedin.com/in/tomslin/" rel="noreferrer" target="_blank">https://www.linkedin.com/in/tomslin/</a><br>
> <<a href="https://www.linkedin.com/in/tomslin/" rel="noreferrer" target="_blank">https://www.linkedin.com/in/tomslin/</a>><br>
> > <<a href="https://www.linkedin.com/in/tomslin/" rel="noreferrer" target="_blank">https://www.linkedin.com/in/tomslin/</a><br>
> <<a href="https://www.linkedin.com/in/tomslin/" rel="noreferrer" target="_blank">https://www.linkedin.com/in/tomslin/</a>>><br>
> ><br>
> ><br>
> > On Tue, 10 Oct 2023 at 00:38, Johan<br>
> Helsingius <<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a><br>
> <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>><br>
> > <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a><br>
> <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>>>> wrote:<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > -------- Forwarded Message --------<br>
> > Subject: Invitation - RSVP -<br>
> ICANN Leadership Program (LP) 2024<br>
> > Date: Fri, 6 Oct 2023 17:43:28 +0000<br>
> > From: Public Responsibility Support<br>
> <<a href="mailto:prs@icann.org" target="_blank">prs@icann.org</a> <mailto:<a href="mailto:prs@icann.org" target="_blank">prs@icann.org</a>><br>
> > <mailto:<a href="mailto:prs@icann.org" target="_blank">prs@icann.org</a><br>
> <mailto:<a href="mailto:prs@icann.org" target="_blank">prs@icann.org</a>>>><br>
> > To: Johan Helsingius<br>
> <<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a> <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>><br>
> <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a> <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>>>><br>
> > CC: Sandra Hoferichter<br>
> <<a href="mailto:info@hoferichter.eu" target="_blank">info@hoferichter.eu</a><br>
> <mailto:<a href="mailto:info@hoferichter.eu" target="_blank">info@hoferichter.eu</a>><br>
> > <mailto:<a href="mailto:info@hoferichter.eu" target="_blank">info@hoferichter.eu</a><br>
> <mailto:<a href="mailto:info@hoferichter.eu" target="_blank">info@hoferichter.eu</a>>>>, Ergys Ramaj<br>
> > <<a href="mailto:ergys.ramaj@icann.org" target="_blank">ergys.ramaj@icann.org</a><br>
> <mailto:<a href="mailto:ergys.ramaj@icann.org" target="_blank">ergys.ramaj@icann.org</a>><br>
> <mailto:<a href="mailto:ergys.ramaj@icann.org" target="_blank">ergys.ramaj@icann.org</a><br>
> <mailto:<a href="mailto:ergys.ramaj@icann.org" target="_blank">ergys.ramaj@icann.org</a>>>>, Andrea<br>
> > Glandon <<a href="mailto:andrea.glandon@icann.org" target="_blank">andrea.glandon@icann.org</a><br>
> <mailto:<a href="mailto:andrea.glandon@icann.org" target="_blank">andrea.glandon@icann.org</a>><br>
> <mailto:<a href="mailto:andrea.glandon@icann.org" target="_blank">andrea.glandon@icann.org</a><br>
> <mailto:<a href="mailto:andrea.glandon@icann.org" target="_blank">andrea.glandon@icann.org</a>>>>,<br>
> > Carlos Reyes <<a href="mailto:carlos.reyes@icann.org" target="_blank">carlos.reyes@icann.org</a><br>
> <mailto:<a href="mailto:carlos.reyes@icann.org" target="_blank">carlos.reyes@icann.org</a>><br>
> <mailto:<a href="mailto:carlos.reyes@icann.org" target="_blank">carlos.reyes@icann.org</a><br>
> <mailto:<a href="mailto:carlos.reyes@icann.org" target="_blank">carlos.reyes@icann.org</a>>>><br>
> ><br>
> ><br>
> ><br>
> > Dear Julf,<br>
> ><br>
> > It was great having you join us for<br>
> the 2023 ICANN Academy Leadership<br>
> > Program (LP)!<br>
> ><br>
> > We are now preparing for the 8^th<br>
> edition of the LP, which is<br>
> > scheduled<br>
> > to take place 29 February - 1 March<br>
> 2024, two days prior to the<br>
> > official<br>
> > start of ICANN79 in San Juan, Puerto<br>
> Rico.<br>
> ><br>
> > For this program, one seat is<br>
> reserved for a representative from the<br>
> > NCSG. As you are aware, the program<br>
> is designed for current<br>
> > /_and_/incoming leaders, helping to<br>
> increase understanding of the<br>
> > complexity of ICANN and to develop<br>
> facilitation skills, as well as<br>
> > building a network with other<br>
> leaders. We are aware that understanding<br>
> > ICANN as an organization, the topics<br>
> discussed within ICANN, and<br>
> > interaction within other stakeholder<br>
> groups can be challenging for<br>
> > incoming leaders, but sometimes also<br>
> for experienced leaders. ICANN and<br>
> > the community are making considerable<br>
> efforts in order to help incoming<br>
> > leaders have a good start to their<br>
> terms and to provide current leaders<br>
> > the opportunity to strengthen their<br>
> leadership and facilitation skills.<br>
> > Opportunities for Leadership Program<br>
> participants include the following:<br>
> ><br>
> > * Meet leaders from the other<br>
> SOs/ACs and get an insight of the<br>
> > functionality and issues in<br>
> other groups<br>
> > * Discuss current ICANN topics in<br>
> an in-depth manner<br>
> > * Deepen the understanding of key<br>
> ICANN processes<br>
> > * Develop facilitation and<br>
> leadership skills, focused personal<br>
> > effectiveness to run meetings<br>
> and foster processes<br>
> ><br>
> > A preliminary agenda is attached to<br>
> this email. Kindly note that<br>
> > this is<br>
> > subject to change.<br>
> ><br>
> > Accommodation for participants will<br>
> be covered between Wednesday and<br>
> > Thursday, 28-29 February 2024, and<br>
> participants will receive a stipend.<br>
> > Please note that flights will*NOT*be<br>
> covered under this program, as<br>
> > incoming and current leaders are<br>
> normally covered by the regular ICANN<br>
> > travel support. Please ensure that<br>
> the leaders you select are being<br>
> > covered by ICANN Travel Support for<br>
> their flights to San Juan for<br>
> > ICANN79.<br>
> ><br>
> > We would like to ask you to identify<br>
> one incoming or current leader<br>
> > from<br>
> > your stakeholder group who is<br>
> interested and available to<br>
> > participate in<br>
> > this program. We recommend that you<br>
> also identify an alternate<br>
> > candidate.<br>
> ><br>
> > *Kindly forward us the names and<br>
> email addresses of the endorsed<br>
> > individuals no later than Wednesday,<br>
> 15 November 2023, and ask them to<br>
> > register **here*<br>
> <<a href="https://forms.gle/cvr6qt5jRXGQKQNo6" rel="noreferrer" target="_blank">https://forms.gle/cvr6qt5jRXGQKQNo6</a><br>
> <<a href="https://forms.gle/cvr6qt5jRXGQKQNo6" rel="noreferrer" target="_blank">https://forms.gle/cvr6qt5jRXGQKQNo6</a>><br>
> > <<a href="https://forms.gle/cvr6qt5jRXGQKQNo6" rel="noreferrer" target="_blank">https://forms.gle/cvr6qt5jRXGQKQNo6</a><br>
> <<a href="https://forms.gle/cvr6qt5jRXGQKQNo6" rel="noreferrer" target="_blank">https://forms.gle/cvr6qt5jRXGQKQNo6</a>>>>***by<br>
> Friday, 17<br>
> > November 2023.*<br>
> ><br>
> > We hope this program will meet the<br>
> needs of your community. All<br>
> > participants will be encouraged to<br>
> partake in an open exchange of their<br>
> > views, as this will help facilitate<br>
> cross-constituency collaboration<br>
> > during their terms.<br>
> ><br>
> > We are happy to answer any questions<br>
> you may have and look forward to<br>
> > having your group’s participants<br>
> confirmed.<br>
> ><br>
> > If you would like to learn more about<br>
> the program, Sandra can give a<br>
> > short presentation at the upcoming<br>
> ICANN78 meeting at a time that is<br>
> > convenient for your group.<br>
> ><br>
> > Kind regards,<br>
> ><br>
> > Sandra Hoferichter, Chair of the<br>
> ICANN Academy Working Group<br>
> ><br>
> > Fernanda Iunes, ICANN Capacity<br>
> Development Program Manager<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>
> <mailto:<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a>><br>
> <mailto:<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
> <mailto:<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a>>><br>
> ><br>
> <a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a> <<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>
> <<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a> <<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>
> <br>
> _______________________________________________<br>
> NCSG-PC mailing list<br>
> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a> <mailto:<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>
> <<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>
> _______________________________________________<br>
> NCSG-PC mailing list<br>
> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a> <mailto:<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>
> <<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> <mailto:<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>
> <<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>
> _______________________________________________<br>
> NCSG-PC mailing list<br>
> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a> <mailto:<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>
> <<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>
> _______________________________________________<br>
> NCSG-PC mailing list<br>
> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a> <mailto:<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>
> <<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>
</blockquote></div></div>