<div class="__aliyun_email_body_block"><div style="clear:both;"><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;">Hi all,</div><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;"><br ></div><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;">Many thanks to those who contributed to the discussions.</div><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;"><br ></div><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;">Also, thanks to Rafik for reaching out to Heather (GNSO's representative on the ICANN Fellowship Selection Committee) who authored the strawman list and has kindly responded to some of the comments from our Councilors: <ul style="font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;text-decoration:none;caret-color:#000000;color:#000000;background-color:#ffffff;"><li ><a href="https://mm.icann.org/pipermail/council/2019-April/022566.html" target="_blank">[council] Fellowship Selection Process - Council questions answered </a></li></ul><pre style="font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;text-decoration:none;caret-color:#000000;color:#000000;background-color:#ffffff;">"There are universal criteria that apply to all applications; a basic ability to communicate in English is indeed inherent in the process, as
applications must be submitted in English and understandable to the Selection Committee members. It seems to me that it is not necessary to
specify English language ability as a GNSO-specific criterion."</pre></div><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;">In light of Heather's response, I think we can delete the bullet "<span style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Calibri;font-size:14.7px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:-24.0px;text-transform:none;background-color:#ffffff;text-decoration:line-through;float:none;display:inline;">Ability to communicate in English orally and in writing, in a respectful and constructive manner</span><span style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Calibri;font-size:14.7px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:-24.0px;text-transform:none;background-color:#ffffff;float:none;text-decoration:none;display:inline;"> ".</span> </div><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;"><br ></div><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;">With regard to Darcy's' suggested edits, I am leaning towards keeping "<span style="margin:.0px;padding:.0px;border:.0px;outline:.0px;font-family:Calibri;font-size:14.7px;text-indent:-24.0px;">Willingness to adhere to the ICANN’s Expected Standards of Behaviour" <span style="margin:.0px;padding:.0px;border:.0px;outline:.0px;text-indent:-24.0px;font-size:14.0px;font-family:tahoma;">as it is much broader than just communications.</span></span></div><div style="margin:.0px;padding:.0px;border:.0px;outline:.0px;caret-color:#000000;color:#000000;font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;background-color:#ffffff;text-decoration:none;clear:both;"><br ></div></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Kind regards,</span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;"><br ></span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Pam</span></div><blockquote style="margin-right:0;margin-top:0;margin-bottom:0;"><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">------------------------------------------------------------------</span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Sender:Marie Pattullo <marie.pattullo@aim.be></span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Sent At:2019 <span class="spellcheck_typo">Apr</span>. 11 (<span class="spellcheck_typo">Thu</span>.) 19:33</span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Recipient:darcy.southwell@endurance.com <darcy.southwell@endurance.com>; "<span class="spellcheck_typo">Novoa</span>, Osvaldo" <onovoa@Antel.com.uy>; Martin Pablo <span class="spellcheck_typo">Silva</span> Valent <mpsilvavalent@gmail.com></span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Cc:council <council-bounces@gnso.icann.org>; council@gnso.icann.org <council@gnso.icann.org></span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Subject:Re: [council] Fellowships for ICANN65 Marrakech - Update</span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;"><br ></span></div>Hi all,<br ><br >The BC has a number of suggestions - see attached.<br ><br >Also, we know this is a list of criteria for the suitability of the applicants, but we think that there should be more clarity to help them understand to which part of the GNSO they would actually be best suited before they apply. We've all seen cases of misunderstanding in self-designation; we need a short explanation of how the designation correlates to the SO/C. For example, the word "business" doesn't always mean "the BC is your appropriate home": we've seen applicants claiming the "business" badge but they were with a ccTLD, a small registrar, even the trade department of a government... On the other hand, small business from the global south would be a great asset to our ecosystem.<br ><br >Thanks<br ><br >Marie<br ><br >-----Original Message-----<br >From: council <council-bounces@gnso.icann.org> On Behalf Of <span class="spellcheck_typo">Darcy</span> Southwell<br >Sent: Wednesday, April 10, 2019 5:59 PM<br >To: '<span class="spellcheck_typo">Novoa</span>, Osvaldo' <onovoa@Antel.com.uy>; 'Martin Pablo <span class="spellcheck_typo">Silva</span> Valent' <mpsilvavalent@gmail.com><br >Cc: council@gnso.icann.org; 'council' <council-bounces@gnso.icann.org><br >Subject: Re: [council] Fellowships for ICANN65 Marrakech - Update<br ><br >I agree with the comments about the English language requirement. That's unreasonable and is a discouraging component.<br ><br >Regarding the bullet about communication, what if we considered this:<br >"Ability and willingness to communicate orally and in writing in a manner consistent with ICANN's Expected Standards of Behavior." And then we could delete the next bullet about "willingness to adhere...."<br ><br >I have to put some additional thought into Ayden's comments about the new purpose of the Fellowship program, but my immediate reaction is that the new purpose doesn't warrant a change in expectations. Whatever program criteria is established, I feel it should serve two purposes: 1) allowing the selection team to identify the most appropriate candidates for participation, and 2) measuring the effectiveness of the program.<br ><br >-----Original Message-----<br >From: council <council-bounces@gnso.icann.org> On Behalf Of <span class="spellcheck_typo">Novoa</span>, Osvaldo<br >Sent: Wednesday, April 10, 2019 7:06 AM<br >To: Martin Pablo <span class="spellcheck_typo">Silva</span> Valent <mpsilvavalent@gmail.com><br >Cc: council <council-bounces@gnso.icann.org>; council@gnso.icann.org<br >Subject: Re: [council] Fellowships for ICANN65 Marrakech - Update<br ><br >Me too.<br >Osvaldo <span class="spellcheck_typo">Novoa</span><br ><br >Enviado <span class="spellcheck_typo">desde</span> mi <span class="spellcheck_typo">iPhone</span><br ><br >El 10 <span class="spellcheck_typo">abr</span>. 2019, a la(s) 10:24, Martin Pablo <span class="spellcheck_typo">Silva</span> Valent <mpsilvavalent@gmail.com<mailto:mpsilvavalent@gmail.com>> escribió:<br ><br >I agree with <span class="spellcheck_typo">Philippe</span> point.<br ><br >Martin <span class="spellcheck_typo">Silva</span> Valent<br ><br >mpsilvavalent@gmail.com<mailto:mpsilvavalent@gmail.com><br ><br >Partner | <span class="spellcheck_typo">Silva</span>.legal<br >martin@<span class="spellcheck_typo">silva</span>.legal<mailto:martin@<span class="spellcheck_typo">silva</span>.legal><br ><br >Director | <span class="spellcheck_typo">Dat</span>.as<br >martin.silva@dat.as<mailto:martin.silva@dat.as><br ><br ><span class="spellcheck_typo">Skype</span> ID: mpsilvavalent<br >Tel: +5491164993943<br >Libertador 5990, Off. 406<br >Buenos Aires, Argentina.<br ><br ><span class="spellcheck_typo">Este</span> email, incluyendo adjuntos, podría <span class="spellcheck_typo">contener</span> información <span class="spellcheck_typo">confidencial</span> protegida <span class="spellcheck_typo">por</span> <span class="spellcheck_typo">ley</span> y es para uso exclusivo de su destinatario. Si Ud. no es el destinatario, se le advierte que cualquier uso, difusión, <span class="spellcheck_typo">copia</span> o retención de <span class="spellcheck_typo">este</span> email o su contenido está estrictamente prohibido. Si Ud.<br >recibió <span class="spellcheck_typo">este</span> email <span class="spellcheck_typo">por</span> error, <span class="spellcheck_typo">por</span> favor <span class="spellcheck_typo">avise</span> inmediatamente al remitente <span class="spellcheck_typo">por</span> teléfono o email y <span class="spellcheck_typo">borre</span> el <span class="spellcheck_typo">mismo</span> de su computadora. / This e-mail, including any attachments, may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by telephone or reply e-mail, and permanently delete this e-mail from your computer system.<br ><br >On <span class="spellcheck_typo">Apr</span> 10, 2019, at 4:52 AM,<br >philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com> wrote:<br ><br >Thanks Rafik. The point was not to call for a specific level, I agree, but to say that given the other criteria, this particular one is pointless IMO, and would suggest to delete it.<br ><br >In other words, if the applicant can demonstrate they "know the GNSO PDP", or is "able [.] to actively contribute to GNSO activity [.] via remote participation in conference calls or a group mailing list", asking whether they can speak, understand, or write in decent English is futile.<br ><br >It's really just a personal opinion and not a strong one, but it's worthwhile noting that within the ISPCP we already have a number of members who would intervene in a manner that could be misconstrued as "disrespectful" to a native speaker (to use the word of the document), and yet once you ignore the form and focus on substance, their inputs are invaluable to our community of <span class="spellcheck_typo">ISPs</span> because they're from part of the Internet ecosystem we sometimes have difficulty reaching out to.<br ><br >Regards,<br ><span class="spellcheck_typo">Philippe</span><br ><br >From: Rafik <span class="spellcheck_typo">Dammak</span> [mailto:rafik.dammak@gmail.com]<br >Sent: Wednesday, April 10, 2019 12:41 AM<br >To: FOUQUART <span class="spellcheck_typo">Philippe</span> TGI/OLN<br >Cc: Martin Pablo <span class="spellcheck_typo">Silva</span> Valent; <span class="spellcheck_typo">Arsene</span> Bajuma; council; council@gnso.icann.org<mailto:council@gnso.icann.org><br >Subject: Re: [council] Fellowships for ICANN65 Marrakech - Update<br ><br >Hi,<br ><br >I thought that the current language is neutral since it is not setting a specific threshold or condition (such having some score in TOEIC, TOFEL, IETLS etc) and leave that to applicants who can demonstrate that through their application which is in English.<br >can a different wording alleviate the concerns?<br ><br >Best,<br ><br >Rafik<br >Le <span class="spellcheck_typo">mer</span>. 10 <span class="spellcheck_typo">avr</span>. 2019 à 01:30,<br ><philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> a écrit<br >:<br >It counts obviously but not sure this condition is useful either, or that it brings anything to the list for that matter: can we reasonably expect people to have a "Knowledge of the GNSO policy development process [.]" without reasonable good language skills? Because for general speaking and listening skills, I would think B1 English level is good enough if that means anything to people.<br ><br >I'm not even sure it looks good for GNSO to say you have to speak good English to join the band;<br ><br >Otherwise the list looks good to me, maybe we could have something to the effect that those who may potentially be new constituency members in the future would be welcome. Just a thought.<br ><br >Regards,<br ><span class="spellcheck_typo">Philippe</span><br ><br >From: council<br >[mailto:council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org<br >>] On Behalf Of Martin Pablo <span class="spellcheck_typo">Silva</span> Valent<br >Sent: Tuesday, April 09, 2019 6:03 PM<br >To: <span class="spellcheck_typo">Arsene</span> Bajuma<br >Cc: council@gnso.icann.org<mailto:council@gnso.icann.org>; council<br >Subject: Re: [council] Fellowships for ICANN65 Marrakech - Update<br ><br >I agree, for several fellows in the past, the experience was a big intensive improvement in their English, so it is tricky to marginalize less fluent people only based on that. Fluently is usually acquired in experiences like this one. I would say they require some basic level to follow the debate, like they do currently, but not professional level. Remember a lot of their value is their relevance on their community back home, not only to work in <span class="spellcheck_typo">icann</span> matter but to take their acquired knowledge on their own IG work.<br ><br >Martin <span class="spellcheck_typo">Silva</span> Valent<br ><br >mpsilvavalent@gmail.com<mailto:mpsilvavalent@gmail.com><br ><br >Partner | <span class="spellcheck_typo">Silva</span>.legal<br >martin@<span class="spellcheck_typo">silva</span>.legal<mailto:martin@<span class="spellcheck_typo">silva</span>.legal><br >Director | <span class="spellcheck_typo">Dat</span>.as<br >martin.silva@dat.as<mailto:martin.silva@dat.as><br ><br ><span class="spellcheck_typo">Skype</span> ID: mpsilvavalent<br >Tel: +5491164993943<br >Libertador 5990, Off. 406<br >Buenos Aires, Argentina.<br ><br ><span class="spellcheck_typo">Este</span> email, incluyendo adjuntos, podría <span class="spellcheck_typo">contener</span> información <span class="spellcheck_typo">confidencial</span> protegida <span class="spellcheck_typo">por</span> <span class="spellcheck_typo">ley</span> y es para uso exclusivo de su destinatario. Si Ud. no es el destinatario, se le advierte que cualquier uso, difusión, <span class="spellcheck_typo">copia</span> o retención de <span class="spellcheck_typo">este</span> email o su contenido está estrictamente prohibido. Si Ud.<br >recibió <span class="spellcheck_typo">este</span> email <span class="spellcheck_typo">por</span> error, <span class="spellcheck_typo">por</span> favor <span class="spellcheck_typo">avise</span> inmediatamente al remitente <span class="spellcheck_typo">por</span> teléfono o email y <span class="spellcheck_typo">borre</span> el <span class="spellcheck_typo">mismo</span> de su computadora. / This e-mail, including any attachments, may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by telephone or reply e-mail, and permanently delete this e-mail from your computer system.<br ><br >On <span class="spellcheck_typo">Apr</span> 9, 2019, at 11:58 AM, Arsène Tungali <arsenebaguma@gmail.com<mailto:arsenebaguma@gmail.com>> wrote:<br ><br >Hi all,<br ><br >Thanks for this ongoing effort. I have read the following as part of the bullet points/<br ><br >"Ability to communicate in English orally and in writing, in a respectful and constructive manner"<br ><br >I would like to object to this statement. The ability to speak English SHOULD NOT, in my opinion, be a criterion when selecting a member of the fellowship program.<br ><br >Happy to hear what you all think here.<br ><br >Thanks,<br ><span class="spellcheck_typo">Arsene</span><br ><br >2019-04-09 12:15 UTC+02:00, Marie Pattullo<br ><marie.pattullo@aim.be<mailto:marie.pattullo@aim.be>>:<br >Merci!<br ><br >From: Rafik <span class="spellcheck_typo">Dammak</span> <rafik.dammak@gmail.com<mailto:rafik.dammak@gmail.com>><br >Sent: Tuesday, April 9, 2019 12:14 PM<br >To: Marie Pattullo <marie.pattullo@aim.be<mailto:marie.pattullo@aim.be>><br >Cc: Pam Little<br ><pam.little@alibaba-inc.com<mailto:pam.little@alibaba-inc.com>>; <span class="spellcheck_typo">Darcy</span> Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>;<br >council<br ><council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>>;<br >council@gnso.icann.org<mailto:council@gnso.icann.org><br >Subject: Re: [council] <span class="spellcheck_typo">Fwd</span>: Fellowships for ICANN65 Marrakech - Update<br ><br >Hi Marie,<br ><br >I think that is fine.<br ><br >Best,<br ><br >Rafik<br ><br >Le mar. 9 <span class="spellcheck_typo">avr</span>. 2019 à 17:25, Marie Pattullo <marie.pattullo@aim.be<mailto:marie.pattullo@aim.be><mailto:marie.pattullo@a<br >im.be>> a écrit :<br >I'm talking to the BC Rafik; hoping it's not too late for me to send comments in on Thursday?<br >Best<br >Marie<br ><br >From: council<br ><council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org><<span class="spellcheck_typo">mailt</span><br >o:council-bounces@gnso.icann.org>> On Behalf Of Pam Little<br >Sent: Tuesday, April 9, 2019 5:36 AM<br >To: <span class="spellcheck_typo">Darcy</span> Southwell<br ><darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com><mailto:<br >darcy.southwell@endurance.com>>;<br >council<br ><council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org><<span class="spellcheck_typo">mailt</span><br >o:council-bounces@gnso.icann.org>><br >Cc:<br >council@gnso.icann.org<mailto:council@gnso.icann.org><mailto:council@gnso.ic<br >ann.<span class="spellcheck_typo">org</span>><br >Subject: Re: [council] <span class="spellcheck_typo">Fwd</span>: Fellowships for ICANN65 Marrakech - Update<br ><br >Thank you for the reminder, Rafik<br ><br >I have updated the strawman list of criteria/desirable skills Heather has kindly put together. I have tried to incorporate Darcy's feedback but welcome further input/suggestions.<br ><br >Kind regards,<br ><br >Pam<br >------------------------------------------------------------------<br >Sender:Rafik <span class="spellcheck_typo">Dammak</span><br ><rafik.dammak@gmail.com<mailto:rafik.dammak@gmail.com><mailto:rafik.<span class="spellcheck_typo">dammak</span>@g<br >mail.com>><br >Sent At:2019 <span class="spellcheck_typo">Apr</span>. 9 (Tue.) 11:16<br >Recipient:<span class="spellcheck_typo">Darcy</span> Southwell<br ><darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com><mailto:<br >darcy.southwell@endurance.com>><br >Cc:council@gnso.icann.org<mailto:council@gnso.icann.org><mailto:Cc%<mailto:C<br >c%25>3Acouncil@gnso.icann.org<mailto:3Acouncil@gnso.icann.org>><br ><council@gnso.icann.org<mailto:council@gnso.icann.org><mailto:council@gnso.i<br ><span class="spellcheck_typo">cann</span>.<span class="spellcheck_typo">org</span>>><br >Subject:Re: [council] <span class="spellcheck_typo">Fwd</span>: Fellowships for ICANN65 Marrakech - Update<br ><br >Thanks <span class="spellcheck_typo">Darcy</span> for the feedback.<br >I would like to ask other councillors to share their input in order to update the list.<br ><br >Best Regards,<br ><br >Rafik<br ><br >Le mar. 2 <span class="spellcheck_typo">avr</span>. 2019 à 03:24, <span class="spellcheck_typo">Darcy</span> Southwell<br ><darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com><mailto:<br >darcy.southwell@endurance.com>> a écrit :<br >Thanks for sharing, Rafik.<br ><br >When I think about fellowship selection, I also think about how we measure success once a fellow has been selected and completed any level of participation. I think much of what is outlined is the strawman is valuable for selection criteria. When we refer to "awareness," we're really referring to knowledge, and we may want to establish definitions of knowledge levels. For example, consider this these:<br ><br ><br >. Familiar = becoming aware, first introduction<br ><br >. Basic = ability to talk about at a high level<br ><br >. Fluent = comfortable getting into detail and teaching others<br ><br >. Expert = subject matter expert, let me write a book on the<br >subject<br ><br >Working with defined levels of knowledge allows the Council to evaluate the effectiveness of the selection criteria and the engagement efforts that take place with the fellows to enable their growth and engagement in the community.<br ><br >Thanks,<br ><span class="spellcheck_typo">Darcy</span><br ><br ><br >From: council<br ><council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org><<span class="spellcheck_typo">mailt</span><br >o:council-bounces@gnso.icann.org>> On Behalf Of Rafik <span class="spellcheck_typo">Dammak</span><br >Sent: Sunday, March 31, 2019 10:22 PM<br >To: Council GNSO<br ><council@gnso.icann.org<mailto:council@gnso.icann.org><mailto:council@gnso.i<br ><span class="spellcheck_typo">cann</span>.<span class="spellcheck_typo">org</span>>><br >Subject: [council] <span class="spellcheck_typo">Fwd</span>: Fellowships for ICANN65 Marrakech - Update<br ><br >Hi all,<br ><br >I am sharing update from Heather regarding the fellowship selection committee and strawman document for GNSO specific skills expected from fellows, for council review and input.<br ><br >Best,<br ><br >Rafik<br >---------- Forwarded message ---------<br >De : Heather Forrest<br >Date: <span class="spellcheck_typo">mer</span>. 13 mars 2019 à 17:38<br >Subject: Re: Fellowships for ICANN65 Marrakech - Update<br >To:<br ><br >Dear Keith, Rafik, Pam,<br ><br >Now that the Council meeting of ICANN64 is behind you, I return to the request from the Fellowship Selection Committee for GNSO-specific target skills for ICANN Fellows in the ICANN66 selection round.<br ><br >For your post-ICANN64 action item list, attached is the strawman I volunteered to prepare. If Council can finalise its list of criteria at or before its April meeting, these should be able to be applied to the ICANN66 selection round.<br ><br >Best wishes,<br ><br >Heather<br ><br ><br >_______________________________________________<br >council mailing list<br >council@gnso.icann.org<mailto:council@gnso.icann.org><mailto:council@gnso.ic<br >ann.<span class="spellcheck_typo">org</span>><br >https://mm.icann.org/mailman/listinfo/council<br ><br ><br >--<br >------------------------<br >**Arsène Tungali* <http://about.me/ArseneTungali>* Co-Founder & Executive Director, *<span class="spellcheck_typo">Rudi</span> international <http://www.rudiinternational.org<http://www.rudiinternational.org/>>*,<br >CEO,* Smart Services <span class="spellcheck_typo">Sarl</span> <https://www.smart-kitoko.com/>*,<br >Tel: +243 993810967 (DRC)<br >GPG: 523644A0<br ><br >2015 Mandela Washington Fellow<br ><<br >http://tungali.blogspot.com/2015/06/selected-for-2015-<span class="spellcheck_typo">mandela</span>-washington.<span class="spellcheck_typo">htm</span><br >l><br ><br >(YALI) - ICANN GNSO Council Member<br ><https://gnso.icann.org/en/about/gnso-council.<span class="spellcheck_typo">htm</span>> Member. UN IGF MAG <https://www.un.org/press/en/2018/pi2247.doc.htm> Member _______________________________________________<br >council mailing list<br >council@gnso.icann.org<mailto:council@gnso.icann.org><br >https://mm.icann.org/mailman/listinfo/council<br ><br ><br >____________________________________________________________________________<br >_____________________________________________<br ><br ><br ><br >Ce message et <span class="spellcheck_typo">ses</span> pieces <span class="spellcheck_typo">jointes</span> peuvent contenir des <span class="spellcheck_typo">informations</span> confidentielles ou privilegiees et ne doivent <span class="spellcheck_typo">donc</span><br ><br >pas <span class="spellcheck_typo">etre</span> diffuses, <span class="spellcheck_typo">exploites</span> ou copies sans <span class="spellcheck_typo">autorisation</span>. Si <span class="spellcheck_typo">vous</span> <span class="spellcheck_typo">avez</span> <span class="spellcheck_typo">recu</span> ce message par <span class="spellcheck_typo">erreur</span>, veuillez le signaler<br ><br >a l'expediteur et le detruire ainsi que <span class="spellcheck_typo">les</span> pieces <span class="spellcheck_typo">jointes</span>. Les messages electroniques etant susceptibles d'alteration,<br ><br >Orange decline <span class="spellcheck_typo">toute</span> responsabilite si ce message a <span class="spellcheck_typo">ete</span> altere, <span class="spellcheck_typo">deforme</span> ou <span class="spellcheck_typo">falsifie</span>. Merci.<br ><br ><br ><br >This message and its attachments may contain confidential or privileged information that may be protected by law;<br ><br >they should not be distributed, used or copied without authorisation.<br ><br >If you have received this email in error, please notify the sender and delete this message and its attachments.<br ><br >As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<br ><br >Thank you.<br ><br >_______________________________________________<br >council mailing list<br >council@gnso.icann.org<mailto:council@gnso.icann.org><br >https://mm.icann.org/mailman/listinfo/council<br ><br >____________________________________________________________________________<br >_____________________________________________<br ><br >Ce message et <span class="spellcheck_typo">ses</span> pieces <span class="spellcheck_typo">jointes</span> peuvent contenir des <span class="spellcheck_typo">informations</span> confidentielles ou privilegiees et ne doivent <span class="spellcheck_typo">donc</span> pas <span class="spellcheck_typo">etre</span> diffuses, <span class="spellcheck_typo">exploites</span> ou copies sans <span class="spellcheck_typo">autorisation</span>. Si <span class="spellcheck_typo">vous</span> <span class="spellcheck_typo">avez</span> <span class="spellcheck_typo">recu</span> ce message par <span class="spellcheck_typo">erreur</span>, veuillez le signaler a l'expediteur et le detruire ainsi que <span class="spellcheck_typo">les</span> pieces <span class="spellcheck_typo">jointes</span>. Les messages electroniques etant susceptibles d'alteration, Orange decline <span class="spellcheck_typo">toute</span> responsabilite si ce message a <span class="spellcheck_typo">ete</span> altere, <span class="spellcheck_typo">deforme</span> ou <span class="spellcheck_typo">falsifie</span>. Merci.<br ><br >This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.<br >If you have received this email in error, please notify the sender and delete this message and its attachments.<br >As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<br >Thank you.<br ><br ><br >_______________________________________________<br >council mailing list<br >council@gnso.icann.org<mailto:council@gnso.icann.org><br >https://mm.icann.org/mailman/listinfo/council<br ><br >________________________________<br ><br >El <span class="spellcheck_typo">presente</span> <span class="spellcheck_typo">correo</span> y cualquier <span class="spellcheck_typo">posible</span> archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que <span class="spellcheck_typo">puede</span> <span class="spellcheck_typo">ser</span> <span class="spellcheck_typo">confidencial</span>. Si Ud. no es el destinatario <span class="spellcheck_typo">correcto</span> <span class="spellcheck_typo">por</span> favor notifique al remitente respondiendo anexando <span class="spellcheck_typo">este</span> mensaje y <span class="spellcheck_typo">elimine</span> inmediatamente el e-mail y los <span class="spellcheck_typo">posibles</span> archivos adjuntos al <span class="spellcheck_typo">mismo</span> de su sistema. Está <span class="spellcheck_typo">prohibida</span> cualquier utilización, difusión o <span class="spellcheck_typo">copia</span> de <span class="spellcheck_typo">este</span> e-mail <span class="spellcheck_typo">por</span> cualquier persona o entidad que no <span class="spellcheck_typo">sean</span> las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con <span class="spellcheck_typo">respecto</span> a cualquier comunicación que <span class="spellcheck_typo">haya</span> <span class="spellcheck_typo">sido</span> emitida incumpliendo nuestra Política de Seguridad de la Información<br ><br ><br >This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.<br >_______________________________________________<br >council mailing list<br >council@gnso.icann.org<br >https://mm.icann.org/mailman/listinfo/council<br ><br >_______________________________________________<br >council mailing list<br >council@gnso.icann.org<br >https://mm.icann.org/mailman/listinfo/council<br ><br >_______________________________________________<br >council mailing list<br >council@gnso.icann.org<br >https://mm.icann.org/mailman/listinfo/council<br ></blockquote><div ><br ></div></div>