[CCWG-ACCT] Copenhagen F2F

[lists at christopherwilkinson.eu]

But we were not told, until after travel had been booked   …  :-((

Too late now. (And too busy today to follow remotely.)

CW

On 09 Mar 2017, at 22:22, Xavier J. Calvez <xavier.calvez at icann.org> wrote:

> Paul,
> Be aware that the scheduling of the CCWG meeting plenary was made on Friday's preceding ICANN meetings at the request of the CCWG in order to avoid conflicts with other SO/AC scheduled meetings.
> 
> Thank you. 
> Best,
> 
> Xavier
> 
> On Mar 9, 2017, at 20:02, Paul McGrady <policy at paulmcgrady.com> wrote:
> 
>> Dear All,
>>  
>> Unfortunately, I will not be able to make this face to face meeting which is held outside of the normal ICANN schedule.  I would like for the record to reflect that ICANN does itself no favors by moving this important work to the margins of the meeting instead of holding this during the core of the meeting schedule where more people could attend and contribute.
>>  
>> Kind regards,
>> Paul McGrady
>>  
>>  
>>  
>> From: accountability-cross-community-bounces at icann.org [mailto:accountability-cross-community-bounces at icann.org] On Behalf Of Daniel Nanghaka
>> Sent: Thursday, March 09, 2017 2:06 AM
>> To: Johan Helsingius <julf at julf.com>
>> Cc: accountability-cross-community at icann.org
>> Subject: Re: [CCWG-ACCT] Copenhagen F2F
>>  
>> Dear All, 
>>  
>> Please accept my kind appologies, I will not be in Copenhagen for the F2F meeting but will be following remotely. 
>>  
>> Daniel 
>> ᐧ
>> 
>> Daniel Nanghaka 
>> ALAC Sub-Committee on Outreach and Engagement – Co-chair from AFRALO
>> ISOC Uganda Chapter 
>> Tel: +256 772 898298
>>  
>> On 9 March 2017 at 10:46, Johan Helsingius <julf at julf.com> wrote:
>> Please accept my apologies for not attending the F2F in Copenhagen. Due
>> to ICANN travel policy I won't be arriving in Copenhagen until Friday
>> evening.
>> 
>> I still haven't found an answer to the question "Who, and by what
>> process, determines the Travel Policy?". I do have confirmation that
>> at least parts of it isn't published - not very good in terms of
>> transparency and accountability.
>> 
>>         Julf
>> 
>> _______________________________________________
>> Accountability-Cross-Community mailing list
>> Accountability-Cross-Community at icann.org
>> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>>  
>> _______________________________________________
>> Accountability-Cross-Community mailing list
>> Accountability-Cross-Community at icann.org
>> https://mm.icann.org/mailman/listinfo/accountability-cross-community
> _______________________________________________
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
> https://mm.icann.org/mailman/listinfo/accountability-cross-community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20170310/586ed3c1/attachment-0001.html>