[NCUC-EC] [Ext] Re: ICANN 77 Funded Traveler slots

Fri Feb 10 14:47:43 CET 2023

Hi Andrea. Thanks for clarifying (or rather, reminding!). Indeed, we were discussing now and agreed to put out a call today for someone to use that slot.

We really do need to avoid these last-minute vacancies that we have to scramble to fill.

Ken

From: Andrea Glandon <andrea.glandon at icann.org> 
Sent: Friday, February 10, 2023 8:12 AM
To: Ken Herman <ken at kherman.com>
Cc: Benjamin Akinmoyeje <benakin at gmail.com>; Exec. Comm <ncuc-ec at lists.ncuc.org>
Subject: Re: [NCUC-EC] [Ext] Re: ICANN 77 Funded Traveler slots

Hi Ken! 

The NCSG EC NCUC representatives are unable to attend so there is a slot from them available as well.

Sent from my iPhone

On Feb 10, 2023, at 5:04 AM, Ken Herman <ken at kherman.com <mailto:ken at kherman.com> > wrote:

I am not sure this is correct, Benjamin, unless I am misunderstanding something:

3 EC slots (deadline Feb 13): 

1.	Benjamin (As chair)
2.	Ines (EC Member)
3.	Claudio (EC member)

1 CROP slot (deadline April):

4.	To be determined

Ken

From: NCUC-EC <ncuc-ec-bounces at lists.ncuc.org <mailto:ncuc-ec-bounces at lists.ncuc.org> > On Behalf Of Benjamin Akinmoyeje
Sent: Friday, February 10, 2023 7:45 AM
To: Andrea Glandon <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org> >
Cc: Exec. Comm <ncuc-ec at lists.ncuc.org <mailto:ncuc-ec at lists.ncuc.org> >
Subject: Re: [NCUC-EC] [Ext] Re: ICANN 77 Funded Traveler slots

Dear Andrea and Ken,

Thank you for coming out of your team's working schedule and responding to this discussion.

As things stand this is what we have 

1. Benjamin 

2. Ines

3. Claudio (my previous recommendation )

4. vacant ( we need to decide whether we give it to an EC (Mili) or quickly put it out for members, especially someone who can support NCUC - NCSG activities at that meeting )

This will be my take.

Kind regards,

Benjamin

On Fri, Feb 10, 2023 at 2:41 PM Andrea Glandon <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org> > wrote:

Hello all! 

I would just like to pop in here real quickly. What I am seeing is that the NCUC has 4 slots for ICANN77.

Benjamin will use one slot. Who is using the other 2 “EC” slots?

There will also be the CROP slot that is only available for someone from North America. 

Thanks!

Sent from my iPhone

On Feb 10, 2023, at 4:12 AM, Benjamin Akinmoyeje <benakin at gmail.com <mailto:benakin at gmail.com> > wrote:

Dear Olga,  

Thank you for the update. I am super sorry to know this.

I think at this point we probably have to reach out to the mailing list to request a replacement before Monday.

Or what does the EC recommend?

Kind regards,

Benjamin 

On Fri, Feb 10, 2023 at 2:09 PM Olga Kyryliuk <olga_kyryliuk at ukr.net <mailto:olga_kyryliuk at ukr.net> > wrote:

Hi All! 

As I said before and to confirm - I won’t be able to travel to ICANN 77 in Washington. Feel free to use my slot this time.

Best,

Olga

9 лютого 2023 р. о 15:59:58,від "Cláudio Lucena" < <mailto:claudiokilla at gmail.com> claudiokilla at gmail.com>: 

Dear ECs, 

As for ICANN77, I am available to attend the meeting and with dates already blocked, but I have the impression that the CROP funding that I am receiving for ICANN76 prevents me from applying again. And, in any case, I'll just follow and confirm the collective decision if the allocation of the EC slots have already been discussed and aligned in meetings prior to my appointment. I'll then either try to secure another source of funding or attend remotely.

I believe all MIli's suggestions of criteria for eventual extra slots make a very good process of promoting fair opportunities. I'll just point out that the shortlisting task will probably make us go back to another round of defining objective criteria for the list, although it's definitely useful, productive and generates participation incentive. Finally, a concern I share with Benjamin, is that we should make sure that we are neither expanding nor narrowing the guidelines which are already set out in the Bylaws and existing travel policies.

best,

Cláudio

--

Cláudio S. de Lucena Neto

Head of the International Office

Professor of Law, Center for Legal Studies

Paraíba State University (UEPB), Brazil

*

Membro do Conselho Nacional de Proteção de Dados Pessoais e da Privacidade (CNPDP)

Autoridade Nacional de Proteção de Dados (ANDP)

*

Researcher, Fundação para a Ciência e a Tecnologia

Ministério da Ciência, Tecnologia e Ensino Superior de Portugal

*

PhD Candidate, Research Centre for the Future of Law

Católica Global School of Law, Universidade Católica Portuguesa

LinkedIn:  <https://urldefense.com/v3/__https:/br.linkedin.com/pub/cl**Audio-lucena/22/7a8/822__;w6E!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BAPlzoPN$> https://br.linkedin.com/pub/cláudio-lucena/22/7a8/822 [br.linkedin.com]

Universidade Estadual da Paraíba

 <https://urldefense.com/v3/__https:/br.linkedin.com/pub/cl**Audio-lucena/22/7a8/822__;w6E!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BAPlzoPN$> www.uepb.edu.br [br.linkedin.com]

Centro de Ciências Jurídicas - Campus I

Departamento de Direito Privado

Rua Coronel Salvino de Figueiredo, 157

CEP 58.400-253

Campina Grande - PB - Brasil

Fone/Fax: *55 83 3310 9753

CONFIDENTIALITY NOTICE

This message, as well as any attached document, may contain information that is confidential and privileged and is intended only for the use of the addressee named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying or distribution of this email or attached documents, or taking any action in reliance on the contents of this message or its attachments is strictly prohibited and may be unlawful. Please contact the sender if you believe you have received this email by mistake.

Em qua., 8 de fev. de 2023 às 12:29, h i <hfaiedh.ines2 at gmail.com <mailto:hfaiedh.ines2 at gmail.com> > escreveu:

Regarding the roster, i really like the idea but suggest this is done while still sticking to the open call for transparency and tracability matters.

Having this roster, we can  send them reminders to apply if they are not for example aware of the calls for applications.

On Wed, Feb 8, 2023, 14:17 Mili Semlani <milisemlani at gmail.com <mailto:milisemlani at gmail.com> > wrote:

Hi Benji

  We dont have to change any bylaws. We ONLY have to agree up on some basic guidelines and processes for us to follow. Which is something we can propose and gather consensus between the 6 of us on this email thread itself. 

here are my 2 cents to the proposal

1. For the extra slots

- To be used for the community only. But instead of an open call, we put together a shortlist of the top 3 most active participants we have observed in the last 6 months. 

- We should use the funding to fly in someone from the furthest distance possible to maximise the use of the fund and someone from a nearer time zone can still virtually manage the timezone and attend the meeting virtually

- It should not go to anyone who has received CROP, or any other funding from NCUC/SG in the last 6 months to give a chance to people who haven't attended in person 

2. For the extra slots

- In addition to the policy here  <https://urldefense.com/v3/__https:/www.ncuc.org/get-involved/travel-policy/__;!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BAhf2eqK$> https://www.ncuc.org/get-involved/travel-policy/ [ncuc.org], we should also buffer for contingencies eg: If the funded member is unable to go (after confirmation due to unforeseen circumstances like health, visa or securing any other kind of funding) then, such slots should be opened back to the remaining EC members (including the Chair's slot)

- In doing so, the EC member furthest away from the destination of the meeting should be given the first preference again to maximise the use of the fund and someone from a nearer time zone can still virtually manage the timezone and attend the meeting virtually

Feel free to add any more guidelines. And denote if you agree or disagree with these.

--

With gratitude

Mili Semlani

Community specialist

 <https://urldefense.com/v3/__https:/www.instagram.com/theuntraveller/__;!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BJym8kCG$> Instagram [instagram.com] |  <https://urldefense.com/v3/__https:/www.linkedin.com/in/milisemlani/__;!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BAJZZJ32$> LinkedIn [linkedin.com]

On Wed, 8 Feb 2023 at 18:31, Benjamin Akinmoyeje <benakin at gmail.com <mailto:benakin at gmail.com> > wrote:

Dear Mili & ECs,

Your recommendations are greatly appreciated. However are they achievable within the timeframe?

I agree we should create the process, but there are guidelines in the Bylaws on how to change the process. Someone has to develop the draft and that should be happening already.

The process of changing or creating a guideline may be too late for these selections.

I agreed with your suggestions and I only pointed you to the existing travel policy.

All I expect now is for us to agree on who are the two ECs going to ICANN77 by default, and my suggestion is 

Olga and Ines - with clear expectations or TOR developed for both ICANN-supported funded travel slots.

In the case of the NCSG  travel slot one, we should consider another NCUC  EC - and my immediate suggestion here will be Claudio since he just only got the CROP and hopefully, he can represent the NCSG appointee during the NCSG session (we develop clear expectations or TOR). If not we throw the slot open to the membership.

Hence subsequent travel slot selections can follow as you have recommended... This is my take at this moment.

Kind regards,

Benjamin 

_______________________________________________
NCUC-EC mailing list
NCUC-EC at lists.ncuc.org <mailto:NCUC-EC at lists.ncuc.org> 
https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org] <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BPgtQEJN$> 

_______________________________________________
NCUC-EC mailing list
NCUC-EC at lists.ncuc.org <mailto:NCUC-EC at lists.ncuc.org> 
https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org] <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BPgtQEJN$> 

_______________________________________________
NCUC-EC mailing list
NCUC-EC at lists.ncuc.org <mailto:NCUC-EC at lists.ncuc.org> 
https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org] <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BPgtQEJN$> 

_______________________________________________
NCUC-EC mailing list
NCUC-EC at lists.ncuc.org <mailto:NCUC-EC at lists.ncuc.org> 
https://urldefense.com/v3/__https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BPgtQEJN$ <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!-9w5Zonc5q7W1MxVNC4xRv1EXjx5oGY-73KzjsX6w7TDNk8S5IsR8MnEg--ybYtoRcyl_261MeH4BGP5BPgtQEJN$>  [lists[.]ncuc[.]org]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20230210/3924eb1e/attachment-0001.htm>