<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] MOTION - To extend the term of the current GNSO Liaison to the GAC
- To: WUKnoben <wolf-ulrich.knoben@xxxxxxxxxxx>
- Subject: Re: [council] MOTION - To extend the term of the current GNSO Liaison to the GAC
- From: "Edward Morris" <egmorris1@xxxxxxxxx>
- Date: Tue, 21 Jun 2016 12:57:54 +0100
- Cc: Paul McGrady <policy@xxxxxxxxxxxxxxx>, "James M. Bladel" <jbladel@xxxxxxxxxxx>, GNSO Council List <council@xxxxxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toast.net; s=smartermail; h=from:cc:in-reply-to:to:references:date:message-id:subject :mime-version:content-transfer-encoding:content-type; bh=KxkGf2xrMQXC9ix7oz/qrE4qGQu9DfIVwlOIZUXPYks=; b=tozuofSR3BJkSnJmqjiqnCrbPQNb6+foY7JkGLAObpgs9d10vlKx1eGpyPKG9nEZ2 AG0bbAW77UPQeBRNj3T/S7ulpcq2FJwmfergIkCDD96+Vn++Jav64oZUVGgMJr9Dg P1lBNDK3zQg1F7TmFhYmJ6+n9ZKgsh/Kgr+Qu03K0=
- In-reply-to: <0E8A13881A6B4301BF7C531B42382858@WUKPC>
- List-id: council@xxxxxxxxxxxxxx
- References: <D38DB801.C6FFA%jbladel@godaddy.com> <00d501d1cb3b$af0d04b0$0d270e10$@paulmcgrady.com> <199E9C8D-0979-4BDC-A156-DD19F0A85BDB@godaddy.com> <EF5FCC7E-33AA-4B6F-9D1F-57C143F3A0FF@paulmcgrady.com> <0E8A13881A6B4301BF7C531B42382858@WUKPC>
- Sender: owner-council@xxxxxxxxxxxxxx
+1
Sent from my iPhone
> On 21 Jun 2016, at 12:40, WUKnoben <wolf-ulrich.knoben@xxxxxxxxxxx> wrote:
>
>
> Hi Paul,
>
> I'm with you that WHEREAS 2 as originally suggested should be improved.
> However expressing or describing hopes in a motion seems to bring in some
> subjectivity which is difficult to assess. So I wonder whether this could be
> acceptable:
>
> 2. The subsequent call for volunteers resulted in the decision to extend
> the selection process.
>
>
> Best regards
>
> Wolf-Ulrich
>
> -----Ursprüngliche Nachricht----- From: Paul McGrady
> Sent: Tuesday, June 21, 2016 4:28 AM
> To: James M. Bladel
> Cc: GNSO Council List
> Subject: Re: [council] MOTION - To extend the term of the current GNSO
> Liaison to the GAC
>
>
> Thanks James. How about we strike it as written, and just say "whereas the
> volume of responses to the request for applications for the role was less
> robust than hoped for."
>
> Best,
> Paul
>
>
> Sent from my iPhone
>
>> On Jun 20, 2016, at 8:50 PM, James M. Bladel <jbladel@xxxxxxxxxxx> wrote:
>>
>>
>> Hi Paul -
>>
>> You are correct, "incomplete" is probably not the best word. The intention
>> was to leave the door open for the lone application received to be
>> resubmitted.
>>
>> I'm fine if we strike "incomplete", or even the entirety of WHEREAS 2.
>>
>> Thank you,
>>
>> J.
>> ____________
>> James Bladel
>>
>>
>>> On Jun 20, 2016, at 16:35, Paul McGrady <policy@xxxxxxxxxxxxxxx> wrote:
>>>
>>> Hi James,
>>>
>>> I am Ok with this, except I don't understand WHEREAS 2. What element of the
>>> application wasn't completed? I thought from all that back and forth that
>>> the reason to not move forward with the one candidate we had was that there
>>> was only 1 applicant and, in the opinion of some, he didn't fit the bill.
>>> This motion reads as if there was an application form that didn't have all
>>> the checkmarks checked. Can you please elaborate on what is meant by
>>> "incomplete"? Thanks in advance.
>>>
>>> Best,
>>> Paul
>>>
>>>
>>> -----Original Message-----
>>> From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On
>>> Behalf Of James M. Bladel
>>> Sent: Monday, June 20, 2016 3:11 PM
>>> To: GNSO Council List
>>> Subject: [council] MOTION - To extend the term of the current GNSO Liaison
>>> to the GAC
>>>
>>> Councilors -
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|