[NCUC-EC] ICANN 77 Funded Traveler slots

[h i]

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> 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://www.ncuc.org/get-involved/travel-policy/, 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
> Instagram <https://www.instagram.com/theuntraveller/> | LinkedIn
> <https://www.linkedin.com/in/milisemlani/>
>
>
>
> On Wed, 8 Feb 2023 at 18:31, Benjamin Akinmoyeje <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
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20230208/37e28930/attachment-0001.htm>