[NCUC-EC] Reminder: Procedures for EC funding allocation

Louise Marie Hurel louise.marie.hsd at gmail.com
Sun Mar 25 20:09:00 CEST 2018


Dear Chair and EC,

After having demonstrated my interest in attending ICANN62 as part of the
EC team travel slots, I would kindly ask that you consider this my formal
application. As previously mentioned, I will also be representing NCUC at
the Onboarding team as Kathy Kleiman’s mentee and would be delighted to
work on organizing outreach/inreach for NCUC as part of the EC priorities
for ICANN62.

My suggestion would be to work in liaising with EC LAC in consolidating
outreach with NCUC-members and organizations (i.e. IPANDETEC -
Panama-based) so that they can help us to connect with local/regional
community and thus communicate some of the main themes that we have been
working in policy. The objective here would be to establish an open
dialogue following the successful experience we had in Johannesburg
(ICANN59) last year.

Given that this is a Policy Forum, we have to optimize our use of time and
channel our efforts to specific activities. For our Constituency session,
I’d suggest we use it go over the status of working groups and aligning our
priorities for the course of the second semester of 2018 and keep it an
open space for fellows to get better acquainted with our
work/views/positions (maybe a more dynamic Q&A with some of them, as we did
last year in Copenhagen, just to get a general yet more objective feeling
on what they might be interested in). But I’d also agree that this can be
further detailed as we have a clearer view of the overall Agenda.

As previously mentioned, Kathy, Dina and I are part of the Onboarding Team
- working on developing tools for making it smoother for newcomers to
better understand ICANN and NCUC as well as gradually create a cycle of
mentorship and capacity building. I have been an active member at the
Rights Protection Mechanisms working group and following closely the
CCWG-IG as an observer. Given my interest in security, I have also recently
teamed up to write a public comment on the postponing of the KSK Rollover -
where I could apply some of the skills and tips I got to learn during the
Policy Writing course in ICANN61.

Hope this provides a quick insight as to the potential work-plan we might
develop for this meeting and some of my current activities. I remain at
your disposal, should you need any other information.

Kind regards,

Louise Marie Hurel

Cybersecurity Project Coordinator | Igarapé Institute

London School of Economics (LSE) Media and Communications (Data and Society)
Skype: louise.dias
+44 (0) 7468 906327
*l.h.dias at lse.ac.uk <l.h.dias at lse.ac.uk> *
louise.marie.hsd at gmail.com


2018-03-23 16:01 GMT+00:00 Renata Aquino Ribeiro <raquino at gmail.com>:

> Hi
>
> Thank you Ines for completing your application
> As we've had an extension to the deadline I'll review all applications and
> send notes soon
>
> Thanks
>
> On Thu, Mar 22, 2018 at 5:39 PM, hfaiedh ines <hfaiedh.ines2 at gmail.com>
> wrote:
>
>> Thank you Renata
>>
>> My suggested Activity Plan for ICANN62 which will be more developed once
>> schedule is out, I think as it is a Policy meeting, I hope we can still
>> have an outreach initiative during or after the NCSG Policy Course to make
>> sure attendees understand what NCUC is and where it stands in NCSG and
>> ICANNin general.
>> For outreach, I would highly recommend, for the interest of time and
>> since we will not have a constituency day, that we focus only on NCUC in
>> our outreach or NCSG as a stakeholder.
>> I have received great feedback on our outreach sessions we held with
>> At-large but I feel we might need this opportunity to highlight who we are
>> and what we do in a more targeted way and I would like to be part of the
>> outreach efforts in planning and onsite facilitation, moderation or
>> presentation.
>> I also see outreach as an opportunity to share work on track-issues: We
>> can invite experienced and knowledgeable community members as well as
>> mentees. I joined WT5 since its creation and asked Robin Gross for
>> mentorship right away which she accepted and, though it hasn't made
>> tremendous steps, I have contributed to the work that was put on the table
>> such as made suggestions on  the Definition and Treatment of Geographic
>> names Document and.the Terms of Reference Document.
>> I have also contacted Collin Cure before ICANN61 to learn more about the
>> CCWP on Human Rights and recently requested to join the mailing list. I am
>> looking forward to learning as much as possible from it. I am also part of
>> the Drafting Team of “The Middle East Statement on WHOIS Compliance with
>> GDPR” chaired by Farzaneh Badiei  and aiming to take part on the next
>> comments as well.
>> For our NCUC Constituency session, in addition to NCUC Introduction and
>> EC briefings, I suggest we keep securing the time for ICANN fellows
>> questions and hearing from NCUC Fellows on their mentor-mentee experience
>> and their learning experience from the NCSG Policy Course. If time allows,
>> we could have some of our members sharing some regional initiatives related
>> to NCUC work (I hope active Remote Participation will be back to ICANN
>> meetings). If done at earliest convenience, it would be great to invite
>> ICANN CEO or some Board members and update them on the topics NCUC is
>> working on.
>>  One last suggestion that I have noticed while volunteering at the booth
>> lately, NCUC is very attractive to a lot of people who are interested in
>> contributing to our issues, we just need to clarify where we are in ICANN
>> Ecosystem in the easiest way possible whether at outreach, NCUC session,
>> ICANN Fellowship session or at ICANN Information Booth and I am looking
>> forward to helping in these efforts.
>>
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Garanti
>> sans virus. www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>> <#m_-2953791795291581346_m_-4814756193997399373_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> 2018-03-20 16:59 GMT+01:00 Renata Aquino Ribeiro <raquino at gmail.com>:
>>
>>> Hi
>>>
>>> As a reminder, these are the procedures for EC funding allocation
>>> Note that EC allocated funds to ICANN61 should send to publication their
>>> reports
>>>
>>> Thanks
>>>
>>> -----
>>>
>>> https://www.ncuc.org/get-involved/travel-policy/
>>>
>>> Procedures for EC funding allocation
>>>
>>>  – ICANN Meetings funding allocation for Executive Committee
>>> representatives
>>>
>>> –  Executive Committee representatives travel support allocations
>>>
>>> For each ICANN Meeting, the NCUC leadership team is allocated three
>>> travel slots. One of these travel slots must be assigned to the NCUC
>>> Chair. The remaining two travel slots, or a reallocation of the
>>> Chair’s travel slot if he or she relinquishes it, will be assigned to
>>> representatives who fulfill the following criteria:
>>>
>>> The representative develops an activity plan that he or she will carry
>>> out in the ICANN meeting. This plan must contain a detailed account of
>>> the representative’s current engagement in ICANN activities, their
>>> plan of engagement at the face-to-face meeting, and explain why and
>>> how their physical presence in that meeting is important for achieving
>>> the NCUC’s objectives and mission. The timeline for the submission of
>>> this application will follow the procedure described in the NCUC
>>> Travel Support Policy unless initiated sooner by the NCUC Chair at his
>>> or her discretion. The EC travel funding allocation should precede
>>> NCUC travel support programme.
>>> The representative must observe all criteria for eligibility as
>>> described in the NCUC Travel policy session above, highlighting the
>>> participation on NCSG and NCUC activities.
>>> In case of a tie between applicants, the Chair will ask
>>> representatives to make reasonable efforts to find an alternative
>>> source of funding. Evidence must be provided to the Chair of these
>>> attempts. If a representative seeks alternative funding but is
>>> declined or rejected, this will not be held against them.
>>> Representatives who make no reasonable efforts to find alternative
>>> funding will receive lower priority for NCUC resources than those who
>>> make reasonable efforts;
>>> Where there are more candidates for a slot than there are slots
>>> available, the regional designation of the EC representative may be a
>>> factor weighing in its allocation. The EC representative must send a
>>> detailed action plan outlining their plans for inreach/outreach of
>>> membership within their region;
>>> As described in Eligibility criteria, EC who have received travel
>>> support for the previous meeting cannot apply again.
>>> In receiving funding for a meeting, travellers agree to write daily
>>> reports during the meeting to update the membership on the proceedings
>>> . At his or her discretion, the NCUC Chair may choose to publish these
>>> reports as a blog post, or may request that the representative convert
>>> their report into a blog post.
>>> If a representative receives support, and does not meet their
>>> commitments as outlined above, they will be ineligible to receive
>>> further NCUC resources.
>>>
>>> References:
>>>
>>> NCUC Operating Procedures
>>>
>>> https://www.ncuc.org/wp-content/uploads/2017/09/NCUC-Operati
>>> ng-Procedures-Sept-2017.pdf
>>>
>>> (Noting item III Travel support selection and VI Outreach and VII
>>> Funding)
>>>
>>> NCUC Bylaws (Esp. Item XI.A on Transparency)
>>>
>>> https://www.ncuc.org/bylaws/
>>> _______________________________________________
>>> 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/20180325/984498c2/attachment.html>


More information about the NCUC-EC mailing list