[NPOC-EC] ICANN 76

[Andrea Glandon]

Hello all,

The trip proposal for ICANN76 was due on Friday, 20 January.

Kind Regards,
Andrea


From: NPOC-EC <npoc-ec-bounces at icann.org> on behalf of Caleb Olumuyiwa Ogundele via NPOC-EC <npoc-ec at icann.org>
Reply-To: Caleb Olumuyiwa Ogundele <muyiwacaleb at gmail.com>
Date: Sunday, January 22, 2023 at 19:30
To: Juan Manuel Rojas <jumaropi at yahoo.com>
Cc: NPOC-EC <npoc-ec at icann.org>
Subject: Re: [NPOC-EC] ICANN 76

Totally agree with you Juan. We should consult staff too.

On Sun, Jan 22, 2023, 7:19 PM Juan Manuel Rojas <jumaropi at yahoo.com<mailto:jumaropi at yahoo.com>> wrote:
Hey everyone,
I see she is outside from LAC region but she belongs to LAC region I think we could consider it and wait whether GSE have any observation on this regard. This application has my support.

My two cents,
JUAN MANUEL ROJAS P.
Director - MINKA DIGITAL Colombia
NPOC Policy Chair - NCSG/GNSO
Master IT candidate, UNAD
Registered Linux User No.533108.


Cel. +57 301 743 56 00
Instagram/Twitter: @JmanuRojas [twitter.com]<https://urldefense.com/v3/__http:/www.twitter.com/jmanurojas__;!!PtGJab4!-DpnyS7FASwhclFcnKXX7KE-G3C70v15MHshSQ9SNUmzVDuqH67sxBdYJXcXmf4W4EJaR2GmiWorlwJ6A2Y5FP6wxg$>







El domingo, 22 de enero de 2023, 08:01:12 p. m. GMT-5, Caleb Olumuyiwa Ogundele via NPOC-EC <npoc-ec at icann.org<mailto:npoc-ec at icann.org>> escribió:


Hello Guys,

Given we don't have any applications against this application,  I would support it.
However, I'm afraid her application through the GSE team might not scale through because of the location she is traveling from which is outside the LAC region.

What do you guys suggest?



On Sun, Jan 22, 2023, 6:06 PM Gloria Meneses via NPOC-EC <npoc-ec at icann.org<mailto:npoc-ec at icann.org>> wrote:
Dear NPOC E.C

I want to express my desire to attend the ICANN 76 meeting. Details for my application are described below

Name:  Gloria Patricia Meneses Portilla
Dates:

  *   Arriving: March 11th
  *   Departure City: London, UK
I consider myself as a good candidate due to my previous participation in NPOC. Despite my recent absence due to studies, I have been an active member since 2015. I have supported NPOC in different meetings, reviews and writing comments for various documents.  I have participated In a couple of opportunities as a fellow as well, which makes me understand the ICANN ecosystem.

I hope you consider the reasons above as valid.

Regards,

--
Gloria Patricia Meneses Portilla
Linux user No 542404


_______________________________________________
NPOC-EC mailing list
NPOC-EC at icann.org<mailto:NPOC-EC at icann.org>
https://mm.icann.org/mailman/listinfo/npoc-ec

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
_______________________________________________
NPOC-EC mailing list
NPOC-EC at icann.org<mailto:NPOC-EC at icann.org>
https://mm.icann.org/mailman/listinfo/npoc-ec

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/npoc-ec/attachments/20230123/29acad90/attachment-0001.html>