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