[NCUC-EC] Request for Acceptance and Approval to Submit CROP Proposal Form

Tue Aug 29 11:09:20 CEST 2023

Thank you Mili good point

TBH I totally lost track of who got funding for what and when, so it makes
sense to give an opportunity to other members.

That said we need to decide if the CROP slot is going to be used this time
or for next meetings.

On Tue, Aug 29, 2023, 05:51 Mili Semlani <milisemlani at gmail.com> wrote:

> My two cents
>
> *Re CROP slots for other non ICANN events*
> Agree with the rest above to use only 1 slot for an ICANN meeting. The
> CROP fund can be used for other IG-related events too. There is IGF Kobe
> and if someone from the membership wants to attend this and has a plausible
> cause, we can also run a new application round for that or other such
> events before the end of 2023. This will also help us use available
> opportunities for enabling member participation and our community will feel
> supported.
>
> *Re Amine's application*
> While Amine's application for CROP is relevant and he is an incoming EC
> member but I feel we will be ending up funding the same person repeatedly.
> Since we have been flagged for this in the past, I think we should consider
> it a bit more closely. Amine was funded for DC by the EC (Robin and David
> Morars extra slot and he was CROP funded for KL meeting from the APAC
> region).
>
> We should optimize all available funding for more effective and engaged
> participation and we really need to win the support of our member community
> especially in the light of incidents in 2023.
>
> *A couple of things we need clarity on *@Andrea Glandon
> <andrea.glandon at icann.org>
> 1. Until when can we use the 2 CROP slots we have? What is the deadline
> (month and year will be great)
> 2. Is the confusion around Oksana's eligibility sorted? Does Oksana
> qualify for CROP if she is flying from any other place in the EU and not
> Ukraine?
> 3. Just for clarification's sake, which CROP region would people (flying
> in and out of Ukraine qualify for?
> --
> With gratitude
> *Mili Semlani*
> Community specialist
> Instagram <https://www.instagram.com/theuntraveller/> | LinkedIn
> <https://www.linkedin.com/in/milisemlani/>
>
>
>
> On Tue, 29 Aug 2023 at 00:34, Hfaiedh Ines <hfaiedh.ines2 at gmail.com>
> wrote:
>
>> Thank you Olga.
>>
>> I agree with you on using one CROP slot per meeting.
>>
>> Not an easy decision indeed, on the one hand an EC colleague who would
>> benefit from attending and also help in the preparations.
>> Also am thinking that maybe given the limited days allocated in CROP, a
>> regular NCUC member won't get as much as desired from the meeting.
>>
>> Just thinking out loud, so my vote would go for Amine for the interest of
>> time and quick answer.
>>
>>
>> On Mon, Aug 28, 2023, 19:25 Olga Kyryliuk <olga_kyryliuk at ukr.net> wrote:
>>
>>> So we have two applications - by Oksana and Amine submitted next day
>>> after deadline. Andrea says we can allocate two slots but if it precludes
>>> us from using CROP for the upcoming ICANN meetings, I would be in favor of
>>> using only one slot per meeting. And if so we need to vote on two submitted
>>> applications if we decide to accept Amine’s given later submission.
>>>
>>>
>>> * 28 серпня 2023 р. о 19:52:40, від "Benjamin Akinmoyeje"
>>> <benakin at gmail.com <benakin at gmail.com>>: *
>>>
>>> >
>>> Dear ECs,
>>> Good day and I hope you are doing well.
>>>
>>> Please your response is highly appreciated on this request.
>>>
>>> Kind regards,
>>> Benjamin
>>>
>>> On Fri, Aug 25, 2023 at 5:11 PM Benjamin Akinmoyeje <benakin at gmail.com>
>>> wrote:
>>>
>>> Dear Amin,
>>> Thank you for your email and expression of interest.
>>>
>>> It is noted accordingly.
>>> Kind regards,
>>> Benjamin
>>>
>>> On Fri, Aug 25, 2023, 2:21 PM Amin Hacha <aminhacha at gmail.com> wrote:
>>>
>>> Dear chair and EC members,
>>> I hope this email finds you well. I am writing to formally request your
>>> acceptance and approval to proceed with the submission of the CROP
>>> (Collaborative Research Opportunity Proposal) form to reach travel support
>>> for Humburg ICANN78.
>>>
>>> I have carefully reviewed the CROP program, as I am a resident in Italy
>>> and the coming ICANN78 will be organized in the same constitutional area in
>>> Europe. Also, it will be an opportunity for me to attend ICANN78 in person,
>>> especially since I will be the same regional representative of NCUC soon.
>>>  I kindly request your guidance and approval to move forward with the
>>> submission of the CROP proposal form.
>>>
>>> Thank you very much for considering my request. I greatly appreciate the
>>> opportunity to be part of the NCUC and contribute to its mission. I look
>>> forward to your positive response.
>>> N.B. You can find below my answers to the questions asked.
>>>
>>> Warm regards,
>>> Amine Hacha
>>>
>>> -------------------------------------------------
>>>
>>> Please complete the following and send to the email addresses listed
>>> below. Once the EC approves then you will fill out the CROP proposal form,
>>> but I will help you with that once we get to that point.
>>>
>>>
>>>
>>> *How to apply: *If you are interested to be considered for CROP
>>> funding, make sure to submit your expression of interest to
>>> ncuc-ec at lists.ncuc.org
>>>
>>> and andrea.glandon at icann.org *by 23:59 CEST on 24 August 2023*.
>>>
>>>
>>>
>>> *What should be included in the expression of interest:*
>>>
>>>    1. Name    *  AMINE HACHA*
>>>    2.      Email    *aminhacha at gmail.com <aminhacha at gmail.com>*
>>>    3.      Short explanation of how you have contributed to NCUC
>>>    activities and policy discussions to date.   *I have been an active
>>>    participant in NCUC activities and policy discussions, offering my insights
>>>    and perspectives on various issues related to noncommercial internet users.
>>>    I have attended regular meetings and engaged in working groups. I am
>>>    looking forward to serving NCUC as a region representative at the EC. Also,
>>>    I am a member of the FY25 Planning Prioritization Group from the side of
>>>    GNSO - NCSG.*
>>>    4. Short statement explaining why you would like to attend ICANN78
>>>    representing the NCUC. Include a mention of which working groups or
>>>    policy discussions you have been involved with and would like to be
>>>    involved further. If you have not been involved in policy discussions,
>>>    which policy discussion(s) you will become involved with. Please provide
>>>    links to your mailing list contributions and your record of attendance in
>>>    WG meetings.  *My active involvement in various working groups, such
>>>    as the Privacy and At/large working group, and UA, during several previous
>>>    ICANN meetings. I am eager to further contribute to these discussions and
>>>    collaborate with stakeholders to advocate for the interests of
>>>    noncommercial users.*
>>>    5. Short explanation how you plan to stay engaged in NCUC after the
>>>    ICANN78 meeting. *To stay engaged in NCUC after the ICANN78 meeting,
>>>    especially that this ICANN 78 will be organized in Europe the same region
>>>    area which I will be involved soon to help NCUC into it. I intend to
>>>    continue my active participation in working groups and policy discussions.
>>>    I will regularly attend virtual meetings and contribute to the ongoing
>>>    efforts working group. Additionally, I plan to collaborate closely with
>>>    fellow NCUC members in the region to exchange ideas, share insights, and
>>>    contribute to policy recommendations. *
>>>    6. Confirm that you can obtain visa on time, if visa is needed for
>>>    your travel. If you do not need a visa, please indicate so. *I
>>>    confirm that as a resident of Europe I don't need a visa to travel to
>>>    Germany.*
>>>
>>>
>>>
>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>> Virus-free.www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>> <#m_6496790243142264627_m_617067390982997217_m_-6341009291472314807_m_6082017513251129765_m_3530382136314735976_m_-6473313741522797916_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>> _______________________________________________
>>> NCUC-EC mailing list
>>> NCUC-EC at lists.ncuc.org
>>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>>
>>> _______________________________________________
>>> NCUC-EC mailing listNCUC-EC at lists.ncuc.orghttps://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
>>>
>> _______________________________________________
>> 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/20230829/e6de7334/attachment-0001.htm>