[proposed comment] Community Travel Support Guidelines
Stephanie Perrin
stephanie.perrin at MAIL.UTORONTO.CA
Sun Jul 1 13:49:13 EEST 2018
while I agree with Ayden that the comments about visa problems and site
choice will not likely appear in the summary, we have to consider the
other benefits of including a short statement (with facts and
illustrative examples if possible). More people read comments than
letters I think, so the oftener we deliver our message the better. I
don't think this is that much out of scope, as long as we keep it tight
as Caleb suggests, I think we should go for it.
Stephanie Perrin
On 2018-07-01 14:23, Ayden Férdeline wrote:
> Thanks for the edits, Caleb-
>
> I will pass the suggestion on to the Policy Committee for its
> consideration, though I do think it is better to write a letter on
> this particular issue, as it allows us to address it to the correct
> recipient. When ICANN org analyses the comments received on this
> issue, they fill in their template around the questions they have
> asked, and statements that do not relate to their specific questions
> are not typically included.
>
> Best wishes,
>
> Ayden
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On 1 July 2018 8:11 PM, caleb olumuyiwa <muyiwacaleb at gmail.com> wrote:
>
>> Hello Ayden,
>>
>> How about "The Elevator Pitch" idea as taught by Jim Trengrove at
>> the last NCUC public comment course. It simply means that we are to
>> use every available opportunity to communicate well and pitch your
>> ideas as we might never have such opportunities again.
>>
>> I still think there is an open opportunity for us to give our
>> feedback regarding the visa services.
>>
>> Don't visa problem is a travel related issues. While i have made
>> some observations and comments on the document you might want to
>> revert as they remain suggestions.
>>
>> Regards
>>
>> Caleb
>>
>> On Sun, Jul 1, 2018 at 6:34 PM Ayden Férdeline <icann at ferdeline.com
>> <mailto:icann at ferdeline.com>> wrote:
>>
>> Hi,
>>
>> I’m not sure what was covered in the comment writing course
>> earlier this year, but in my opinion an effective comment is one
>> which addresses the questions being asked. I do not think it is
>> appropriate to include issues that are not a part of the
>> proposed guidelines which we are being asked to comment on.
>>
>> If there are issues that fall outside the scope of a public
>> comment proceeding, I would suggest these can be addressed
>> separately by writing a letter to ICANN org.
>>
>> Just my opinion, of course,
>>
>> Ayden
>>
>> Sent from ProtonMail Mobile
>>
>>
>> On Sun, Jul 1, 2018 at 19:17, Bruna Martins dos Santos
>> <bruna.mrtns at GMAIL.COM <mailto:bruna.mrtns at GMAIL.COM>> wrote:
>>> Hey Ayden,
>>>
>>> While I agree that venue selection does not fall perfectly in
>>> this comment's scope, I think there's space for us to touch upon
>>> our feedback regarding the visa services ICANN has been offering
>>> lately. Newland Chase staff at times is unable to offer any
>>> input in the visa processes within the timeframe or even directs
>>> us to governments websites - what is the point of ICANN org
>>> hiring a company to bridge community travellers and embassies
>>> with regards to visa processes if the company will not do any
>>> facilitation, whatsoever.
>>>
>>> Maybe there's space to provide feedback on this sense ? That the
>>> company hired to help community with visas is often unable to
>>> provide the necessary information and do the mediation in the
>>> available time.
>>>
>>> Either way, thanks for the comment you guys!
>>>
>>> Cheers,
>>> Bruna
>>>
>>> 2018-07-01 14:02 GMT-03:00 Ayden Férdeline <icann at ferdeline.com
>>> <mailto:icann at ferdeline.com>>:
>>>
>>> Hi,
>>>
>>> The consultation is narrow in scope and in our comment we
>>> should only address those issues which fall within the
>>> purview of the travel support guidelines (this does not
>>> include the choice of meeting location).
>>>
>>> Best,
>>>
>>> Ayden
>>>
>>> Sent from ProtonMail Mobile
>>>
>>>
>>> On Sun, Jul 1, 2018 at 18:51, dorothy g
>>> <dgdorothydg at GMAIL.COM <mailto:dgdorothydg at GMAIL.COM>> wrote:
>>>> I have been through the document. I feel we can reduce the
>>>> number of words. I also feel it would be useful to start
>>>> with some principles. e.g effective participation in
>>>> meeting; avoiding unnecessary stress etc. We should call
>>>> for consistency in administrative procedures while
>>>> acknowledging special circumstances linked to developing
>>>> countries.
>>>>
>>>> Could we not insert some explicit language on the visa
>>>> issue we were recently discussing? Something that links it
>>>> to the choice of host?
>>>> best
>>>>
>>>> On Sun, Jul 1, 2018 at 3:47 PM, Arsène Tungali
>>>> <arsenebaguma at gmail.com <mailto:arsenebaguma at gmail.com>>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Thanks for drafting this comment, Ayden. I have read it
>>>> and i am glad
>>>> it covers many of the ocncerns i too have on the travel
>>>> guidelines. I
>>>> made one or two comments though.
>>>>
>>>> I hope this cna be approved soon and be sent within time.
>>>>
>>>> Regards,
>>>> Arsene
>>>>
>>>> 2018-07-01 17:07 UTC+02:00, Ayden Férdeline
>>>> <icann at ferdeline.com <mailto:icann at ferdeline.com>>:
>>>> > Dear all,
>>>> >
>>>> > ICANN org is currently requesting feedback on its
>>>> proposed updates to the
>>>> > Community Travel Support Guidelines. These guidelines
>>>> clarify the
>>>> > responsibilities of supported travellers and the duty
>>>> of care that ICANN org
>>>> > has to us. [The comment documents are
>>>> >
>>>> here.](https://www.icann.org/public-comments/travel-support-guidelines-2018-05-30-en)
>>>>
>>>> >
>>>> > I have prepared a response on behalf of the NCSG. You
>>>> can find it here:
>>>> >
>>>> https://docs.google.com/document/d/1FEWgze1lVbMlB5if0EnfZE2BxGreHoQ6SKaj6ya7sZY/edit?usp=sharing
>>>> >
>>>> > Please consider reviewing the proposed comment and
>>>> sharing feedback either
>>>> > in the Google Doc itself or on this mailing list. The
>>>> comment window closes
>>>> > on 16 July, so please provide your inputs before 12
>>>> July so that the NCSG
>>>> > Policy Committee has time to review them and to
>>>> finalise the text. We will
>>>> > share the final text on this list prior to submission.
>>>> >
>>>> > Best wishes,
>>>> >
>>>> > Ayden Férdeline
>>>>
>>>>
>>>> --
>>>> ------------------------
>>>> **Arsène Tungali* <http://about.me/ArseneTungali >*
>>>> Co-Founder & Executive Director, *Rudi international
>>>> < http://www.rudiinternational.org>*,
>>>> CEO,* Smart Services Sarl
>>>> <https://www.smart-kitoko.com/ >*, *Mabingwa Forum
>>>> < http://www.mabingwa-forum.com >*
>>>> Tel: +243 993810967
>>>> GPG: 523644A0
>>>> *Goma, Democratic Republic of Congo*
>>>>
>>>> 2015 Mandela Washington Felllow
>>>> <
>>>> http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.html>
>>>>
>>>> (YALI) - ISOC Ambassador (IGF Brazil
>>>> <
>>>> http://www.internetsociety.org/what-we-do/education-and-leadership-programmes/next-generation-leaders/igf-ambassadors-programme/Past-Ambassadors>
>>>>
>>>> & Mexico
>>>> <
>>>> http://www.internetsociety.org/what-we-do/education-and-leadership-programmes/next-generation-leaders/Current-Ambassadors>)
>>>>
>>>> - AFRISIG 2016
>>>> <http://afrisig.org/afrisig-2016/class-of-2016/> - Blogger
>>>> < http://tungali.blogspot.com> - ICANN's GNSO Council
>>>> < https://gnso.icann.org/en/about/gnso-council.htm>
>>>> Member. AFRINIC Fellow (
>>>> Mauritius
>>>> <
>>>> http://www.afrinic.net/en/library/news/1907-afrinic-25-fellowship-winners>)*
>>>>
>>>> - *IGFSA Member <http://www.igfsa.org/> - Internet
>>>> Governance - Internet
>>>> Freedom.
>>>>
>>>> Check the *2016 State of Internet Freedom in DRC*
>>>> report (English
>>>> < http://cipesa.org/?wpfb_dl=234 >) and (French
>>>> < http://cipesa.org/?wpfb_dl=242 >)
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> */Bruna Martins dos Santos /*
>>>
>>> Skype ID: bruna.martinsantos
>>> @boomartins
>>
>>
>>
>> --
>> *Ogundele Olumuyiwa Caleb*
>> /*muyiwacaleb at gmail.com <mailto:muyiwacaleb at gmail.com>*/
>> /*234 - 8077377378*/
>> /*234 - 07030777969*/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20180701/d7753956/attachment.htm>
More information about the Ncsg-discuss
mailing list