[council] Elections

[Stéphane Van Gelder]

Councillors,

We are going to have to start our election process soon and I would like to determine the Council's preference for the 2 scenarios Glen and I floated to you a while back.

As a reminder:

Chair Nomination Process (Two options)

1.    Allow for voting in Dakar

Start nominations Wednesday  28 September until Wednesday 12 October  ( 2 weeks)

	Per the GNSO Operating Procedures referenced above (Section 2.2.b): “Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate.” To allow for the possibility of a timely Council election process in Dakar, each house is asked to submit its nominee for Council chair for the term beginning at the end of the 2011 ICANN annual meeting not later than 12 October 2011.

				Nominees shall submit a candidacy statement in writing to the GNSO Secretariat (gnso.secretariat at gnso.icann.org) as soon as possible after they have been selected 					by their house and not later than 22:00 UTC on 14, October 2011.

2.   Electronic ballot voting – Before Dakar meeting

		Start nominations Wednesday  7 September until Wednesday 21 September  ( 2 weeks)

		Per the GNSO Operating Procedures referenced above (Section 2.2.b): “Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is 			responsible for determining how to nominate its candidate.” To allow for the possibility of a timely Council election process in Dakar, each house is asked to submit its 			nominee for Council chair for the term beginning at the end of the 2011 ICANN annual meeting not later than Wednesday, 21 September 2011.


It was my understanding that scenario 1 had the Council's preference and I plan to ask Glen to implement that one.

If there are objections, please voice them quickly.

Thanks,

Stéphane



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20110825/c63e26c3/attachment.html>