[NCUC-EC] [Ext] Re: NCUC Travel Support

Sun Jun 21 22:53:48 CEST 2026

Thank you Andrea and colleagues for the feedback.

Indeed , key details on travel allocation are missing and accounting for
different slots is pivotal if fairness and transparency is the objective.
ICANN staff can give us the fuller details and the comprehensive travel
slots allocation stating the nature of the slot NCSG, NCUC and CROP slots..
from what I know however, some colleagues have been attending every single
ICANN event or almost all through those ICANN NCSG constituency different
ressources (not speaking about Fellowships or self-funding).

Hence there is no fairness or regional representation equality at all
between attending all or almost all meetings and attending zero or close to
zero meetings.

Again, I wish all to attend but not at the detriment of other colleagues. I
hope we can find a way in a consultative and fair manner.

Le sam. 20 juin 2026, 19:14, Namra N via NCUC-EC <ncuc-ec at lists.ncuc.org> a
écrit :

> I need to get back on this. Wisdom this is a consultative process. You are
> missing key details here.
>
> Please account for who has been traveling maybe on different slots too and
> I remember giving up my slot and taking up crop to make space for other
> members.
>
> As a chair, the council exists to suggest/ advise you. You cannot
> unilaterally decide and expect people to oblige.
>
> On Sat, Jun 20, 2026 at 11:31 Andrea Glandon via NCUC-EC <
> ncuc-ec at lists.ncuc.org> wrote:
>
>> Hello all,
>>
>> Travel funding cannot be transferred between meetings. Once the funding
>> is lost, it is gone.
>>
>> Thanks!
>> Andrea
>>
>> On Jun 19, 2026, at 8:23 AM, Amin Hacha via NCUC-EC <
>> ncuc-ec at lists.ncuc.org> wrote:
>>
>> 
>>
>> Dear Andrea,
>>
>> I was just wondering whether, since Iness did not receive her visa for
>> ICANN86, it might be possible for the ICANN travel support to allocate the
>> budget for her trip to be transferred to ICANN87, or if that would not be
>> possible.
>>
>> Just a thought.
>>
>> Best regards,
>> Amine
>>
>> On Fri, Jun 19, 2026 at 11:19 AM Hfaiedh Ines via NCUC-EC <
>> ncuc-ec at lists.ncuc.org> wrote:
>>
>> Dear Wisdom
>>>
>>> Thank you for your email but I am sorry to disagree here. I find this
>>> utterly unfair to me and here I am speaking on my own behalf.
>>>
>>> Seeing the statistics you shared, some colleagues have already had NCUC,
>>> CROP and NCSG slots during this term and the previous one.
>>>
>>> Me on the contrary I did not any sort of any ICANN ressouced slot
>>> neither in this term or the previous one.
>>>
>>> Added to that, I did not travel to this ICANN 87 meeting due to reasons
>>> beyond my control and I have followed and applied for the visa to Spain
>>> early and with complete documents and full communication with ICANN travel
>>> team. I did not cancel the trip myself.
>>>
>>> I wish to all the EC team to attend through ICANN ressources or else but
>>> I am sorry to not accept being treated unfairly.
>>>
>>>
>>> Le ven. 19 juin 2026, 10:01, Wisdom Donkor via NCUC-EC <
>>> ncuc-ec at lists.ncuc.org> a écrit :
>>>
>> Dear EC,
>>>> Regarding ICANN 87 travel. I requested the travel statistics, and I
>>>> am happy to share them with the EC.
>>>>
>>>> See below the travel statistics:
>>>>
>>>>
>>>>
>>>> ICANN82
>>>>
>>>> Wisdom Donkor
>>>>
>>>> NCUC chair
>>>>
>>>> Amin Hacha
>>>>
>>>> NCUC EC
>>>>
>>>> Mili Semlani
>>>>
>>>> NCUC EC
>>>>
>>>>
>>>>
>>>> ICANN83
>>>>
>>>> Wisdom Donkor
>>>>
>>>> NCUC chair
>>>>
>>>> Namra Naseer
>>>>
>>>> NCUC EC
>>>>
>>>> Sara Ali
>>>>
>>>> NCUC EC
>>>>
>>>>
>>>>
>>>> ICANN84
>>>>
>>>> Wisdom Donkor
>>>>
>>>> NCUC chair
>>>>
>>>> Mili Semlani
>>>>
>>>> AP rep
>>>>
>>>> trip canceled by EC
>>>>
>>>> Amin Hacha
>>>>
>>>> EU rep
>>>>
>>>> ICANN85
>>>>
>>>> Wisdom Donkor
>>>>
>>>> chair
>>>>
>>>> Pedro
>>>>
>>>> EC LAC
>>>>
>>>> Juliana
>>>>
>>>> EC AP
>>>>
>>>>
>>>>
>>>> ICANN86
>>>>
>>>> Wisdom Donkor
>>>>
>>>> chair
>>>>
>>>> Namra Naseer
>>>>
>>>> Did not travel/Visa
>>>>
>>>> Ines
>>>>
>>>> Did not travel/Visa
>>>>
>>>> Based on the statistics and in the interest of fairness and balanced
>>>> regional representation, I am approving the following candidates for ICANN
>>>> 87:
>>>>
>>>>    1. *Pedro*
>>>>    2. *Amin*
>>>>
>>>> In addition, *Juliana* will be supported through the CROP programme to
>>>> help mobilise and strengthen participation from her region:
>>>>
>>>> I also understand that there is one GNSO Council travel slot that may
>>>> become available, which could potentially be allocated to another member of
>>>> the Executive Committee. In any case, we still have some time before final
>>>> decisions need to be made.
>>>>
>>>> Andrea will continue to provide guidance and updates as the process
>>>> unfolds to ensure that no travel slot goes unused, as unfortunately
>>>> occurred in the case of ICANN 86. This will help us maximise available
>>>> opportunities and ensure effective representation of the constituency.
>>>>
>>>> Regards,
>>>>
>>>> *Wisdom Donkor* (CASP+,  CISM, CEH Certified,)
>>>> Chair, NCUC
>>>> Tel: +233 20 812 8851
>>>> Skype: wisdom_dk | Facebook: kwasi wisdom |  Twitter: @wisdom_dk
>>>>
>>>> _______________________________________________________________________________________________________________________
>>>> ICANN GNSO Council Member | ICANN transfer policy review working group
>>>> Member  | Council Committee for Overseeing and Implementing Continuous
>>>> Improvement (CCOICI) | UN IGF MAG Member | IGF Support Fund
>>>> Association Executive Committee Member, World Bank Independent Consultant
>>>> | AU AFIGF Member |  Ghana OGP Advisory Committee member | GSS SDGs
>>>> Advisory Committee Member
>>>>
>>>> ____________________________________________________________________________________________
>>>> Specialization:
>>>> E-government Network Infrastructure and E-application, Internet
>>>> Governance,  Open Data policies platforms & Community Development, Cyber
>>>> Security, Geospatial Technologies, Open Source Technologies, Domain Name
>>>> Systems, Human Resource Planning and Development, Software Engineering,
>>>> Event Planning & Management,
>>>> _______________________________________________
>>>> NCUC-EC mailing list
>>>> 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!_hiG2jDn3Mtk7dp-9kHryaW54pKN2nM8IckqkAXSnINuIIQtLm_m3-mqY4Yvna9lFBrYp6AFRSIk7CxLdk2KuBzKPciWYA$>
>>>>
>>> _______________________________________________
>>> NCUC-EC mailing list
>>> 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!_hiG2jDn3Mtk7dp-9kHryaW54pKN2nM8IckqkAXSnINuIIQtLm_m3-mqY4Yvna9lFBrYp6AFRSIk7CxLdk2KuBzKPciWYA$>
>>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>>
>> https://urldefense.com/v3/__https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!_hiG2jDn3Mtk7dp-9kHryaW54pKN2nM8IckqkAXSnINuIIQtLm_m3-mqY4Yvna9lFBrYp6AFRSIk7CxLdk2KuBzKPciWYA$
>> [lists[.]ncuc[.]org]
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>
> _______________________________________________
> NCUC-EC mailing list
> NCUC-EC at lists.ncuc.org
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20260621/d37e5e7a/attachment-0001.htm>