[NCUC-DISCUSS] [Ext] Fellowship Request for ICANN 62 Policy Forum

Arsène Tungali arsenebaguma at gmail.com
Thu Mar 8 08:14:52 CET 2018


Well said, Olga and so sorry Claire this happened to you! Hope you are able to make it for next rounds!

-----------------
Arsène Tungali,
about.me/ArseneTungali
+243 993810967
GPG: 523644A0
Goma, Democratic Republic of Congo

Sent from my iPhone (excuse typos)

> On Mar 6, 2018, at 12:19 PM, Olga Kyryliuk <olga_kyryliuk at ukr.net> wrote:
> 
> Dear Renata and All,
> 
> I believe there was nothing wrong in bringing the issue to the attention of the constituency. This is life, things happen - both good and bad. And people need support not only with "congrats" but especially in situations, which just don't go right. Easy to judge when situations like this don't concern us personally. It's not a matter of influencing or reversing the decision, which is done. In my understanding chair's request was only about double-checking the administrative procedures before giving false hopes in the future. 
> 
> Regards,
> Olga Kyryliuk
> 
> 
> 4 марта 2018, 14:56:43, от "Renata Aquino Ribeiro" <raquino at gmail.com>:
> 
> Hi
> This fellowship cancellation is done and this is irreversible, as well as whatever effect it had.
> Fellowship program (regional or otherwise) does not have consultation w/ Chair or Constituency, never did. So there is possibility to influence the process. All Chair does is distribution of call. 
> There was really a public call and public announcement of results. There usually is an announcement of results for funding processes in our mailing lists, even when Constituency leader is just the "messenger" and selection is done by organization, just like we let members know when Nextgen or Fellowship results are out. 
> James G. (long time no speak!) and Stephanie, on your concerns on sharing this "glitch in the system" thread:
> I addressed 1 member distress situation and asked for this not to happen again.
> Perhaps you are right I didn't need to see the thread, for that I apologize.
> However the enigmatic situation which caused all this remains and I reinforce that it should not happen to any other member.
> While the result of this process, so far, that we know of, affected only one member, the whole process was public as a call was shared and inquiries/applications were sent by a dozen or so members. So informing members and having the thread for proof is what I decided to do.
> Best,
> Renata
> 
> 
>  _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20180308/4d35a98d/attachment.html>


More information about the Ncuc-discuss mailing list