<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] GNSO work place improvements +
- To: "Philip Sheppard" <philip.sheppard@xxxxxx>
- Subject: Re: [council] GNSO work place improvements +
- From: "Sophia B" <sophiabekele@xxxxxxxxx>
- Date: Thu, 6 Apr 2006 22:21:51 +0700
- Cc: "GNSO Council" <council@xxxxxxxxxxxxxx>
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=e3Xvd7Z01vgZOfD2DvhWmMiJtt+zpk7GMqAk9JUhWLeFn7npMBvgRsd14DyIiUeOy7lFKfQd71+ZTabxQH7TSyNFqF7kzKj0HqrnFrEHdcgPQRE8aIQJ8nW0w5dlaTwANBeDksvDrcRD6FKZx7uZApE0xWfhOz45/clHieZZjeU=
- In-reply-to: <012801c65988$57f86a00$e601a8c0@PSEVO>
- References: <fdcd4ef30604060042k549f6bc8i5f8a9814f77b18b3@mail.gmail.com> <012801c65988$57f86a00$e601a8c0@PSEVO>
- Sender: owner-council@xxxxxxxxxxxxxx
Thanks for the feedback Phillip...will consider both suggestions to see what
is acceptable and how far we can go!
SB
On 06/04/06, Philip Sheppard <philip.sheppard@xxxxxx> wrote:
>
> Sophia,
> great suggestions in this useful summary.
>
> Two observations.
> Using the gnso.icann.org web site for our own use makes eminent sense but
> the key is to get agreement from ICANN senior staff that the GNSO policy and
> secretariat can update this section of the web site without pre-clearance
> from ICANN legal. This has been the issue until now. If the issues persists
> I would suggest with ICANN legal agreement an entirely new URL for our
> purposes.
>
>
> There is already a list for Council members only - its called NAMES and is
> used for updating contact info etc. Its use could be extended for admin
> matters.
>
> Philip
>
>
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|