<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] Revised Motion on Drafting Team/Empowerment
- To: council@xxxxxxxxxxxxxx
- Subject: Re: [council] Revised Motion on Drafting Team/Empowerment
- From: avri doria <avri@xxxxxxx>
- Date: Wed, 29 Jun 2016 06:45:43 +0300
- In-reply-to: <019c01d1d180$22e8db80$68ba9280$@paulmcgrady.com>
- List-id: council@xxxxxxxxxxxxxx
- References: <019c01d1d180$22e8db80$68ba9280$@paulmcgrady.com>
- Sender: owner-council@xxxxxxxxxxxxxx
- User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
Hi,
In terms of the changes, I find it problematic that is still refers
solely to modifying bylaws. I think most of the work will involve
modifying operating procedures and thus the council should consider the
following ammendment:
> 2. The Drafting Team shall comprise those volunteers from the GNSO
> community which are identified by their Constituencies and Stakeholder
> Groups who express interests and can demonstrate reasonable knowledge
> of or experience with the process of revising the ICANN Bylaws.
> Constituencies and Stakeholder Groups are requested to identify
> volunteers by letter to the GNSCO Council Chair by 22 July 2016.
to
2. The Drafting Team shall comprise those volunteers from the GNSO
community which are identified by their Constituencies and Stakeholder
Groups who express interests and can demonstrate reasonable knowledge of
or experience with the process of revising the ICANN Bylaws _or GNSO
operating procedures_. Constituencies and Stakeholder Groups are
requested to identify volunteers by letter to the GNSCO Council Chair by
22 July 2016.
avri
On 29-Jun-16 00:00, Paul McGrady wrote:
>
> Hi All,
>
>
>
> Attached is a revised version (with track changes) of my motion which
> we discussed on Monday. Thank you all for your input into improving
> this. I look forward to discussing the revised version with you all soon.
>
>
>
> Best,
>
> Paul
>
>
>
> Paul McGrady
>
> policy@xxxxxxxxxxxxxxx <mailto:policy@xxxxxxxxxxxxxxx>
>
>
>
>
>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|