[Chapter-delegates] ISOC Meetings @ ICANN Buenos Aires

[Glenn McKnight]

hi
I agree two meetings has merit and the first meeting can focus on social
networking and the Isoc hq updates while the second one can be issues and
concerns for the chapters

I think the efforts of staff was well intended but as Evan stated he didnt
have a take away

glenn

On Wednesday, October 23, 2013, Evan Leibovitch wrote:

> Hello all,
>
> I realize that IGF Bali is still on, but I would like to raise an issue
> that has been bothering me, in regards to the ISOC meetings at ICANN
> events. I am hoping that by raising this issue now we may be able to
> influence what happens at the ISOC meeting in Argentina next month.
>
> Here are my own views:
>
> I think it was a very bad idea to go from two meetings (Sunday and
> Tuesday) just to one. I am aware that not everyone can make the Tuesday
> meeting, so I am suggesting that the Sunday meeting be a formal and
> policy-based event, while a Tuesday event should be more for socializing
> and enabling Chapter delegates to learn from each other on local issues
> such as governance, communications and outreach.
>
> (Yes, I know that Tuesday is ICANN music night. But that usually starts at
> 21:00 and runs very late, ISOC meetings really would not conflict.)
>
> Splitting the two functions enables the main Sunday meeting to be wholly
> informed by ISOC policy staff of critical issues, the policy work that is
> being done, and to engage chapters on local initiatives and ideas that
> could be useful globally.
>
> Anyway, that is my opinion, to go back to two meetings. The last one in
> Durban was near useless for me in terms of EITHER informing me about ISOC
> programs/priorities OR sharing knowledge with and meeting other chapters.
>
> Thanks.
>
> --
> Evan Leibovitch
> ISOC Canada Chapter
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://elists.isoc.org/mailman/private/chapter-delegates/attachments/20131023/53435ef6/attachment.htm>