ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] GNSO Council meetings time rotation tool

  • To: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Subject: Re: [council] GNSO Council meetings time rotation tool
  • From: Erika Mann <erika@xxxxxxxxxxxxx>
  • Date: Tue, 6 Dec 2016 19:42:57 +0100
  • Cc: Nathalie Peregrine <nathalie.peregrine@xxxxxxxxx>, "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>, Marika Konings <marika.konings@xxxxxxxxx>, Mary Wong <mary.wong@xxxxxxxxx>, Julie Hedlund <julie.hedlund@xxxxxxxxx>, "gnso-secs@xxxxxxxxx" <gnso-secs@xxxxxxxxx>
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=erikamann-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8qnyui6NO8tirq4d4gH/rlJSVbvAJitVSVOnbOX/yUA=; b=llXhCiG0iKAq71Xk1KnuJOk0+X/mg9cOpRAzk7oI/rl9vuVsguhRsPo/wXy2pk5kCW FMlxKxMpwaGKUXKIFu46PHXksLe72QS57+nzGp+QAP0mOEdOTO0bl3S5cSkuiKlMth5X 9IoLbfFmacUjvFYahMKLRdbOkg6AZgBrnYvuGx91o/zWjxm6VWRGvbfSPosohOkaFAoY r5k4+Aw9AGs4E6zMY+lHmniL5NadvQiKKi9FPkD1MgbbYPXgTBSCfMxZI3N2UgDnMC+h Uqc90UouTV+hNE7SYxM6299PHF3dOsQZuDVb5zrdFfVu/5jTvAOkyzbNDSMX/pi3Ae8+ mDBw==
  • In-reply-to: <C53886EF-3B92-423A-9CB7-759E46EB3D26@godaddy.com>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <C53886EF-3B92-423A-9CB7-759E46EB3D26@godaddy.com>
  • Sender: owner-council@xxxxxxxxxxxxxx

I like your proposal, James. In my case it doesn't really matter which
timezone we select, I move around too much.
Thanks,
Erika

On Tue, Dec 6, 2016 at 3:04 PM, James M. Bladel <jbladel@xxxxxxxxxxx> wrote:

> Thank you, Nathalie.
>
>
>
> Colleagues, as you can see from this tool, the “span” of time zones, along
> with the distribution of Councilors within those time zones, hasn’t changed
> much since last year. For example, we exchanged Mason for Darcy (Yay
> Portland!), Volker for Michele, David for Rafik, etc.
>
>
>
> It was also this time last year when we shifted the rotation from 3
> meeting timeslots, down to 2, after having determined that more time slots
> created significant complexities with little benefit.  So if there aren’t
> any objections, I propose that we keep the current 2 time slots, and adopt
> the meeting calendar that was previously circulated.
>
> Thanks –
>
> J.
>
>
>
> *From: *<owner-council@xxxxxxxxxxxxxx> on behalf of Nathalie Peregrine <
> nathalie.peregrine@xxxxxxxxx>
> *Date: *Monday, December 5, 2016 at 17:32
> *To: *GNSO Council List <council@xxxxxxxxxxxxxx>
> *Cc: *Marika Konings <marika.konings@xxxxxxxxx>, Mary Wong <
> mary.wong@xxxxxxxxx>, Julie Hedlund <julie.hedlund@xxxxxxxxx>, "'
> gnso-secs@xxxxxxxxx'" <gnso-secs@xxxxxxxxx>
> *Subject: *[council] GNSO Council meetings time rotation tool
>
>
>
> Dear all,
>
>
>
> From the Council meeting on the 1st December 2016,  an action item for
> staff was to use a time rotation tool to visualise how the current time
> rotation of Council meetings fits in with Council member locations.
>
>
>
> The following Google doc covers the 24hr clock with all Council member
> timezones (row 3) and how many members per said timezone (row 4). Our
> current times of 12:00 UTC and 21:00 UTC are highlighted in column R.
>
>
>
> https://docs.google.com/spreadsheets/d/1vY7O_8jOzHc_
> UZ3AyKryUPbAuGgeNlsFslA4IsFp0iM/edit?usp=sharing
>
>
>
> Kind regards,
>
>
>
> Nathalie
>
> --
>
>
>
> Nathalie Peregrine
>
> Specialist, SOAC Support (GNSO)
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> Email: nathalie.peregrine@xxxxxxxxx
> <http://nathalie.peregrine@xxxxxxxxx%20>
>
> Skype: nathalie.peregrine.icann
>
>
>
> Find out more about the GNSO by taking our interactive courses
> <http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages
> <http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers>
>
>
>


<<< Chronological Index >>>    <<< Thread Index >>>