<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] FW: GNSO Council Update
- To: <council@xxxxxxxxxxxxxx>
- Subject: [council] FW: GNSO Council Update
- From: "Jonathan Robinson" <jrobinson@xxxxxxxxxxxx>
- Date: Fri, 18 Oct 2013 06:39:07 +0100
- Importance: High
- In-reply-to:
- List-id: council@xxxxxxxxxxxxxx
- Organization: Afilias
- References:
- Reply-to: <jrobinson@xxxxxxxxxxxx>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: Ac7LxB7MiOii+9RxQx+qmgJ3l+RJBgAAA2/A
All,
Please see below for an update sent out today to SG & Constituency chairs.
Thanks,
Jonathan
From: Jonathan Robinson [mailto:jonathan.robinson@xxxxxxxxxxx]
Sent: 18 October 2013 06:38
To: 'kdrazek@xxxxxxxxxxxx'; Michele Neylon :: Blacknight
(michele@xxxxxxxxxxxxxx) (michele@xxxxxxxxxxxxxx); 'Elisa Cooper'; 'Kristina
Rosette'; 'tony holmes'; 'Robin Gross'; 'William Drake'; 'Marie-Laure
Lemineur'
Cc: 'Glen de Saint Géry'; 'gnso-secs@xxxxxxxxx'; MASON COLE
(mcole@xxxxxxxxxx); 'WUKnoben'
Subject: GNSO Council Update
Importance: High
Dear Colleagues,
We are now inevitably starting to turn our attention towards the countdown
to the ICANN annual meeting in Buenos Aires, so it seems timely to provide
you with an update containing a few points relating to the work and running
of the GNSO Council.
The GNSO weekend working sessions are well established by now. We have a
full agenda emerging, including covering much of the policy work being
undertaken within the GNSO, as well as interaction with senior staff, the
ICANN Board and the GAC. Whilst the weekend sessions provide an excellent
opportunity for the Council to become well-briefed and work together, they
are clearly much more than GNSO Council sessions. They are an opportunity
for interaction within the whole GNSO and so, other commitments and
logistics permitting, I would like to take this opportunity to remind you of
the opportunity to participate and to invite and encourage you and
colleagues within your groups to do so.
For the first time I believe, we have a GNSO Council development meeting,
which will be held on Friday 22nd November between 10h00 & 18h00, followed
by a meal in the evening. The motivation for the meeting is to run an
induction and development workshop for the ?new? GNSO Council i.e. the
Council to be seated and in place from the Buenos Aires meeting onwards. We
plan to kick off on Friday 22nd at 10h00 with a first session to include
additional participation from the leadership of the groups represented on
the Council. So, we would very much like to have attendance from the Chair
(or Vice Chair or alternative if not available) of your SG or Constituency
as appropriate, in order to give additional perspective to that of your
Councillors for the first 60-90 minutes of the meeting. Accordingly, please
can you let Glen De Saint Gery (glen@xxxxxxxxx) which individual from your
leadership group (if not the chair) will be able to attend?
Regarding the leadership of the Council, you will be aware of the
requirement to elect a Council Chair for the forthcoming year as well as
select two Vice Chairs of the Council. My understanding is that both Vice
Chairs will be changing and we can look forward to confirmation of the new
Vice Chairs in due course. The Council confirmed a timetable for the
election of the Chair at its 10th October meeting. From my perspective, I
have enjoyed the not inconsiderable challenge of working as GNSO Council
Chair over the past year and am pleased to confirm to you that I am
available, if elected, to continue in the role for the year ahead. It?s
challenging and stimulating and there is plenty more work ahead!
If you have any questions or input relating to this note, or indeed any
aspect of the leadership and running of the Council, please do get in touch
with me. I am personally committed to a well-managed and effective GNSO
Council and am open to any feedback in how best to achieve that.
Best wishes,
Jonathan
Jonathan Robinson
Chair
ICANN GNSO Council
jonathan.robinson@xxxxxxxxxxx
Tel: +44 (0)20 7993 6103
skype: jonathan.m.r
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|